No way to embed a picure uploaded to the gallery #474
Labels
No labels
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#474
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Once you have uploaded a picture to the gallery, the user gets prompted with a page showing him the picture itself and a markdown code to embed the picture into a blog, but once the user leaves this page, they cannot get back to it, because of the images in the gallery not being clickable. This results in the user being unable to use the pictures uploaded to the gallery, except as the Illustration, which is selectable in the drop-down menu below a post.
Plume version (and/or commit):
0.2.0
Did you wrote a description for your image? Normally, if you did, it should show next to the image in the gallery and be clickable. But the gallery interface was quite horrible before #452 (which is probably not yet deployed on your instance).
Anyway, I will check if the issue is still here with the new gallery design.
The instance I'm using is https://fediverse.blog/ if this helps.
OK, thanks. As I said in #475 I'm currently updating it. I will tell you once it's done, so that you can check the issue is indeed fixed, but I checked in the code and normally it should be: there a now a "Details" link for each image that is always visible.
@MrSoUndso It should be fixed now. Can you please confirm?
I think we can consider this as resolved. If the issue is not actually fixed, please tell us.