Documentation Links Broken

[shkkmo]

Many of the links throughout the web to doctrine's documentation have all been broken. This includes a large number of links from blogs and from stackoverflow.

Example:
http://docs.doctrine-project.org/en/latest/reference/advanced-configuration.html

The issue appears to be a re-organization that moved that resource to:

http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/advanced-configuration.html

Instead of showing a "Page not found" error, that resource (and all other moved resources) should provide a 301 redirect response to the new url for that resource.

[jwage]

It is unfortunately not possible to do currently because we use a statically built website and github pages. It might be possible to build a map of redirect rules and do it in javascript though.

[shkkmo]

Maybe I'm missing something, but GitHub pages should be able to do a redirect easily: https://help.github.com/articles/redirects-on-github-pages/

…

On Wed, Oct 10, 2018, 7:07 PM Jonathan H. Wage ***@***.***> wrote: It is unfortunately not possible to do currently because we use a statically built website and github pages. It might be possible to build a map of redirect rules and do it in javascript though. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/doctrine/common/issues/856#issuecomment-428822235>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABLK8VPe2HsncT7ROvrsoePUrnHA4Z66ks5ujtISgaJpZM4XWf2f> .

[Majkl578]

Would that work with HTML too? We generate HTML from RST manually and only publish final HTMLs on the GH Pages.

[shkkmo]

Yes. The article I linked talks about using a plugin for github page's default static build tool, Jekyll, that generates static pages that use the refresh meta tag as an inferior substitute for a 301 redirect.

I don't know the details of your build process, but having the ability to not break links to documentation seems pretty important.

[Majkl578]

It's important to note that it also includes different subdomain, which may significantly complicate things.
It may be a lot easier to set up static redirects with NGINX for some period. I'll discuss that with @jwage if there is some sane way to get old -> new URL map to set it up.

[shkkmo]

I see this was never fixed. Due to issues like this, I have implemented a new policy of always archiving referenced documentation pages using web.archive.org/save/ and linking to the archived page.

However, this does not fix the numerous links that have been broken from sites like stackoverflow.

I see you moved the documentation yet again, now to a new sub domain. You do have redirects working there, but the older links, such as the example I posted, are all still broken and do not redirect properly.

[shkkmo]

Perhaps the scale of this issue is not understood? Just looking at the top doctrine tagged questions / answers on StackOverflow, they almost all have links to your documentation that have been broken. This seems like a rather significant issue to me.

https://stackoverflow.com/a/2062636
https://stackoverflow.com/questions/3376881/default-value-in-doctrine
https://stackoverflow.com/questions/2062473/php-orms-doctrine-vs-propel

[Ocramius]

I can understand the Doctrine 2 issues, but the 1.2 docs surely aren't relevant anymore.

Anyway, having a report of links that got broken by the move by this (by generating the old website locally) would be more helpful. The understanding of why this is problematic is very clear.

Anyway:

I see this was never fixed.

We aren't paid to work on this: step up and jump in on this work, if it is something you care about.

[Ocramius]

As for the implementation, <meta http-equiv="refresh" content="0; url=target-uri-here" /> plus <link rel="canonical" ... would be sufficient.