Wade Walla wrote:
I personally setup a new folder on my root. I then copied the current site locally and then uploaded the files into the new folder.
Basically, a Joomla install exists in two parts, the files in the folder that Joomla uses, and the DB that holds all the information.
Copying the folders to a sub folder is only half the process. If you want to create a second permutation of your site to edit, you need a new DB to store the information (edits to the site).
When you simply copy all the folders from your current install and place them in a sub folder, you are not really copying the site because you are not creating a new DB to hold the new information.
Besides that, even if you can access the new site the edits will effect the old site, not the new one because all the references are pointing to the original site.
Simply:
A) Use Akeeba to backup your site.
Create a new DB for the new site.
C) Extract the backup files from Akeeba to the sub-folder
D) Point your browser to the sub folder to run the install, e.g., if your sub folder is named "dev", instead of going to
www.mysite.com
, you would go to
www.mysite.com/dev
When you run the install from your backup, the old DB info will display as default, replace it with the info you used wen you created the new DB (Step
.
After you complete the install, you will have two separate sites and two separate DBs, the site that is in the root, and the site that is in the 'dev' folder.
To view the current site, you'd go
www.mysite.com/
, to edit
www.mysite.com/administrator
, for the 'dev' site to view,
www.mysite.com/dev
, to edit
www.mysite.com/dev/administrator
...so I can then upload the Panacea template, make changes as I want, test everything and when I'm fully ready, point the current live domain to this newly created site (based on new template)
You won't want to point the current live domain to the newly created site because it's in a sub folder.
When you are ready, you'll reverse the process by backup up the dev site, then deleting the old site and than installing the dev site in the root... but let's cross that bridge when we come to it.