I tried to backup cs-cart from original server and restore it on new server. My cs-cart version is 4.3.4.
I firstly setup a trial version of cs-cart on my new server. I restore the backup copy I made on original server.
On the new server, I did rename the admin.php to storeadmin.php and start to restore by using the backup file, the process looks like to extract the .tgz file, after a while, load error found, I check with the file, the storeadmin.php lost. Now I can't continue the restore.
What is the proper way to migrate cs-cart from one server to another? Is there any documentation show the procedure step by step?
I read this, I have problem when installing the new cs-cart
The URL rewrite engine is disabled. Subpath-based storefront URLs will not work
Although it doesn't affect the installation, I continue, after I overwrite the files and restore the database, I can't see the menu " Add-ons | Administration | Settings | Design " on the top. My backup has two storefronts using subdirectory.
My first question: Is mod_security the reason I can't see the menu after restore?
Second question: How can I run the new cs-cart on new server and ensure everythings ok before I release the license from old server, once I change the full license to free license, then all my storefront not work on old server. It is not save to me to migrate the server without having a full testing on new server.
My migration steps as below:
Zip the whole folder of cs-cart on old server
Backup from admin panel (do I need to backup each storefront one by one?)
New install the cs-cart with same version on new server
Rename config.local.php on new server
Extract the zip file from old server
Replace config.local.php with the renamed file
Restore from admin panel
Now I have question how I can transfer the license save.
It is allowed to use live license on the development website. But this website should be closed for public. Just contact CS-Cart license department and ask them to add development domain as alias to the main domain of your license
When you backed up all files on old server, you also included var/cache. Remove this folder from new server manually.
Open the administrator area (it should work after cache clearing) and re-configure your storefronts.
Thanks for reply.
Recently I found the support from cs-cart was a bit slow. As we urgent to fix the problem and there is not alternative way to contact the support even though we have the support credit.
I replaced whole cs-cart folder on new server by old server, of course I did remember to keep the new config.local.php, I logged into the admin panel and restored the database, I couldn't restore the storefront. I did backup the database from old server under All Stores (not individual store). Is it the reason I didn't clear the cache before the restore action? Should I need to backup/restore all stores individually? I could not find any documentation about backup/restore for multiple storefronts.
After restoring database on new server, make sure you opened the 'Stores' page in the administrator area and configure each storefront properly there. And it is very important to manually remove var/cache after moving file to the new server.
After restoring database on new server, make sure you opened the 'Stores' page in the administrator area and configure each storefront properly there. And it is very important to manually remove var/cache after moving file to the new server.
I backup the Database and restore it on new server, I am sure I remove /var/cache after moving file, I goto menu Administration > Stores, I could not able to see the two storefront in list, only the Smitech? If the step of removing files and restore database swapped, will it affect the result? Anyway, I remove the files and restore again, still only the Simtech store on cs-cart.
I backup the Database and restore it on new server, I am sure I remove /var/cache after moving file, I goto menu Administration > Stores, I could not able to see the two storefront in list, only the Smitech? If the step of removing files and restore database swapped, will it affect the result? Anyway, I remove the files and restore again, still only the Simtech store on cs-cart.
Best regards,
Kelvin.
Looks like the database was not restored in full. Did you receive the "Done" green notification?
Looks like the database was not restored in full. Did you receive the "Done" green notification?
Every things look fine without error, I install the cs-cart using trial mode first, once I confirm the restore is fine, then I migrate the license, remove cache and restore several times, still can't see the storefront but the Simtech and all language disappear also. Although my old cs-cart is in Chinese as primary language, I don't think it is the critical issue.
I'm trying to migrate my cs-cart multivendor 4.3.8 site to the new server. I have to import database and update the config.local.php file.
But, when I access my site in the new server, I get this error
Fatal error: Uncaught --> Smarty: unable to write file /var/www/html/var/cache/templates/responsive/wrt591a6df1c1b492_68829712 <-- thrown in /var/www/html/app/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_write_file.php on line 46
I'm trying to migrate my cs-cart multivendor 4.3.8 site to the new server. I have to import database and update the config.local.php file.
But, when I access my site in the new server, I get this error
Fatal error: Uncaught --> Smarty: unable to write file /var/www/html/var/cache/templates/responsive/wrt591a6df1c1b492_68829712 <-- thrown in /var/www/html/app/lib/vendor/smarty/smarty/libs/sysplugins/smarty_internal_write_file.php on line 46
Can anyone tell me how to fix this?
The issue is caused by file/directory permissions. Try setting permissions for var/cache directory to 777 recursively
Assuming you created an archive from your old site. When you extract the archive in your new site you need to ensure that you are doing this as your cpanel account (or appropriate user). If you do it as root, it will use the old user/group ids and they will probably be wrong on the new server.
Better to fix the actual (root cause) problem than to open up the permissions to everyone/everything.