Support

Normally you wouldn't need to delete anything. Just retrying the installation should work. However, the white page tells me that a timeout error occurs while installing Akeeba Backup. I would suggest following the manual installation instructions here: https://www.akeebabackup.com/documentation/akeeba-backup-documentation/installation-updates-upgrades.html#installation-manual

You have a timeout error on your host. Akeeba Backup is a big package, bigger than Admin Tools. You have to ask your host to set a higher max_execution_time in the php.ini or move your site to a more performant host.

Oops, ignore the second reply. I typed it in the wrong ticket :s

Regarding your question, 60 seconds should be enough but it actually depends. It depends, among other things, on the speed of the server and if you are using Joomla!'s FTP mode. On a slow shared host using Joomla!'s FTP mode the installation can be notoriously slow. It's neither Akeeba Backup's fault (it actually doesn't even run any of its code yet) not Joomla!'s fault: it's just a slow server. Having your host increase your PHP maximum execution time is one of the two ways to deal with this problem. The other is going to a more performant host.

If you are curious what difference does a fast host make, create a new, free Joomla! demo site at http://demo.joomla.org/. That's a low end CloudHost.net account. Try installing Akeeba Backup on that site. See how mind-blowingly faster and moother it is? That's the difference a good host makes to your site. Now stop and think that search engines do take into account the page load time in their rankings. Yes. A good quality host can be the best search engine optimisation (SEO) investment you can make, no kidding.

You need to have write access to the following folders (and their subdirectories):

• components/com_akeeba
• administrator/components/com_akeeba
• media/com_akeeba
• media/akeeba_strapper
• languages/en-GB
• administrator/languages/en-GB
• administrator/modules/mod_akadmin
• plugins/jmonitoring/akeebabackup
• plugins/quickicon/akeebabackup
• plugins/system/akeebaupdatecheck
• plugins/system/aklazy
• plugins/system/oneclickaction
• plugins/system/srp
• libraries/fof

That said, if you need to give each folder very wide permissions (like 0777) in order to install anything you need to do either of these things:

• enable Joomla!'s FTP layer, as explained in our installation troubleshooting (https://www.akeebabackup.com/documentation/troubleshooter/abinstallation.html); or
• move to a different host which uses suPHP, mod_fpm or mod_itk, eliminating permission issues

Most likely that JFTP warning is nothing to worry about. As long as the component works without a hitch you should be able to safely ignore it :)

I think that's a different issue. Please take a look at your database using phpMyAdmin. Do you see the #__ak_profiles table (where #__ is the same prefix as the rest of your database tables)?

This means that you have a partial installation of Akeeba Backup. In order to work around that, you will have to perform some manual work. Remove the following folders:
- administrator/components/com_akeeba EXCEPT the administrator/components/com_akeeba/backup directory and the administrator/components/com_akeeba/akeeba/serverkey.php file. If you remove that directory and that file you will lose your existing backups and/or settings.
- components/com_akeeba
- administrator/modules/mod_akadmin
- media/com_akeeba
- plugins/system/plg_srp
- plugins/system/plg_akeebaupdatecheck
- plugins/system/plg_aklazy
- plugins/system/plg_oneclickaction
Now you can re-install Akeeba Backup Professional.

Look. Both the Core and the Professional version share the same code. In fact the installation SQL code is identical in both versions. The only difference between the two is that Core skips a few views and a few Akeeba Engine filters. Nothing that has anything to do with the installation. If installing the Core works, installing the Pro release also works.

But! There is something that can go wrong. It's possible that Joomla! has some stuck entries in the #__extensions table and thinks that the subsequent fresh installation is an upgrade, therefore NOT trying to run the SQL code in the installation package, the one which creates the database tables. That's a Joomla! bug, not an issue on my end. I'm more furious about it than you'd ever imagine, especially since I've reported it one and a half year ago, submitted a patch which wasn't accepted / forgotten about.

Anyway. There are two ways to work around that Joomla! bug:

a. Completely uninstall and reinstall Akeeba Backup, losing all your settings and existing backups in the process

b. Have me take a look, fix things in your database and reinstall Akeeba Backup Professional on your site.

Just let me know which of those alternatives you'd like to follow.

Uninstalling the Akeeba Backup component will uninstall all associated plugins and modules.

You're welcome!

You're welcome!