-
Notifications
You must be signed in to change notification settings - Fork 535
Closed
Description
What steps does it take to reproduce the issue?
- Copy an html file containing a custom header (e.g. https://guides.dataverse.org/en/latest/_downloads/4e2c4e359b641142d3b5d34f979248b0/custom-header.html) to dataverse (e.g.
/usr/local/payara5/glassfish/domains/domain1/docroot/) - Configure dataverse to use this customized header:
curl -X PUT -d '/usr/local/payara5/glassfish/domains/domain1/docroot/custom-header.html' http://localhost:8080/api/admin/settings/:HeaderCustomizationFile - Test
- Disable default Dataverse theme
curl -X PUT -d 'true' http://localhost:8080/api/admin/settings/:DisableRootDataverseTheme) - Test
-
When does this issue occur?
When trying to use a customized header -
Which page(s) does it occurs on?
-
What happens?
- Customized header does not replace default header. Instead, both headers are displayed
- Disabling/enabling default Dataverse theme
curl -X PUT -d 'true' http://localhost:8080/api/admin/settings/:DisableRootDataverseTheme) does not have any impact
-
To whom does it occur (all users, curators, superusers)?
all users -
What did you expect to happen?
Custom header should replace default header
Which version of Dataverse are you using?
Tested with 5.9, 5.10 and 5.10.1
This is also happening both on a running server and on a vagrant deploy
Any related open or closed issues to this bug report?
Not specifically related to this behaviour
Screenshots:
No matter the issue, screenshots are always welcome.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
