Last post 5 hours 33 min ago

Posts last week 141

Average response time last week 4 hours 42 min

All time posts 67805

All time tickets 10478

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.

#5784 – 404 page

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.

Thursday, 02 May 2019 22:06 UTC

Jake

The 404 page is only partially working. If I enter a URL I know that doesn't exist to test it, for example, https://xxxx/test it works as it should. It shows the bad karma page. But when I enter numbers instead of text, https://xxxx/567899 it does not work. It will instead show jos-Error: Article not found

The reason I stumbled on to this error is that I have articles that begin with a number, for example, https://xxxx/6851-kullaberg and I tried adding a number after it to test the 404 feature (https://xxxx/6851-kullaberg1), I received the jos-Error: Article not found message.

Friday, 03 May 2019 12:33 UTC

wb_weeblr

Hi

That error is likely not coming from sh404SEF actually. It's caused by one of your extension (possibly your template) which breaks when being displayed on the sh404SEF error page.

Now this is true assuming you are fully up to date, both Joomla and sh404SEF on the latest version.

Note that even with Joomla latest version, there might be an issue with the Redirect system plugin, so if you have that plugin enabled, make sure to disable it.

Then to debug the issue:

- set Joomla error reporting to "Maximum", this may yield a more detailed error message, with a hint of the actual source of the problem
- temporarily switch to one of Joomla built-in template such as protostar
- if that does not identify the issue, disable one by one your non-joomla system plugins
- if that does not identify the issue, disable one by one your non-joomla content plugins

We can then advise.

Best regards

Friday, 03 May 2019 13:55 UTC

Jake

Both Joomla and sh404SEF are up to date.

The redirect plugin is disabled.

I set the error reporting to maximum but it doesn't show any more details of the error than jos-Error: Article not found.

It did help to switch to protostar, but don't you think it's odd that this only happens when there are numbers in the URL. I'm using Yootheme Pro which is very popular. Am I the only one that has encountered this issue?

Friday, 03 May 2019 14:07 UTC

wb_weeblr

but don't you think it's odd that this only happens when there are numbers in the URL.

Not at all. This happening is linked to a specific action taken by one or more of the features of your template.

One thing you can try is to disable sh404SEF "similar URL" URL plugin: as this removes some of the work we do in case of 404 (searching for a 404), this may also remove the interference your template is causing.
But that's unlikely to help. What's likely happening is that your template is trying also to handle itself the 404 and it causes this.

Am I the only one that has encountered this issue?

In recent years, yes. This used to happen with Joomla and some extensions some years back, which is why I asked about being up to date. This might also be something they have introduced recently and nobody noticed yet.

You might want to ask YooTheme how can their 404 handling feature can be disabled for instance?

Best regards

Friday, 03 May 2019 14:15 UTC

Jake

It didn't help to disable the similar URL plugin.

They do state in their changelog that they have sh404SEF error handling compatibility since a year ago.

Friday, 03 May 2019 14:24 UTC

wb_weeblr

They do state in their changelog that they have sh404SEF error handling compatibility since a year ago.

Well, something's changed in that sector then. I'd still recommend talking to them at this stage, as the problem source is now identified.

Best regards

Saturday, 18 May 2019 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.