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

Handle 404s from old site. #178

Closed
radimklaska opened this issue Mar 8, 2018 · 8 comments
Closed

Handle 404s from old site. #178

radimklaska opened this issue Mar 8, 2018 · 8 comments

Comments

@radimklaska
Copy link
Member

Jeste jedna SEO drobnost - meli bychom nejak poresit tu tunu 404 chyb co deployem vytvorime. Issue na to nebyla protze jsme problem umyslne ignorovali, ale protoze mam pred deployem jeste trochu casu, tak se na to podivam.

Deadline je dokud se nevyresi: Switch to core Media images #113

@radimklaska radimklaska added this to the Site improvements milestone Mar 8, 2018
@radimklaska radimklaska self-assigned this Mar 8, 2018
@radimklaska radimklaska modified the milestones: Site improvements, Minimum viable product Mar 8, 2018
@radimklaska
Copy link
Member Author

Presne tohle jsem chtel napsat: https://www.drupal.org/project/redirect_404

Let's say you have a legacy system which contains most of your web presence and decide to migrate to Drupal, starting with the home page, but didn't want to orphan the legacy site. So, URL such as http://www.example.com/department would stop working and would return 404 to users visiting the site.

With mod_rewrite in Apache, it is possible to redirect 404 to an external URL, but it does not preserve the full request path nor support multiple destination servers.

If you specify legacy1.example.com and legacy2.example.com as your possible destinations for your Drupal site on www.example.com and a user visited http://www.example.com/department, which hadn't existed, Redirect 404 would then try legacy1.example.com/department if found, the user would be redirected. If not found, legacy2.example.com/department would be tried, and if found, the user would be redirected to that URL instead. If still not found, a custom 404 error page may be specified or a user message defined. You could also specify a site search URL as an option, so if you try to go to www.example.com/department and no servers are found that know what to do with the request, the user is taken to the search results page for department (example: www.example.com/search/department)

@radimklaska
Copy link
Member Author

Issue Switch to core Media images #113 je hotova. Time is up. :-)

@radimklaska radimklaska modified the milestones: Minimum viable product, Site improvements Mar 8, 2018
@martin-klima
Copy link
Contributor

@radimklaska Je k tomu nějaké konkrétnější zadání? Nevidím do logu, tak nevím, jaké máme 404 (jaké adresy jsou nenalezeny) a na jaké URL by se mělo redirektovat. Je možno získat nějakou převodní tabulku? Např.

Hledaná stránka Redirektovat na
/forum/* /forum
/clanek/* /clanek
/cokoliv ostatního/* /search/*

@radimklaska
Copy link
Member Author

Zadani je v predchozim komentu. ( #178 (comment) ) Zadne konkretni adresy...

@radimklaska
Copy link
Member Author

Issue na d.o na port modulu do D8: https://www.drupal.org/project/redirect_404/issues/2880426

@martin-klima
Copy link
Contributor

Nejprve #166 a pak se uvidí, jestli to má vůbec cenu podle logu, jestli přcházejí požadavky končící chybou 404.

@miromichalicka
Copy link
Member

Po roku je toto pointless...

@radimklaska
Copy link
Member Author

SEO timeout :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants