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

Customizable 404 page for Vitro/VIVO #4053

Open
hauschke opened this issue Feb 14, 2025 · 4 comments · May be fixed by #4060 or vivo-project/Vitro#493
Open

Customizable 404 page for Vitro/VIVO #4053

hauschke opened this issue Feb 14, 2025 · 4 comments · May be fixed by #4060 or vivo-project/Vitro#493
Assignees

Comments

@hauschke
Copy link
Member

Is your feature request related to a problem? Please describe.
VIVO lacks a helpful and customizable 404 page. It could be a standard VIVO page, but the content should give directions on how to find relevant content in the VIVO, maybe linking to browsing pages, including a search slot etc.

Describe the solution you'd like
A standardized template is created. Bonus points, if it can be customized via SiteAdmin -> page management.

Describe alternatives you've considered
Alternatives would be server side, as far as I know. It would be much better to have something included in VIVO.

Additional context

@hauschke
Copy link
Member Author

Image

Mockup of potential default content for the page. Could link to browsing options or search.

@gneissone
Copy link
Member

As a little more context, there is technically a 404 returned if you try to navigate to a missing page under the /individual/ or /display/ context, e.g. http://vivo.domain.edu/display/missing-person. It just says "Individual Not Found" but the server code is 404. The template used, for reference, is https://github.com/vivo-project/Vitro/blob/main/webapp/src/main/webapp/templates/freemarker/body/individual/individual-help.ftl.

Trying to reach a page at the top level context, e.g. http://vivo.domain.edu/broken just returns the Tomcat 404, which is definitely not ideal.

@hauschke
Copy link
Member Author

Thanks, that's helpful. Would you agree that one 404 page for both scenarios wouls be sufficient, or do we need separate ones for a) missing individuals and b) missing top level sites?

@gneissone
Copy link
Member

I agree one 404 page is likely sufficient.

This was linked to pull requests Feb 26, 2025
@litvinovg litvinovg self-assigned this Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants