Modern websites need customizable 404 pages

[johannessteu]

Jira issue originally created by user gerhard_boden:

As a developer, I need the possibility to integrate custom 404 pages into websites with full support of content dimensions and no side effects that may interfere with other plugins or custom code on the website.

Here is a list of requirements:

• Easy to set up (path to 404 page in Configuration.yaml, or backend module)
• No or only minor performance loss when checking if page is available
• No implications with other plugins or custom code
• Multi dimension support

Ideas by [~lubitz]:

• Different types of 404 pages. For example when a node reaches it "Hide after" date, the message should differ.

There are third party solutions available, but none could fulfill the requirements mentioned above. This is why I propose to solve the issue with an official Neos core module.

Jira-URL: https://jira.neos.io/browse/NEOS-1747

[johannessteu]

Comment created by lubitz:

I would also like to see the possibility to serve different 404 pages depending on

• "does really not exist",
• "no available anymore" and
• "not yet available".

It does not need to be a "real feature", but the package should provide something (pointcut, event,...) where to hook in.

[johannessteu]

Comment created by gerhard_boden:

Hi [~lubitz],

thanks for your input!

I would need more information to get an idea how to implement this features. For Neos to know if a page is "not available anymore" or even "not yet available" it would need some sort of URI list to compare against. Or do you have any other idea how to do this?

[johannessteu]

Comment created by lubitz:

I didn't thought so deep into it. It's more an functional requirement for a better handling of time based content. E.g you have an event and promote this on a page. Now the event is gone and you disable this page by the "hiddenAfterDateTime" feature. Each traffic from search engines or other links get's an error atm. So the idea is to say on a custom 404 - "hey sorry, seems that the event has gone ... but have a look to the other ones...".

Technically, i guess you could retrieve a list of all pages (ideally by NodeType) where the hiddenAfterDateTime < NOW and where the hiddenBeforeDateTime > NOW.

[johannessteu]

Comment created by gerhard_boden:

Thanks for providing a use case scenario, now i have a better idea what you mean. I could imagine that handling different types of 404 pages is doable. In your example scenario the node isn't actually gone, but just hidden. So there could be a check at some point if the page is just not visible anymore and deliver a special 404 page for that case.

[johannessteu]

Comment created by lubitz:

Yes, sorry for didn't make it clear. I was just talking about existing nodes and there "non-existance" in the frontend.