• Home
  • Get help
  • Ask a question
Last post 46 min ago
Posts last week 81
Average response time last week 4 hours 29 min
All time posts 67932
All time tickets 10501
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.

#1218 – content items still assigned to sh404sef content category after removing sh404sef

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.
Wednesday, 28 October 2015 12:09 UTC
Kontentwerker
Hi,
unfortunately I had to disable (and finally remove) SH404sef from one of my websites. But still most of the content items seems all assigned from the sh404sef custom content category. I need to end this connection and any possible active redirects or joomla internal routing using SH404sef functionalities.

Here is the short background about this topic:
I used SH404sef for a long time and migrated it over the years from joomla 1.5 to 2.5 up to 3.4.x Since the last major joomla update I had performance problems only with the one website, which used SH404sef. A week ago I noticed SEF redirects to wrong joomla content, dead component links (SOBI) and PHP / Webserver connection problems. I had to find a quick solution. After I disabled SH404sef some problems disappear, performance get a little bit better, but PHP processes seems still to have increased and sometimes server gets down again.

I uninstalled sobi as described in your online documentation. I only uninstalled the sh404SEF component, not any of the other plugins that have 'sh404SEF' in their name. I tried to remove sh404SEF entirely, including all database tables and configuration backup files, according to your documentation. The sh404SEF custom content remained at the backend.

Then JSitemap Developer John Dagelmore found something very strange on my site, he wrote “indeed all articles seems to be assigned to the sh404sef category (maybe a database corruption?)” Despite the fact that articles show a specific category they seems all descendant from the sh404sef custom content category with ID 100. By the way, there is an second sh404sef-custom-content category with ID 111.
Dont get me wrong, I liked this component very much. The problems may caused in some strange migration update topic of previous joomla versions or some dependencies with your component. We probably won´t find out. I only have to get a stable and fast accessibility again for the website and the need to end the connection and any possible active redirects or joomla internal routing using SH404sef functionalities.
How can this be done?
Wednesday, 28 October 2015 15:18 UTC
wb_weeblr
Hi

Since the last major joomla update
You mean the real last? 3.4.5?

Your description of the problem has nothing to do with sh404SEF regular behavior. It is not technically possible for sh404SEF to have move your content into the "Sh404SEF custom content" category, there's just no code in it to achieve that.

and any possible active redirects or joomla internal routing using SH404sef functionalities.

If you uninstalled sh404SEF, it's not doing anything on your site. There's no active part left behind, only some database tables, which are obviously totally passive.

Basically, it's not there any more, so it doesn't do anything at all.

Since the last major joomla update I had performance problems only with the one website, which used SH404sef. A week ago I noticed SEF redirects to wrong joomla content, dead component links (SOBI) and PHP / Webserver connection problems. I had to find a quick solution. After I disabled SH404sef some problems disappear, performance get a little bit better, but PHP processes seems still to have increased and sometimes server gets down again.
If think I would rather connect that to content having moved somehow to the wrong categories.

I uninstalled sobi as described in your online documentation
Not sure what you mean by that. We don't advise how to uninstall Sobi

I only uninstalled the sh404SEF component, not any of the other plugins that have 'sh404SEF' in their name. I tried to remove sh404SEF entirely, including all database tables and configuration backup files, according to your documentation.
The other plugins should have gone as well in the process. You ininstall the "Main" administrator component, and it removes itself and all the rest.
You need not remove the database tables. They are passive data sitting on your server hard drive, and cannot have any impact on your site. Likewise for backup files. They are just files, passive.

The problems may caused in some strange migration update topic of previous joomla versions or some dependencies with your component.
There's not a chance in the world this would have been caused by sh404SEF - or any Joomla extensions for that matter.

The symptoms you described looks very much like:
- either a damaged database that was badly restored
- or issues during migration - but as you probably migrated to J3 quite some times ago, that's also unlikely.

So to summarize:

1 - redirects or routing: if you uninstalled sh404SEF, it's not there and cannot have any impact on that
2 - Content being under the "Sh404SEF custom content" category: no idea how that could happen. It seems to me the only possibly course of operation would be to use the Joomla batch tools and move content back to where it belongs?

