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

Missing pages from old wiki #78

Open
iAugur opened this issue Apr 11, 2016 · 3 comments
Open

Missing pages from old wiki #78

iAugur opened this issue Apr 11, 2016 · 3 comments

Comments

@iAugur
Copy link
Member

iAugur commented Apr 11, 2016

Since the old kendra.org.uk wiki now points at kendra.io there are a lot of 404s for the old wiki pages.
As these pages were perl pages with a querystring it is not easy to put in redirects for individual 404s.
Also as they are perl pages (.pl) they get handled by the fast 404 process by Drupal [?] so don't bootstrap the site and therefore can't utilise the URL redirect functionality.
However we can 'interpret' the querystring and use the id of the old call to redirect the request to a more useable format.
I have put in a rewrite rule to redirect old wiki pages of the format:
wwwkendraorguk/wiki/wiki.pl?action=browse&id=FutureEvents&revision=54
to:
http://www.kendra.io/FutureEvents
i.e. rewrite the request to the use the id of the old call as a path.
This means that when you get 404s now you can see what they were for originally and put in a reasonable redirect using the Drupal redirect interface.
So in the example above they are now redirected to /events.
This will enable you to gradually bring the 404s under control.

There are other wiki requets that 404 that do not have the id parameter and therefore need to be handled separately. eg. https://www.kendra.io/wwwkendraorguk/lists/archive/k-developers/msg00268.html etc
We could also simply put in a redirect from the old wiki to a single page with a note or send them all to the home page.
Either way Google etc will then stop spidering them and remove them form indexes.

@dahacouk
Copy link
Member

Well done for capturing these but would like to talk more...

  • Something like https://www.kendra.io/wwwkendraorguk/wiki/wiki.pl?P2P-Next is not caught because there is no id=.
  • I think I'd still like the redirect to go to something like http://www.kendra.io/wwwkendraorguk/wiki/FutureEvents so that it doesn't get confused with real pages at all.
  • The lists redirect looks good if the .html doesn't get in the way (pre-processed.
  • What would be ideal is to redirect all these old pages to new pages and then to single pages so that I every page has a redirect and a landing error page (even if generic) and I can move them across to real pages as time goes on.
    • If we were to do that then I'd have to check out how to mass update these redirects once (if) we move back in the old content.

@dahacouk
Copy link
Member

Just referencing the closed issue #67 for additional information.

@dahacouk
Copy link
Member

Just realised I still need to do the bulk update for all wiki pages. But I feel what we need to do is send all:
wwwkendraorguk/wiki/wiki.pl?action=browse&id=FutureEvents&revision=54
to
wwwkendraorguk/wiki/wiki.pl?FutureEvents
and then I'll add redirects from there.
I have them already to rock. I just need a good kick. Perhaps that's what this is!

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

No branches or pull requests

2 participants