Last post 2 hours 55 min ago

Posts last week 89

Average response time last week 30 min

All time posts 67735

All time tickets 10467

All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#4652 – sh404sef and J 3.8.5 - 301 redirects not working

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Monday, 12 February 2018 17:58 UTC

rossm

Hi,

I have two sites where the 404 error log and 301 redirect functions are not working.

I believe this happened after upgrading to J 3.8.5.

Both sites are running sh404sef 4.13.2.3783.

Have any other uses experienced similar issues?

Thanks,

Ross

Tuesday, 13 February 2018 20:57 UTC

wb_weeblr

Hi

First off, please make sure that the "301 redirect from Joomla SEF to sh404SEF" setting under the "Advanced" tab of sh404SEF is disabled. When this is enabled, we ask the Joomla router for a possible valid URL for the incoming request, and unfortunately the Joomla router does not do this very well (it will accept URLs that are 404s).

If not entirely solved, please update to the latest dev version, [xxxx]. (you can always look at the development version in case of trouble: the changelog in it might list your problem as already solved).

Rgds

Wednesday, 14 February 2018 03:58 UTC

rossm

Hi,

Thanks for your reply.

A little background...

I have been a sh404SEF subscriber since 2010. The current (2) websites that I am having issues with are my two most recent client websites. Both were built from a "rapid release" base Joomla install that has been used for 30+ sites at this point.

The site that the attached screens are coming from was launched 10 days ago.

In the beginning when we were on J 3.8.4, SH404SEF handled the 404 logging and 301/ alias redirects as expected. I set a number of them (including the example URL as see in the attachment) and testing showed they worked fine.

We then upgraded to 3.8.5. The site was checked a few days later and several of the old 404s that were previously logged & redirect appeared in the 404 list again.

I tried the "Redirect to a SEF URL" function again but an error message was displayed telling me that this URL was already in the database and couldn't be added again.

I then searched and found it in the Aliases list. Another test of the URL still resulted in a 404 (item 4 in attached image).

Since this base Joomla install has so many sites built with it, all of which are using SH404SEF successfully I am very sure something has changed with the 3.8.5 update.

The server environments are all almost the same as well (most all sites use SiteGround).

Please let me know if you have any other ideas for me. I did confirm that "301 redirect from Joomla SEF to sh404SEF" has been disabled.

The Domain in question is https://www.xxxx.net

I have been with you a long time and like your extension and don't want to be forced to find another option.

Thanks again,

Ross

Thursday, 15 February 2018 08:55 UTC

wb_weeblr

on't want to be forced to find another option.

This is really, really harsh statement to make. I hope you don't really mean anything like that because you just had experience one single and simple problem after years. I take these things very personnally.

Please let me know if you have any other ideas for me.

The problem is exactly what the "Dev version" is solving and I can see it on your first screenshot:

That 404 record is invalid because it has a leading slash. You need to update to the dev version and delete those records. You should also delete the aliases records, or modify them to remove the leading slash they may have.

Rgds

Friday, 02 March 2018 05:34 UTC

system

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.