Not found page

[wkloucek]

Userstory

As a user I want to have a meaningfull not found page if I opened a non existing URL.

As a user I want to be able to recover from a not found page so that I can navigate to my files again.

Acceptance Criteria

• A not found page is available
• The not found page contains a link to ownCloud Web

[wkloucek]

@tbsbdr What do you think about this? I have something similar in mind like described here: https://medium.com/designer-recipes/how-to-make-a-custom-404-error-page-for-your-website-1af37a8b20d1

[tbsbdr]

Definitely, users should explicitly know if a file was not found. Ideally we can relieve the pain with a sympathetic image or writing.

Also further help/guidance should be provided.

[tbsbdr]

Examples how others communicate 404s:

[kulmann]

The screenshots are mixing resource not found within files app and page not found. ;-) A resource not found within files app already exists. See screenshot:

[tbsbdr]

@wkloucek Can you work with that or was your request more about a friendlier appearance of the 404?

[wkloucek]

@wkloucek Can you work with that or was your request more about a friendlier appearance of the 404?

My request is about a not found site outside of the files app. Eg. when an oC 10 bookmark (eg. https://ocis.ocis-traefik.latest.owncloud.works/apps/files?dir=/&fileid=16) is opened after the migration to oCIS you would just see a "404 not found" page

[wkloucek]

That example could be misleading since one could argue that we are migrating links inside the files app, which is true. But that won't probably apply to other apps, eg. https://ocis.ocis-traefik.latest.owncloud.works/apps/richdocuments/index?fileId=48, so there is always a use case for the 404 site (besides the file not found page in the file app)

[kulmann]

I understood from your issue, that it's about a generic 404 page for page not found. I was just pointing out that the screenshots are mixing two different things.

[wkloucek]

This is happening when I navigate to a totally wrong route in oC Web 7.0.1:

[kulmann]

As we found out today: we can't offer the notFound page in an anonymous context at the moment:

• user doesn't get initialized
• apps don't get initialized

We might change that in the future, but for now we need to accept that the notFound page only works in user- and publicLink-contexts. That was now added in #11737