Akeeba Backup for Joomla!

Thursday, 03 October 2013 02:18 CDT

user79611

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes - various - blank page after install, troubleshooting install, restore points
Have I searched the tickets before posting? Yes - Ticket 17724 is more relevant
Have I read the documentation before posting (which pages?)? Yes - all
Joomla! version: 3.1.5
PHP version: 5.4.7
MySQL version: 5.5.27
Host: Localhost - XAMPP Lite 1.8.1 on Windoze 7 x64 Pro
Akeeba Backup version: 3.8.2 Pro

EXTREMELY IMPORTANT: Please attach a ZIP file - Didn't get that far.

Description of my issue:

Quickie one-page site being created for upcoming event.
Starting point was a JoomlArt Quickstart for Joomla 3.1.5 for the JA-Onepage template packaged 8/5/2013 (our first suspect!)
One extension added other than those already in the Quickstart to select editors from the footer.
Template design completed & tested, and ready to migrate site to hosting. Needs to be live ASAP.
Attempted install of AdminBackup Core - upload failed due to default file size limit. PHP.ini edited.
Installed AkeebaBackup Core
Install successful.
Clicked to go to first time configuration and immediate error - See screenprint.
Repeated install of core.
Install successful. See screenprint.
Switched to installing Pro per Nick's recommendation in a ticket.
Hand deleted relevant folders from Administration, Library, media,plugins, etc. for FOF, JMonitor Akeeba per checklist from Nick for installing Pro after Core.
Installed AdminTools Pro first per recommended installation sequence (load Backup last) and to also test if Joomla Installer might be having an issue.
Install successful.
Test usage successful.
Installed AkeebaBackup Pro
Install successful.
Clicked to go to first time configuration and immediate error - See screenprint.
Per troubleshooter, repeated install of AkeebaBackup Pro.
Install successful. - See screenprint.
Error recurred.
Repeated install of AkeebaBackup Pro and immediately disabled Restore Point plugin.
Clicked on menu item Component - Akeeba Backup Pro
Error recurred.
Turned on Joomla Debugger. It reported a divide by zero error at line 728 in debug.php and otherwise reported 71 queries took 105ms with nothing standing out to my untrained eye.
Screenprint attached.
Searched your KB, and tickets. Ticket 17724 seemed identical to my situation, but no suggestions were offered. Googled the Joomla! forums, no joy.
Another possible suspect - This was a previously used install of XAMPP meaning there is another site's tables in the database under a different table prefix and htdocs folder was simply emptied before the quickstart installer was run. I have never had two sets of Joomla tables interfere with each other, but mention this just in case. The other site was successfully running 3.8.2 core when it was migrated off

Five screenprints attached in rar5 file.

Thank you in advance for prompt assistance. I am embarrassed that I am having to open a ticket. The objective is to migrate site ASAP and take it live and like any good project, I was supposed to have done it on Monday. I can run screen-sharing using Mikogo and talk via Skype duke_speer.

Best regards,
Duke

Thursday, 03 October 2013 03:59 CDT

nicholas

For crying out loud, I don't need the story of your life, just the error message and the immediately previous step. I took me 20 minutes to read your message. So, you get the error in the title of the ticket when accessing Akeeba Backup. Cool, that's easy to fix.

Turn off Debug Site in your Global Configuration and try accessing your Akeeba Backup Control Panel page twice.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 03 October 2013 09:00 CDT

user79611

OK, then what?
The error is repeatable ad infinitum.
The page that is not rendering is the e-mail checkboxes and mandatory acceptance.

(You complain when people don't self-help, you complain when they do ... <warm smile>)

Thursday, 03 October 2013 10:12 CDT

nicholas

Well, did you turn off the Debug Site in Global Configuration? :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 03 October 2013 11:41 CDT

user79611

I thought you didn't want a novel.

Global Settings - Debug set to 'no'
Click Extensions - Akeeba Backup Pro - Error Displays
Click link to (joomla) Control Panel - Panel Displays
Click Extensions - Akeeba Backup Pro - Error Displays
Clear all caches - verify cache is Off
Reboot
Click Extensions - Akeeba Backup Pro - Error Displays
Extensions - Install Extension - ABP
Click Post-Installation Wizard - Error Displays
Click Extensions - Akeeba Backup Pro - Error Displays
Click Extensions - Akeeba Backup Pro - Error Displays ...

Thursday, 03 October 2013 11:46 CDT

user79611

The pressure is off - in desperation I have hand copied and pasted all content and changed files in the localhost site to the online site. The site has been fully recreated and is now live. Thanks for trying to help.

Thursday, 03 October 2013 16:13 CDT

nicholas

I am still wondering why... This should only happen if one of your database tables was there from an ancient version of Akeeba Backup (pre-3.5.0). In this case the automatic table consistency check and upgrade code will fail with the error you mention. The same error will also happen if you try restoring a new version of the site on top of an older version of the site using an old (pre-3.6.0) version of Akeeba Backup. In your lengthy description I didn't see any of that happening. Did I get lost in the backstory and missed something?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Thursday, 03 October 2013 19:14 CDT

user79611

No, nothing that old.
Of course in all my attempts to self-fix, I could have mucked something up.
Is there a checklist for doing a complete cleanup - both folders and DB entries - removing all traces to start fresh or a master search and delete sequence of queries?

Friday, 04 October 2013 02:36 CDT

nicholas

There is a way, but you'll lose your backup settings. Delete all the _ak_ tables from your database, i.e.:
abc_ak_profiles
abc_ak_stats
abc_ak_storage
where abc_ is the common prefix of your site's tables.

Then reinstall Akeeba Backup.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Sunday, 13 October 2013 03:46 CDT

nicholas

Sometimes you will receive an error:

An error has occurred. 0 SQL=

when installing or upgrading Akeeba Backup. This error occurs only on Windows when you are using an uppercase database table prefix and your default database engine is set up to be MyISAM (default configuration on pre-packaged servers). The solution is to use a lowercase database prefix in your site's Global Configuration page.

Technical explanation
This is actually a problem with MySQL when you're using MyISAM tables. Each MyISAM table is saved as a file on your hard drive. The name of the file is the name of your table. On Windows the filenames ABC_something and abc_something point to the same filename as the underlying file system (NTFS or FAT32) is case insensitive – it treats uppercase and lowercase letters as the same. On Linux and other UNIX-based operating systems –where MySQL was originally designed to run– the file systems are case sensitive which means that ABC_something and abc_something are different files. This fundamental difference makes MySQL fail when trying to modify MyISAM tables whose name includes uppercase characters names on Windows.

This is not a problem with Akeeba software or Joomla!. It is a problem with MySQL. Our software uses abstracted table names, in the format #__something. The "#__" is called the metaprefix and is automatically replaced by Joomla! itself to the configured database table prefix automatically. The SQL query with the replaced prefix is then sent to MySQL for execution. MySQL fails miserably –for the reasons already mentioned– without providing an error code and error message. This confuses Joomla!'s JDatabase API which ultimately results in this unintelligent error message.

A simple solution is:

Open the file configuration.php, found in your site's root, with a plain text editor such as Notepad
Search for the line starting with public $dbprefix
Change the uppercase to lowercase

For example, if the original line reads:

public $dbprefix = "ABC_";

change it to read:

[code]public $dbprefix = "abc_";

WE STRONGLY ADVISE YOU TO NEVER USE UPPERCASE DATABASE TABLE PREFIXES.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Tuesday, 12 November 2013 18:00 CST

System Task

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.

Support