There should be no difference. Can you open your browser’s error console and see if there are any errors when you go via Tools > Redirection?
No Error messages, a couple of warnings about the use of self closing tags and an unmatched end tag for a div in tools.php.
The main difference seems to be that using the Tools menu and clicking on Redirection counts as a navigation as far as the browser is concerned whereas clicking on Redirects from the Options menu of the plugin does not.
Once I am successfully viewing the current redirects, if I click on the urls refresh button it again counts as a navigation and I get the same “Something went wrong” page.
So it is not a url issue.
Hi there! Same problem here! I am using WP v.4.8 and php 5.6. Plugin is 2.7.1
I am trying to downgrade the plugin, and see if it works..
Sort of glad to see its not just us.
We have a couple of different websites, all with similar issue.
We are using PHP 5.4.45.
One of our websites still has Redirection plugin version 2.6.3 on it and Redirect list is working on that version. However the Log and 404 pages are not showing any items and the Option page is not loading properly, so I am suspecting that React is the issue.
With version 2.7.1 all the pages are working when access is via the Options page so React seems to be working. Its just that it does not work when accessed from the Tools>Redirection link.
Hi again,
The issue has disappeared downgrading the plugin to 2.6, but unfortunately it seems we have lost all the previous redirections (ouch).
It is a bit nonsense since all these data surely is in the database… we haven’t confirmed yet if the data and tables are still there..
Any other ideas, news or fixes will be very welcomed.
Thanks, regards
I am unable to reproduce this, and cannot see any reason why it should be happening. If it is at all possible to get a login to a 2.7.1 site exhibiting the problem that would be a big help – my email is on the plugin’s support page.
@javierferraz nothing should change in the database
Fixed by installing version 2.7.3 (skipped 2.7.2 so don’t know about that one).
Thanks John.