Skip to content
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

Collection Thumbnails Not Displayed Correctly on Homepage After Adding Custom Logo, Thumbnail, and Footer Images #10960

Closed
ofahimIQSS opened this issue Oct 23, 2024 · 1 comment
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Type: Bug a defect UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF

Comments

@ofahimIQSS
Copy link
Contributor

ofahimIQSS commented Oct 23, 2024

Description: While testing GitHub Pull Request #10886 , an issue was uncovered regarding collection thumbnails on the homepage. After adding a custom logo, thumbnail, and footer image to a collection, the thumbnail fails to update and still displays the default Dataverse collection thumbnail instead of the uploaded custom one.

Steps to Reproduce:
Create a new Collection.
Navigate to Edit Collection > Theme + Widgets.
Upload a custom Logo, Thumbnail, and Footer Image for the collection.
Publish the Collection.
Navigate to the Dataverse homepage.

Expected Behavior:
The custom thumbnail uploaded for the collection should appear on the homepage, replacing the default Dataverse Collection thumbnail.

Actual Behavior:
The homepage still shows the default Dataverse Collection thumbnail instead of the custom thumbnail that was uploaded.

Environment:
Dataverse Version: v 6.4 (Demo)
Browser: Chrome

Note: This was not introduced as part of PR #10886 and happened sometime before that

@ofahimIQSS ofahimIQSS added the Type: Bug a defect label Oct 23, 2024
@pdurbin pdurbin added Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF labels Oct 23, 2024
@pdurbin pdurbin removed their assignment Oct 23, 2024
@ofahimIQSS
Copy link
Contributor Author

retested and could not reproduce issue in internal and demo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: JSF Involves modifying JSF (Jakarta Server Faces) code, which is being replaced with React. Type: Bug a defect UX & UI: New React UI Needs enough design work that it should probably go in the new React UI, not JSF
Projects
None yet
Development

No branches or pull requests

3 participants