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

Some redirects not working. #101

Open
samuk opened this issue Nov 25, 2016 · 11 comments
Open

Some redirects not working. #101

samuk opened this issue Nov 25, 2016 · 11 comments

Comments

@yvonnestruthers
Copy link
Collaborator

Hi Sam,

I cannot see either of these articles as having been requested to be redirected in the 301s file?

For the second one - that one doesn't seem to need a redirect as when I click on the link it is finding the correct article in any case?

Is it that you have applied other redirects than the 301s we have done which are not pulling through? Sorry if I'm not understanding the issue correctly.

TN-301-v2.xlsx

@samuk
Copy link
Member Author

samuk commented Nov 25, 2016

Ah I see I assumed that you'd done some regex. I didn't realise it was only that specific list of URL's. Could we look at adding something like

RewriteEngine on
RewriteRule ^/blogs/rob-hopkins//(.)$ https://transitionnetwork.org/news-and-blog/$1 [R=301,L]

(The above isn't correct, but illustrative)

@yvonnestruthers
Copy link
Collaborator

Hi Sam

Are there any other areas which you are aware of that were missing from that document? If so, please could you specify them here, as there is a bit of a process involved in implementing each of the changes to the htaccess file which takes up time from the maintenance contract, so it would be best to make any further changes all at once to make the process time efficient.

If this is the only one you're aware of then do let me know and I will find out from the developer if the above is a possibility.

Many thanks

@samuk
Copy link
Member Author

samuk commented Nov 29, 2016

Hi Ella

It's the only one I'm aware of at the moment. Redirecting the old blog URLs to the new ones would be great in my opinion.

@ainsliebeattie are you happy for Yoke to spend time on this?

Thanks

Sam

@yvonnestruthers
Copy link
Collaborator

To clear any confusion - for example 1, that blog is not included in the redirects because it was written after the 301 document was produced so there is not redirect in place for that one. There is a regex set up that is doing as you request for the old blog post that were included in the 301 document.

Regarding example 2:

The issue here seems to be that the URL that Wordpress generates from the blog titles is sometimes different from the one that Drupal generates -

For example this URL:

http://transitionnetwork.org/blogs/rob-hopkins/2010-09-21/transition-pattern-language-project-support-concept

The node with this title:

<title>The unstoppable rise of 'Demain'.</title>

when imported into wordpress created a new post with this URL based on the title:

https://transitionnetwork.org/news-and-blog/the-unstoppable-rise-of-demain/

The old post's URL on Drupal does not match the title, so this is the old drupal url:

http://transitionnetwork.org/blogs/rob-hopkins/2016-02/unstoppable-rise-demain

This redirect is working as the redirect is just grabbing the end of the url (unstoppable-rise-demain), and moving it into the new url structure, giving thus:

https://transitionnetwork.org/news-and-blog/unstoppable-rise-demain

which gives a 404.

Perhaps these have been edited manually in Drupal at some point as Dupal should generate the same strucutre urls based on page titles (which is what all the other blog posts which are finidng their new pages have). This is the common problem for any that are actually redirecting fine, but giving 404's as the URL's dont match the titles.

Not sure what to suggest, this may have to be a manual job, as it's not something we can cater for on an automated basis.

Please let me know how you'd like to proceed.

@thisisyoke
Copy link

@ainsliebeattie and @samuk seems the last comment in this issue nails the problem. Not much we can do apart from manually editing these, but it is tricky to know how many there are. See what you think

@ainsliebeattie
Copy link

Could I have an estimate of time to manually do this - and to determine time to do this. I would probably like to find the funds to get you to fix it so I need a quote.

@thisisyoke
Copy link

Hmm, it is hard to gauge tbh. We am unsure of how many there are. The only way to do this accurately would be to give us 1 hour to try to access how many there are. Then after that hour we can say "Ok, there are 500 to do and this will take 2 hours" for example.

Unless @samuk you can try to calculate how many need attention to begin with

@samuk
Copy link
Member Author

samuk commented Feb 22, 2017

I don't know how to calculate how many need fixing.

I have started a sheet here of high traffic posts that could do with fixing https://docs.google.com/spreadsheets/d/1gzC9py1MLeqaGvDpZNHParV3k3XejvVAFLuPwe4G9F8/edit#gid=0

Could you fix these in the first instance as we continue our investigations.

Thanks

Sam

@thisisyoke
Copy link

I would estimate you give us 3-4 hours and see how much we can get done.

This is a bit of a manual labour job tbh and not sure if using us is best if you are short on cash. But up to you

@samuk
Copy link
Member Author

samuk commented Jun 1, 2017

Have you found the 301 file? I can probably do the grunt work here.

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