Jump to content

  • You cannot start a new topic
  • You cannot reply to this topic

The Proper Way To Migrate Cs-Cart From One Server To Another Rate Topic   - - - - -

 
  • fahrezi
  • Newbie
  • Trial users
  • Join Date: 03-Aug 16
  • 4 posts

Posted 17 May 2017 - 06:52 AM #21

I've changed the permissions to be as suggested (777) and I also cleared the cache manually,

but i still get the same error..



 
  • tbirnseth
  • CS Cart Expert
  • Authorized Reseller
  • Join Date: 08-Nov 08
  • 10769 posts

Posted 17 May 2017 - 10:43 PM #22

Did you check with your hosting to ensure that ownerships (owner/group) are correct and as to what permissions you should be using?  Be sure that your config.local.php file file/dir permission setting matches what you should be using.


EZ Merchant Solutions: Custom (USA based) B2B Development, Consulting, Development and Special Projects (get a quote here).
Commercial addons, payment methods and modifications to meet your business and operations needs.


 

Posted 18 May 2017 - 06:53 AM #23

You can rename or delete the var/cache directory and CS-Cart will create it anew


Sincerely yours, CS-Cart Support Team

 

User guide       |  Developer documentation  |  Core API documentation


 
  • markhedley
  • Advanced Member
  • Trial users
  • Join Date: 19-Nov 16
  • 129 posts

Posted 23 May 2017 - 03:29 AM #24

You can rename or delete the var/cache directory and CS-Cart will create it anew

Delete only the CONTENT of /your/path/var/cache/ DO NOT delete the whole folder of 'cache' not needed! Just delete what resides inside it.

 

As for the overall issue, why no server / cs cart logs to pin the issue in one post instead of people 'Guessing' the issue?



 
  • tbirnseth
  • CS Cart Expert
  • Authorized Reseller
  • Join Date: 08-Nov 08
  • 10769 posts

Posted 23 May 2017 - 06:28 PM #25

Delete only the CONTENT of /your/path/var/cache/ DO NOT delete the whole folder of 'cache' not needed! Just delete what resides inside it.

Your reasons for this restriction?  On customer sites that have ownership/permission issues, we rename var/cache to var/Xcache all the time to get the full cache to rebuilt.

 

The registry build is a one-shot and template caches are rebuilt on demand.  Same with static data like css.


EZ Merchant Solutions: Custom (USA based) B2B Development, Consulting, Development and Special Projects (get a quote here).
Commercial addons, payment methods and modifications to meet your business and operations needs.


 
  • markhedley
  • Advanced Member
  • Trial users
  • Join Date: 19-Nov 16
  • 129 posts

Posted 08 June 2017 - 07:32 AM #26

Your reasons for this restriction?  On customer sites that have ownership/permission issues, we rename var/cache to var/Xcache all the time to get the full cache to rebuilt.

 

The registry build is a one-shot and template caches are rebuilt on demand.  Same with static data like css.

Why bother deleting the folder, just the content is fine as well. Not suggesting it's a form of restriction.



 
  • tbirnseth
  • CS Cart Expert
  • Authorized Reseller
  • Join Date: 08-Nov 08
  • 10769 posts

Posted 08 June 2017 - 08:36 PM #27

Why bother deleting the folder, just the content is fine as well.

Lazy! :-)

Easier to rename one directory than 5 sub-directories to achieve the same result.  It's also more obvious at the higher level.


EZ Merchant Solutions: Custom (USA based) B2B Development, Consulting, Development and Special Projects (get a quote here).
Commercial addons, payment methods and modifications to meet your business and operations needs.