Just install the standalone template in template manager and then make it default and create equivalent template overrides in the new template (and assign them) for any you may have on your existing template.
BUT, please be aware that it is highly likely that you will have to change your content in some way - either to stop using some of your old template classes or to use some classes from the new template. Why not create a backup of your site using akeeba backup and then restore it locally using akeeba kickstart (in WAMP, XAMPP, or MAMP) then you can try it out without risk to your production site.
Regards, Mark.
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
May I pull on your expertise again?
I am on an iMac running OSX 10.9 for a Joomla site.
I installed MAMP and have green lights. I set to Apache Port to 80 and the SQL to 3306.
I restored my site using a .jpa Akeeba backup with Kickstart. The restore seemed to go fine.
When I attempt to start the site via localhost, I get a new start/open window that says "you have chose to open: which is: application/x-httpd-php (1.5 KB) from: http://localhost
Ugg... I restored OS 10.8.5 - then downloaded a new copy of MAMP, Kickstart and the .jpa backup file. Went through the install of all and restoration of the .jpa. The restore went fine. Then when I selected the option to visit my sites frontend, I get an open windown attempting to open index.php. Then when you say OPEN, it opens a blank window.
look in the apache error log - blank screen is nearly always a server500 - most common reason is insufficient memory_limit in php.ini
Regards, Mark.
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.