↑ Return to T02 Fix Broken Links

T02a Forexlive changed URL, but has a 301 redirect

George Dorgan By
George Dorgan
My articles
Follow on:

Page no: T02a

Page no: T03a

This comes from the WP support forum:

An external site has implemented a 301 redirect for old links with a slight modification in its URL syntax.

Our blog massively uses the old syntax.
New Syntax:
http://news.forexlive.com/!/euro-climbs-above-1-3675-after-non-farm-payrolls-20140606
old syntax was: /blog/ instead of the /!/

Result: All of these redirected links work.

But: The Broken Links Checker shows them as about 1300 broken links.

What do you recommend?
1) Fix your Broken Links Checker plugin? Why don’t you wait for the redirect to take place?
2) Fix our links with Regular expression tool?

Additional question: What does Google think about these links?
Does Google consider them as broken as your tool does?

https://wordpress.org/plugins/broken-link-checker/

  • Sorry their 301 redirect is more complicated

    Old syntax:
    http://www.forexlive.com/blog/2014/10/02/time-currency-intervention-inside-information-bank-3-october-2014/

    redirects 301 to new syntax:
    http://news.forexlive.com/!/time-currency-intervention-inside-information-bank-3-october-2014-20141002

    3 differences:
    1) “news” is new,
    2) date added to new URL
    3) ! replaces “blog”

    I got about 1200 of those 301 redirects.
    All recognized by your plugin as not working.
    But they work.

  • Janis Elsts
    Member
    Plugin Author

    Posted 5 days ago #

    Thank you for the example link. Unfortunately, I can’t seem to reproduce the issue – when I add that link to a test site, the plugin correctly detects it as a working redirect. That probably means the problem is server-related.

    On your site, what error message(s) does the plugin show for those redirects?

    Also, is there anything in the server configuration that could prevent the plugin from following redirects? For example, enabling PHP safe mode or open_basedir can prevent PHP scripts from processing redirects. Certain old versions of the CURL extension have redirect-related bugs.

    To check if your server has safe mode or open_basedir turned on, go to Settings -> Link Checker and click the “show debug info” link. Look for any rows highlighted in yellow. The same link will also show the CURL version.

Most of the log looks fine. There is one potential problem, however – the CURL version. CURL 7.19.7 was released almost six years ago and it has a number of known bugs. I would recommend updating to something more recent.
[20/07/2015 18:17:32] Niko: This is from the server configuration and it is not good idea to update
[20/07/2015 18:17:45] Niko: I suggest to change them manually

Fix with Regular Expression Plugin

1700 Forexlive cases –> do not touch yet, we might later use regular Expression replace

Old syntax:
http://www.forexlive.com/blog/2014/10/02/time-currency-intervention-inside-information-bank-3-october-2014/

redirects 301 to new syntax:
http://news.forexlive.com/!/time-currency-intervention-inside-information-bank-3-october-2014-20141002

3 differences:
1) “news” is new,
2) date added to new URL
3) ! replaces “blog”

I got about 1200 of those 301 redirects.
All recognized by your plugin as not working.
But they work.

See more for Tools