Support

 Hi Nicholas,

Problem: Angie setup.php return next SQL string as error at last step restoration with our provider Siteground:

SQL=SELECT COUNT(extension_id) FROM `KMBC_extensions` WHERE `type` = 'plugin' AND `folder` = 'twofactorauth' AND `enabled` = '1'

I assume this is the query in setup.php line 358.

Restorationprocess of the database succeeded without any problems.
I don't understand why this happen. I checked the presence of both twofacterauthentication plugins in the administrator. I can enable/disable them. I tried the restoration with both plug-ins enabled and with both disabled. (2 different backups from local site)
In the database both the records in the KMBC_extensions table are present.

Short history:
This site was originally a Joomla 2.5.24 site, running @ Siteground.
Back-upped with ABpro 3.11.4
Installed the jpa on my local Xampp installation and there performed an upgrade to Joomla 3.3.3 after I un-installed non-compatible extensions with J3.3.3.
Upgrade to J3.3.3 was very successful. No errors, no database errors, no nondiscovered extension, and no warnings.

Only one issue I had. In the Joomla post-install message, when I enabled the twofactor plug-in I was not redirected to my user-account, but both plug-ins became enabled. Also I was not able to hide the post-installation message about the twofactorauthentication. I finaly disabled the component in the database. I also tried the Angie restoration with this component in enabled and in disabled state. Nothing helped.

Took backup from the upgraded local site with ABpro 3.11.4 and tried to install online @ Siteground again. Sadly this fails...

Sorry for long explanation.

BTW, I can do a complete restoration of this jpa on my local Xampp environment sucesfully.
So this only happens when restoration @ Siteground...

Nicholas, do you know what is going wrong here?

Best regards,
Klipper

Hi Davide,

Wow, you provided me the the perfect solution!
In the general settings in Joomla I changed the table prefix to lowercase, made a new backup with Akeeba and did an install test again with Siteground. And yes everything was OK now! And....
the issue I described in my OP with the post-installation messages has been solved too with this fix.

I'm a longtime user of Joomla! but never heared of this lowercase table-prefix. The uppercase prefix was suggested at installation of Joomla! 2.5 which I accepted a few years ago. So probably there will be more people getting this problem. I will tell about this in the Dutch Joomlacommunity forum.

Great. When I see you anywhere on a Joomladay I''ll buy you a beer!

Thanks very much,
Klipper

Hi Davide,

I understand the explanation. On windows in phpMyadmin all table prefixes are in lowercase, even when in the Joomla configuration.php the prefix is in uppercase. So indeed on windows it's hard to detect this problem...

May I ask you one other question about Akeeba Backup behaviour since I upgraded our website to Joomla3.3.3? We are used to let Akeeba Backup upload the the backup files (jpa) to Dropbox automaticly. This process works like a charm.

In the configuration of Joomla! 2.5 and in Joomla! 3.3,3 the "Chunk size" are both set to 20.00 MB and "Enable chunk upload" has been checked. This because before with bigger chunks we got upload-problems at Dropbox. But weird enough our Joomla! 2.5 site was processing chunks of max. 10MB maximum (not 20MB as configured).

Now in the upgraded Joomla 3.3.3 site where the "Chunk size" is still set to 20MB and "Enable chunk upload" is still checked I only get one full .jpa file in my Dropbox. And weird no uploaderrors at Dropbox because of the filesize. I don't have really problems with only one backup file, but I was wondering why Akeeba Backup does not use it's own configuration settings.

Best regards,
Klipper

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.