Forums / Upgrading to 1.5.x / Upgrading v151 to v152 due to php upgrade

Upgrading v151 to v152 due to php upgrade

Views: 949

Results 1 to 3 of 3
11 Feb 2014, 2:31 PM
#1
pazdar avatar

pazdar

Zen Follower

Join Date:
Jan 2008
Posts:
174
Plugin Contributions:
0

Upgrading v151 to v152 due to php upgrade

Like a lot of others my website is affected by Hostmonster's php upgrade. That aside, last year I created a test site upgrading from v137 to v151 (never uploaded it to my main site out of being a little unsure of myself).

My v151 test site is operational (I just have to make a couple of inventory updates to it) Just to make sure I'm doing the right things to upgrade it and test it to v152, please tell me if these are the correct steps to take:

  1. Unzip a copy of v152 (which I've already done)
  2. Print out a list of the Deleted / New / Changed Files (since release of v1.5.1) out of the "doc" folder- I've already done this
  3. Based on that list, copy/paste/change the files in my v151 test site
  4. Test the revised v151 test site
  5. Upgrade my database to the test site
  6. Test the revised v151 test site again
  7. Have Hostmonster make it my new site

Is this correct or am I missing something?

Thanks

4 Mar 2014, 9:15 PM
#2
frank18 avatar

frank18

Deceased

Join Date:
Nov 2007
Location:
Sunny Coast, Australia
Posts:
3,427
Plugin Contributions:
2

Re: Upgrading v151 to v152 due to php upgrade

pazdar:

Like a lot of others my website is affected by Hostmonster's php upgrade. That aside, last year I created a test site upgrading from v137 to v151 (never uploaded it to my main site out of being a little unsure of myself).

My v151 test site is operational (I just have to make a couple of inventory updates to it) Just to make sure I'm doing the right things to upgrade it and test it to v152, please tell me if these are the correct steps to take:

  1. Unzip a copy of v152 (which I've already done)
  2. Print out a list of the Deleted / New / Changed Files (since release of v1.5.1) out of the "doc" folder- I've already done this
  3. Based on that list, copy/paste/change the files in my v151 test site
  4. Test the revised v151 test site
  5. Upgrade my database to the test site
  6. Test the revised v151 test site again
  7. Have Hostmonster make it my new site

Is this correct or am I missing something?

Thanks

1.5.2 is still in Beta and should not be used on a production server.

NOTE: We are sorry that Frank is no longer with us.
We are grateful for all his contributions to the Zen Cart community.

4 Mar 2014, 9:53 PM
#3
divavocals avatar

divavocals

Totally Zenned

Join Date:
Jan 2007
Location:
Los Angeles, California, United States
Posts:
10,011
Plugin Contributions:
3

Re: Upgrading v151 to v152 due to php upgrade

pazdar:

Like a lot of others my website is affected by Hostmonster's php upgrade. That aside, last year I created a test site upgrading from v137 to v151 (never uploaded it to my main site out of being a little unsure of myself).

My v151 test site is operational (I just have to make a couple of inventory updates to it) Just to make sure I'm doing the right things to upgrade it and test it to v152, please tell me if these are the correct steps to take:

  1. Unzip a copy of v152 (which I've already done)
  2. Print out a list of the Deleted / New / Changed Files (since release of v1.5.1) out of the "doc" folder- I've already done this
  3. Based on that list, copy/paste/change the files in my v151 test site
  4. Test the revised v151 test site
  5. Upgrade my database to the test site
  6. Test the revised v151 test site again
  7. Have Hostmonster make it my new site

Is this correct or am I missing something?

Thanks

The only thing you may have to do to prepare for the Hostmonster forced update is to apply these changes to your 1.5.1 store..

https://github.com/zencart/zencart/commit/274f4857062bd6df6cc73286272cb78fc86946c9

Frank is right 1.5.2 is NOT for use in a production store..

My Site - Zen Cart & WordPress integration specialist
I don't answer support questions via PM. Post add-on support questions in the support thread. The question & the answer will benefit others with similar issues.