Rgds
 
Wednesday, 28 October 2015 15:59 UTC
Kontentwerker
Hi,

<<You mean the real last? 3.4.5?
No, joomla 3.4

<<I uninstalled sobi as described in your online documentation
Sorry, I meant SH404sef

<<You ininstall the "Main" administrator component, and it removes itself and all the rest.

The Sh404SEF custom content" category (respectively the two Sh404SEF custom Content categories which left) should normally be deleted automatically , when I uninstall the "Main" administrator component? It has not to stay there as some part of legacy? Maybe I could disable or delete them on a testserver and look, what happen.

<<It seems to me the only possibly course of operation would be to use the Joomla batch tools and <<move content back to where it belongs?
That´s the problem: All articles show the right specific category where they belong and all categories exist. But somewhere in the joomla underground the articles seems all descendant from the sh404sef custom content category with ID 100, which does not exist anymore.

Wednesday, 28 October 2015 16:02 UTC
wb_weeblr
Hi

The Sh404SEF custom content" category (respectively the two Sh404SEF custom Content categories which left) should normally be deleted automatically , when I uninstall the "Main" administrator component?
No, because we have no way to tell if users have modified it or not, so we leave it untouched. As this is just an article and a category, it has not effect on the site and can be deleted using Joomla regular Trash functions.

sh404sef custom content category with ID 100, which does not exist anymore.
Did you delete it?

Have you tried rebuilding the category tree, using Joomla button?

Please note you should have a solid and tested backup before doing all these manipulations.

Rgds
 
Wednesday, 28 October 2015 16:27 UTC
Kontentwerker
No, I tried not rebuilding the category tree yet. I will use a testserver and have a look...

Rgds
Thursday, 29 October 2015 14:18 UTC
Kontentwerker
I tried rebuilding the category tree on a testserver, nothing changed.

I disabled sh404sef custom content category with ID 100 and all other categories except the category Service (which is at my website the Uncategoried category) get disabled too immediately. There seems to be a Connection, which I can´t suspend in the admin backend.

Rgds
Thursday, 29 October 2015 14:23 UTC
wb_weeblr
Hi

At this point I think it's just a coincidence that your content has been moved to the sh404SEF custom content category, and it has nothing to do with sh404SE itself. For instance, having 2 "sh404SEF custom content" cat (id 100 and id 111) is already more than weird.

Now I'm not sure I followed you on that. Initially you said there were 2 categories, 100 and 111, but then later you said the cat with ID 100 doesn't exist anymore?

sh404sef custom content category with ID 100, which does not exist anymore.

Did you delete it?


You didn't reply to that yet.

Rgds
 
Thursday, 29 October 2015 14:29 UTC
wb_weeblr

If you can give me access to an akeeba backup of the site, I can install locally and look at the DB content. This thing is weird. I just read again this thread and all of this sounds like a database corruption. This would be in line with excessive CPU usage by your PHP processes and the server going down.

Rgds
 
Thursday, 29 October 2015 15:16 UTC
Kontentwerker
<<sh404sef custom content category with ID 100, which does not exist anymore.

<<Did you delete it?

No, sorry, that was a wrong Expression (I meant, it should not exist anymore). The category still exist and I haven´t try to delete it. I only tried to disable it.

Surely I can give you access to an akeeba backup of the site. Do you have a wish or proposal, e.g. a directory, where I should provide it (58 MB size) ?
Thursday, 29 October 2015 15:38 UTC
wb_weeblr
Hi

No, anywhere I can download it. Either provide me access to your test site where I can download it directly from Akeeba. Or upload the fiel to dropbox, google drive or onedrive, or similar

Rgds
 
Thursday, 29 October 2015 16:29 UTC
Kontentwerker
Hi,

here is access to test site with akeeba backups

Backend URL: http://www.xxxx.net/administrator/
Name: xxxx
Pwd: xxxx
Thursday, 29 October 2015 19:46 UTC
wb_weeblr
Hi

OK, I've spent like half hour already, but I just can't make the site work locally. you've got something redirecting any request from non-www to www. As I am local, it tries going to www.127.0.0.1, which fails.
I disabled the www redirect in .htaccess, disabled all system plugins one by one, to no avail.

