Updating - follow along
Posted: Mon Jul 18, 2022 7:05 pm
In case someone could learn anything from this or just find it interesting, I will share some progress, thoughts, ideas and maybe tips and tricks here.
Background:
Two and a half year ago, I began working on a PhoenixCart 1.0.4.0-shop to replace a much older and unsupported cart software for my boss. I knew very little about anything at the time, but had messed around with the old shop enough to know that something had to be done to make the site more secure, user-friendly, responsive and future-proof.
My boss had a lot of request for functionalities and I had a lot of ideas and wishes so I did my best to fulfill them all, often by making core-code changes.
Now it's time for that shop to be updated and I curse my past self for the core-code changes!
Considerations
I considered a few different approaches:
For both of these approaches, the plan would be to go through the entire process on a mirror-site on the host-server, take note of all the steps, and then redo them on the live-site. Alternatively I could replace the live-site with the mirrored one, when it was thoroughly tested - that would depend on what would be easiest when I got there.
Another downside to both of the above approaches was that it wouldn't clear out all the core-code changes I had made (and I want to get rid of them) and the database would contain legacy stuff from my own changes, that I would have to clean up afterwards.
Also, there are several things I would like to take a different approach to now, which is easier done by taking a third approach:
I chose this last option, as I wanted a fresh start and the jump to me seemed too big for the other approaches.
Process
My first step was to make a spreadsheet with all current functionalities/add-ons and design-changes, and add notes to each of them: How could they be done? Would another approach make it better and maybe usable in more cases than the specific ones they serve now? Are there any of the already available add-ons that will do the job? etc.
Next I downloaded and installed PhoenixCart 1.0.8.16 to a Xampp-server on my laptop. The first thing I added to this was Zipurman's Phoenix Bundler as that will make the process of creating new add-ons a lot easier. On the final install, the free version will be used to install everything and keep track of what's added to the site.
Next step was to download the add-ons already made by others, that supports 1.0.8.16 and adding links to the rest in my spreadsheet, so I can watch out for updates to them while making the things that are not already there. The downloaded add-ons were loaded with the bundler to make the installer hold every single add-on on the new site in the end.
Next post will touch on the process of making one or some of the add-ons I need to make myself.
//Daniel
Background:
Two and a half year ago, I began working on a PhoenixCart 1.0.4.0-shop to replace a much older and unsupported cart software for my boss. I knew very little about anything at the time, but had messed around with the old shop enough to know that something had to be done to make the site more secure, user-friendly, responsive and future-proof.
My boss had a lot of request for functionalities and I had a lot of ideas and wishes so I did my best to fulfill them all, often by making core-code changes.
Now it's time for that shop to be updated and I curse my past self for the core-code changes!
Considerations
I considered a few different approaches:
- Step-by-step upgrading
- "Chunk" updates
For both of these approaches, the plan would be to go through the entire process on a mirror-site on the host-server, take note of all the steps, and then redo them on the live-site. Alternatively I could replace the live-site with the mirrored one, when it was thoroughly tested - that would depend on what would be easiest when I got there.
Another downside to both of the above approaches was that it wouldn't clear out all the core-code changes I had made (and I want to get rid of them) and the database would contain legacy stuff from my own changes, that I would have to clean up afterwards.
Also, there are several things I would like to take a different approach to now, which is easier done by taking a third approach:
- Fresh start
I chose this last option, as I wanted a fresh start and the jump to me seemed too big for the other approaches.
Process
My first step was to make a spreadsheet with all current functionalities/add-ons and design-changes, and add notes to each of them: How could they be done? Would another approach make it better and maybe usable in more cases than the specific ones they serve now? Are there any of the already available add-ons that will do the job? etc.
Next I downloaded and installed PhoenixCart 1.0.8.16 to a Xampp-server on my laptop. The first thing I added to this was Zipurman's Phoenix Bundler as that will make the process of creating new add-ons a lot easier. On the final install, the free version will be used to install everything and keep track of what's added to the site.
Next step was to download the add-ons already made by others, that supports 1.0.8.16 and adding links to the rest in my spreadsheet, so I can watch out for updates to them while making the things that are not already there. The downloaded add-ons were loaded with the bundler to make the installer hold every single add-on on the new site in the end.
Next post will touch on the process of making one or some of the add-ons I need to make myself.
//Daniel