Support

Hi

i recently installed ATPRO into my baseline build website. I then use Akeeba to backup this baseline and copy to new website install.

When i unzipped this backup and allow the usual Akeeba restore process to run. The restore process failed. It displayed just plain text - not the nice green screen and button that Akeeba restore normally does.

when i delete the .htaccess file (previously created by ATPRO) with HTACCESS Maker and various firewall options) the Akeeka backup process worked.

so it was not a huge hassle - but it is a bug in compatibility between ATPRO and Akeeba Restore process. If you could put this on your maintenance list to fix - would be much appreciated.

peter

hey peter, if i understand your problem correctly this is definitely not a bug. When you create a .htaccess file its specific to that location/name etc same as are SOME installed components looking for a previous root directory from where ever you moved you install from. (hence display and other errors)

I guess Nicholas will correct all if im wrong, however im pretty sure (although obviously you can) its not ideal to be restoring and copying sites (or base site) using akeeba backup, at least its not its intended purpose.

IMHO, its far far easier to zip, move, unzip, create new database to suit new user, and edit the config.php for the new install for copying base install. The whole process is 5 minutes and under

Unless of course you have multiple site's running as addon domains on 1 account which in my option is a BIG NO NO and pretty much a nightmare waiting to happen.

Hola

thanks for that ... your suggestion of zip/unzip install database is essentially what i am doing. I'm just using Akeeba to do all the heavy lifting.

well then maybe this is a feature request for either ATPRO or Akeeba - to ignore this .htaccess file - or rename - so the Akeeba restore process can run properly. Without me having to intervene..

this problem did not exist before i implemented ATPRO

peter

the reason the problem didnt exist with the standard joomla or most likely blank htaccess file is because if you take a close look at it, it does not have 1 tenth the features of the one the htaccess maker has (hence within the htaccess maker you need to specify site / root location)

the correct way to move a base site is simply zip and move the files create a new database and rewrite the htaccess and configuration.php file.

If would be impossible (perhaps not impossible, certainly not feasable) for a program to do that for you as like i said it is a simple process for basically anyone and all in all only takes a few minutes.

For it to work akeeba backup would basically need to re-write a ht access, configuratio.php file and database prior or during the restore process and you would need to ender the necessary info manually root dir, database details which some rely on the account user name username_database, live site var etc etc.

For what its worth, i dont think it'll happen or if its even really possible. Certainly not feasible, considering its only a few minute task manually.

Nicholas ?

(FYI i have a custom script which does something very similar however its been made over a long period of time and is intended as a multi site script, different to what your asking for)