-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Albums: Broken share expiration date in form label #621
Comments
If you reopen the link after being logged in, do you see the expected page? |
@alexislefebvre no after logging in, the album share link gets redirected to my main photos folder. I noticed that the share link does not have "public" in it: this leads me to believe it is a photoprism issue. Thoughts? |
I discovered the issue is related to having an expiration date on the link. Above the selection it says "Invalid DateTime". I'll have to check the date/time of the OS this evening. I suspect it is set incorrect. If it is correct, then maybe a bug. With no expiration date, the share link works |
You're right, we can see this error on https://demo.photoprism.org/albums/aqjyfk72jstm22m5/berge-2020 too: And the share link https://demo.photoprism.org/s/1gxdaj4bas/berge-2020 doesn't work, like you described it. |
Thanks for reporting, we will have a look at it on the weekend! |
Signed-off-by: Michael Mayer <michael@liquidbytes.net>
Signed-off-by: Michael Mayer <michael@liquidbytes.net>
Just tested on new ubuntu 20.04 container - public album share link with expiration worked as expected! I didn't test the actual expiration of the link yet (will have to wait 24 hours), but the link itself functions. Excellent app - I'm loving it |
The link is accesible Addition the expiration is entered in the database i checked with changing the seconds in db the link really expires. |
Looks like a pure frontend issue: It tried finding a date in "UpdatedAt" while the actual field name is "ModifiedAt".
Share form label is fixed: It tried finding a date in |
I am guessing this is related to my reverse proxy. Any tips on where to start looking? For what its worth, I am successfully using my reverse proxy with Nextcloud, Seafile, W10 blue iris, Cryptpad and 3 or 4 other applications, so i'm not a complete novice. But I can't seem to figure this one out. I'm not certain if its a bug or a configuration issue.
The text was updated successfully, but these errors were encountered: