• Home
  • Get help
  • Ask a question
Last post 15 hours 58 min ago
Posts last week 81
Average response time last week 4 hours 29 min
All time posts 67914
All time tickets 10497
All time avg. posts per day 20

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.

#2748 – 404 Error page opens up the home 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.
Friday, 23 September 2016 05:25 UTC
realize
Hi Support,

 We are using SH404 sh404SEF 4.8.0.3423 | in the following website. If Sh404 is enabled the 404 page opens up the home page.
After disabling the Sh404sef then it will open up the proper error.php file.

https://www.xxxx.com.au

Please let us know how to fix it,

Thank You
Friday, 23 September 2016 06:49 UTC
wb_weeblr
Hi

It doesn't "open the home page". It uses the default Itemid, because none has been set, and Joomla displays the module, template, etc attached to the home page.
If you have a different layout for non-home pages on your site, then you can select which Itemid to use to display the home page in sh404SEF configuration. Please refer to the Error page documentation on this page, specifically "Itemid to use".

Rgds
 
Wednesday, 05 October 2016 00:51 UTC
realize
Thank you for the reply. I tried the documentation but still I am not able to display the "Bad karma: we can't find that page!" message or the Joomla 404 page I have created. Could you please have a look where I am doing wrong.

Details for the staging site
https://www.xxxx.com.au/dev/
https://www.xxxx.com.au/dev/administrator

username: xxxx
password xxxx


Thank You
Wednesday, 05 October 2016 07:35 UTC
wb_weeblr
Hi

The first thing is that you had selected "Use Joomla 404 error page", so the sh404SEF was disabled. I restored the setting to its default, "Override Joomla 404 page".

As is often the case, the problem is coming from your template. Switching back to one of Joomla default template fixes the problem immediately:

[xxxx]

I also tried to look at your template settings, but I can't really, as the template settings page is broken (you can't "Save" or "Cancel" from the page, at least I can't on Chrome). In addition, there does not seem to be any settings related to this, so it has to be internal.

While looking at this, I noticed a few malfunctions in sh404SEF:

- it keeps trying to display analytics reports (and thus show an error because you have not setup analytics), while I specifically set it to not display any report
- You still had the "sh404SEF custom conten" category, and the "__404__" article that we used a very long time ago to display error page. This has been changed a long time ago, and should have been removed during updates to a more recent version. I suspect the removal failed because you have set a menu item leading to that 404 page (which is not needed) but I'm not sure. I deleted that category and article, but again, that's not use anymore, so it doesn't have any effect.
- There are many aliases similar to this:
which are invalid and may be causing issues. Do you know where they come from? There cannot be any / there, it has to be a non-sef URL. Those should be deleted.

Though I know the problem is not in sh404SEF, but in the template, next step to understand the problem would be to download an akeeba backup, install on a local machine and debug the PHP. I can't do that because the backup is too large, at 2GB+. If you can exclude images, or whatever takes up that much space, from the backup and get down to a reasonable size, like 300 to 500 MB max, I can do that.

Rgds




 
Friday, 07 October 2016 01:22 UTC
realize
Thank you for going through this issue.

I have created two zip files (files & db) in here

https://www.xxxx.com.au/dev/backup/

username: xxxx
password: xxxx

Thank You

Friday, 07 October 2016 07:18 UTC
wb_weeblr
Hi

I wasted 30 minutes on trying to restore the mysql stuff, it always dies in the middle, with an invalid characters error.

Please just use Akeeba backup, simply exclude the /images folder or which folders have a lot of data. That's by far the most reliable way of doing such transfers.

Rgds
 
Sunday, 09 October 2016 23:25 UTC
realize
Hi

Sorry about the mysql backup.
I have created a Akeeba backup "Backup taken on Sunday, 09 October 2016 23:01 " and it is 316MB.

Thank You
Monday, 10 October 2016 09:28 UTC
wb_weeblr
Hi

You put a password on the installer...

Rgds
 
Tuesday, 11 October 2016 00:47 UTC
realize
Hi

So sorry about it. I was not aware that the backups were protected with a password. As I am have no idea about the password I tried deleting the password.php file from the installation directory ( I was using the Akeeba Kickstart in localhost) as mentioned in this thread.

https://www.akeebabackup.com/xxxx

Also, I have created a another Akeeba backup without the password and tested on my localhost and it is working without the password.

Thank You
Tuesday, 11 October 2016 08:21 UTC
wb_weeblr
Hi

So I got the backup and installed it on my local machine.

The immediate result, without any kind of change, is that everything works perfectly fine:

- The error page is displayed exactly as it should:
[xxxx]

- even the issue with Google Analytics trying to load up even if disabled is gone:
[xxxx]

Everything is absolutely normal. The PHP version I am using for this test is pretty much the same, 4.4.45 vs 4.4.1, this is also Apache

There is not much I can on top of that. One thing that can happen here is that your dev site is completely damaged, and just restoring the site properly, files and db, simply came back to a working state. I have no better idea, but that seems likely. I would encourage you to do the same, and create another copy of your dev site. It might always be something on the server configuration, but I don't see what could cause that, so just a damaged database/file system seems like the most likely reason.

Rgds

 
Tuesday, 11 October 2016 22:43 UTC
realize
Thank you very much for looking in to this issue. I will try to restore the website and check in over end.

Thank you
Wednesday, 12 October 2016 08:19 UTC
wb_weeblr
Hi

I will leave this ticket open in case you need to add something. It will automatically close in 2 weeks, if not further comment is made.

Best regards
 
Thursday, 13 October 2016 22:21 UTC
realize
Hi,

I did restore the live site database using Akeeba backup and it fixed the issue. It seems like database was corrupted. Thank you very much for looking into this issue and directing.

Thank You
Friday, 14 October 2016 08:25 UTC
wb_weeblr
Hi

Glad to hear that, that's what I suspected when I saw that many diverse errors.

Closing this ticket now, feel free to open another one as needed.

Rgds

 
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.