-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Photophere not loading automatically in NC26 #121
Comments
This is indeed not the intended behaviour. Thanks for reporting, will have a look into this |
Thanks for checking this. Just wanted to add some more information My exact Nextcloud version is 26.0.2 (Nextcloud AIO docker, latest) I also found that if I open a photosphere file from a public shared link, then Photosphere app loads automatically as intended. |
Signed-off-by: Robin Windey <[email protected]>
Signed-off-by: Robin Windey <[email protected]>
Signed-off-by: Robin Windey <[email protected]>
) Signed-off-by: Robin Windey <[email protected]>
Should be fixed in app version |
Thank you for fixing this so quickly. I updated the app and now it works. |
By the way, If I recall correctly, in older versions of the app there used to have a autorotate button in the navbar, like this one Has the autorotate button been removed in newer versions? |
Think that was a side-effect of updating the PhotoSphereViewer component to v5. Currently we're starting the component in a kind of "default" configuration: Line 23 in e0235df
I think we might need to add the AutorotatePlugin here like shown in your jsfiddle snippet. |
Until the previous Nextcloud version 25, when I click on a photosphere image (360 panorama) file, it got automatically detected and loaded in Photosphere app. Now after updating to Nextcloud version 26, and app version 1.26.3, I see that photosphere files are loaded like ordinary photos. I have to right-click on an image click "View in PhotosphereViewer" to load into the app.
Is there any setting I am missing of this is an incompatibility /bug for the new version of NC.
The text was updated successfully, but these errors were encountered: