Allow custom error pages if View Code does not exist
Currently any unkown View Code in the URL (e.G: vid=PRIMA) leads to empty page and rotating diamonds.
In the background Angular is unable to fetch the configuration URL /primo_library/libweb/webservices/rest/v1/configuration/PRIMA which is answered by an HTTP 406 error from the server.
To the enduser its completely unclear where the problem is located, did she/he make a mistake or is there a problem on the server.
I would suggest to provide at least generic error page (View Code not found) and respond by HTTP 404 or 406 to the client. This is also important for search engine crawlers if there are any outdated permalinks on websites.
For mulittenant and local installations it would be great if this can be customized at installation level.
Thanks
Ulrich
Ulrich Leodolter
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 30 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Primo.
Best regards,
Primo Product Team
-
Manu_Schwendener
commented
What I'd like to see: an easily customizable 404 page with the main menu of the default view.
---
I asked UX and accessibility expert Craig Abbott https://bsky.app/profile/craigabbott.bsky.social if a 404 page or an automatic redirect to the landing page of the default view is better:
"It depends on what the url is doing.
If you use the link to view a page, and the page has moved, then it makes sense to go a 301 or a 302 redirect, because the outcome still meets the expectations.
If you use a link to view a page and it’s deleted, rather than moved, then a 404 makes sense.
If it’s an outdated base url, but the page exists on a new url, 301 redirect would still be a better option. 404s should really be when there’s no better option available."
-
Manu_Schwendener
commented
I understand that this has been closed as part of the cleanup effort.
That doesn't change the fact that it's an expected feature in any web product. Either a redirect to the start page or a separate 404 page witch includes the main navigation of the default view.
Related:
-
Manu Schwendener commented
-
+1