Do you know what's doing this redirect?

Rgds
 
Thursday, 29 October 2015 20:03 UTC
Kontentwerker
Hi,

Components / Admin Tools / .htaccess Tool
almost down at the end of the settings, above "System coniguration" there is a setting to redirect any request from non-www to WWW, which can easily be deactivated. The green Create and save .htaccess Button change this setting immediately. The result is a file .htaccess.admintools, it can be found directly besides .htaccess .

Rgds
Thursday, 29 October 2015 20:11 UTC
wb_weeblr
Well, I can't access the site at all, including admin. And as I know about this admin tool feature, I removed the .htaccess file altogether, and also disabled *all* system plugins (driectly in the database). To no avail.
Starting to think this is a hack in some php file.

In the mean time I looked at your categories table, and noted the following:

1 - the right sh404SEF custom content category is #111.
The #100 is actually a com_content category, but it's parent, category #82, is a com_webllinks category.

Regardless, most categories are good, they descend from category #1 called "Service", but the path to this category is service/sh404sef-custom-content instead of service. Similarly, it's the path to mosts categories that's wrong, as it include this sh404sef-custom-content.

There's no way this was done through Joomla or any extension (except maybe migration - which indeed rewrite the internal bits of database content), so I'm pretty sure this is a database failure.

If I was able to get to the backend, I'd surely give a go at poking into the db, but I can't.

The other thing is that's probably not helping is that you're using JotCache, which is caching full pages. You should disable it while you're working on this, it can only introduce confusion as changing settings and content is not refleted immediately onto the site.

Rgds
 
Thursday, 29 October 2015 20:20 UTC
wb_weeblr
ok, not sure why, but it looks like this was coming from using PHP 5.3!
 
Thursday, 29 October 2015 20:34 UTC
Kontentwerker
<<ok, not sure why, but it looks like this was coming from using PHP 5.3!

?? Strange.
Joomla Backend System information says: PHP-Version 5.5.30
The serverside Settings are PHP 5.5 too

Thanks for JotCache hint: I activated JotCache on the live system, because it was the only way to keep the site alive (perfromance). For my test with deactivating SH404sef category I deactivated JotCache.

<<If I was able to get to the backend, I'd surely give a go at poking into the db, but I can't.

I could provide you a PHPAdmin access to my testserver, if it would help.
Thursday, 29 October 2015 20:38 UTC
wb_weeblr
Here is what I did that restored a categories database table that looked liek normal:

1 - Open the #__categories database table with phpmyadmin or similar
2 - Delete row #100 (the sh404SEF custom content one that has a com_weblinks parent, #82)
3 - Go back to Joomla and directly hit the "Rebuild" button

After doing this, both the DB table and the display in Joomla categories table look ok, and the front end looks ok as well. Better do that on your test site first. Also, make sure you disable Joomla progressivbe caching and jotcache and other fancy things you may have going, otherwise the front end dispaly will be irrelevant.

Rgds
 
Thursday, 29 October 2015 20:38 UTC
wb_weeblr
Yes, the site works with PHP 5.4 or More, but not with PHP 5.3
 
Thursday, 29 October 2015 20:57 UTC
Kontentwerker
<<Yes, the site works with PHP 5.4 or More, but not with PHP 5.3

Ahh, sorry, I don´t get it. What dou meant before with: ok, not sure why, but it looks like this was coming from using PHP 5.3!

<<Here is what I did that restored a categories database table that looked liek normal:

Great! I will test that. Because of european time it´s late in the evening and I will wait until tomorrow when I am well-rested (hopefully). Thanks for now!

Rgds
Monday, 02 November 2015 13:48 UTC
Kontentwerker
Hi,

I did what you recommended and tested it on a test server. I had to made a few manual changes but the rest seemed to work immediately. There appeared some old categories and content items in the backend again which I had deactivated long ago. So maybe it was really an effect which was related to a previous joomla update migration.

In the meantime I switched the test server version to live website, Perfomance OK, seems to be stable online (knock on wood).

So thank you very much for your help, deleting the sh404SEF database row seems to solve the problem.

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.