OSC 2.3.3.4 vs 2.4

[Ken_Shea]

Is the move worth the effort, or expense of having it done in my case or is it more of a stop gap to OSC V3?

 

What benefits over 2.3.3.4?

 

Thanks for the input

 

Ken

[greasemonkey]

@@Ken_shea currently v2.4 and v3 do not exist.

 

2.3.4 and 2.3.4BS are the most current. The update from 2.3.3.4 to 2.3.4 is not a huge leap and does bring some cool new features - such as content modules.... And will also allow you to install the new PayPal App that brings in "hooks".

 

Do the upgrade on a secondary (sandbox) copy of your store and DB.... Then you can take your time and play with all content modules and new PP features (login with PayPal).

[Ken_Shea]

Thanks for the clarification Scott, Jack had told me that and 'd forgot.

If you are not looking into this every day the Vnumbers start to blur together.

I tried to get a local (sandbox :) I like that term) OSC going some time back but failed, may have to try again.

Now I need to try and locate what a "Content Module" is and what the "New" PayPal app has to offer.

You read all these terms but there is no single place that defines what they are, what they offer and/or what they do differently. Don't presently use PayPal but think it may not be a bad idea in terms of sales.

 

 

Ken

[greasemonkey]

@@Ken_Shea your "sandbox" doesn't have to be a local copy. Just a second duplicate copy in your "public_html" directory (or whatever your host has called it...). Then password protect this new directory to keep prying eyes and bots out.

 

There is probably a better explanation around here but here is the "quick" down and dirty;

 

Back up all files and DB!!!!!!!

 

1) create your new directory with your ftp program (filezilla or whatever) or use the file manager within cpanel (you will have to edit the config files from here anyway)

2) in cpanel go to "password protect directories"

3) choose the new "sandbox" directory and then create username and password and "check" the box and label the protected directory

4) upload your previously backed up files to this new directory

5) with cpanel file manager edit your catalog and catalog/admin/includes/configure.php files (BOTH files) to point to the new directory - example... If you store is currently located at mysite.com/catalog.... you will have to change all instances of "catalog" to "sandbox"

  define('HTTP_SERVER', 'http://www.mysite.com');
  define('HTTPS_SERVER', 'https://www.mysite.com');
  define('ENABLE_SSL', true);
  define('HTTP_COOKIE_DOMAIN', 'www.mysite.com');
  define('HTTPS_COOKIE_DOMAIN', 'www.mysite.com');
  define('HTTP_COOKIE_PATH', '/sandbox/');
  define('HTTPS_COOKIE_PATH', '/sandbox/');
  define('DIR_WS_HTTP_CATALOG', '/sandbox/');
  define('DIR_WS_HTTPS_CATALOG', '/sandbox/');

6) in cpanel (again) go to mysql databases - create a new username and password then create a new (it will be blank) database. Attached the new user to the new database

7) then (again) with cpanels file manager edit your catalog and catalog/admin/includes/configure.php files (BOTH) - near the bottom with the new username, password and database name

  define('DB_SERVER_USERNAME', '********');
  define('DB_SERVER_PASSWORD', '********');
  define('DB_DATABASE', '******');

8) then in cpanel open myphpmyadmin, find your new database and import your previously backed up database

 

These are the "basic" steps.... Hopefully I didn't miss anything (or hopefully someone chimes in if I did).

[Ken_Shea]

Thanks for the instructions, I'll give it a go, one step at a time, in the next few days.

 

I even bought a OSC book that detailed how to set up a local machine and never did get that figured out.

Just too many of those terms and instructions thrown around in it that make sense only to one that already knows.

In all fairness though, I do have a tendency to over complicate things by thinking too literally.

 

This method looks to be more straight forward.

 

Ken