Support

If Admin Tools did not change all of your tables' prefixes you would not be able to use your site. So there's something different going on.

If one of the prefixes you see is bak_ you can remove those tables. They are created when you choose "Backup" instead of "Drop" for old tables during restoration.

It would help me to know what are the other two prefixes you see, what is the prefix your site is currently using and if there is a table overlap, e.g. when you see abc_users and xyz_users it's overlap.

jos_ seems to be a leftover from the olden days of Joomla! 1.5, 1.6 or 1.7. Regarding the other two, which one is currently in use by your site? You can figure that out by going to Global Configuration or by visiting Admin Tools' table prefix change page where the current prefix is stated above the textbox.

Hi, this is the from admin tools backend x8hds_ - so it means i can delete the old ones?

Yes, correct. Just in case, please do take a backup before deleting old tables.

the jos_ is used by activehelper and this component is still in use...

I would recommend not using that component. This is bad practise and should be avoided. Using the metaprefix (#__) in the code is the first thing a Joomla! developer learns.

Frondend works fine...only i cant access the backend. when i change the prefix in config.php i get the backend work but...than many things are missing in the joomla backend. menus and extensions arent there. dont know... - its first time that i have tested the admin tools prefix change :-) so normal i would kick me in my own ass ;-) hahaha...

This means that you have extensions which are either hardcoding the table prefix or they don't use the metaprefix (#__) correctly. In this case you can't change your prefix and you have to find out which extensions exhibit this behaviour and change them. Look, sometimes extensions can't do otherwise. For example if you are using a forum bridge component it usually has to cache the table name prefix and not allow you to change it. This is because it's interfacing with a non-Joomla! extension and most developers don't understand how easy it is to import and use Joomla!'s configuration.

You're welcome, Jürg!