Customizations Questions during upgrade

[g2ktcf]

2.3.8 (2021-04-17) for that key.

And I just looked at all my debug logs after upgrading the database. It looks like I need to remove 80+ files from that OPC 2.3.8 installation as they all create deprecated logs.



Or will installing the new one fix all of these?

[lat9]

And I just looked at all my debug logs after upgrading the database. It looks like I need to remove 80+ files from that OPC 2.3.8 installation as they all create deprecated logs.



Or will installing the new one fix all of these?

Not a surprise; I thought you started with a "bare" Zen Cart for the updgrade. Current OPC version's 2.5.1 and there have been 3+ years of changes made since v2.3.8.

[g2ktcf]

Not a surprise; I thought you started with a "bare" Zen Cart for the updgrade. Current OPC version's 2.5.1 and there have been 3+ years of changes made since v2.3.8.

yea, that may be how I described it and its not really accurate. I am following the upgrade without customizations. But I copy the old store files to the new folder and then copy 2.0.0 files on top of that. All the old bits still hang around. BUT, I found that WinMerge is your friend. Compare the original install and the store folder and you can delete every file in the store folder that appears in both. Really nice and I did not know that previously.

[lat9]

yea, that may be how I described it and its not really accurate. I am following the upgrade without customizations. But I copy the old store files to the new folder and then copy 2.0.0 files on top of that. All the old bits still hang around. BUT, I found that WinMerge is your friend. Compare the original install and the store folder and you can delete every file in the store folder that appears in both. Really nice and I did not know that previously.

I'd be careful with that approach, because that 'process' might not account for core files that have been removed or added in the transition from zc157 to zc200.

[g2ktcf]

I'd be careful with that approach, because that 'process' might not account for core files that have been removed or added in the transition from zc157 to zc200.

So, are you suggesting that I upgrade the db and then use only a clean 2.0.0? I know there are images and other files that need to copied over but I am not sure what folders are truly needed. I did use WinMerger to remove the old version of IH but the site gave me a 500 error until I installed the lastest IH. Then it appears to work.


So far, the only troublesome error I am getting is

[04-May-2024 13:00:16 UTC] Request URI: /, IP address: ::1, Language id not set
#0 C:\wamp64\www\WLC_Artistry_158a\includes\extra_datafiles\about_us_filenames.php(11): zen_debug_error_handler()
#1 C:\wamp64\www\WLC_Artistry_158a\includes\init_includes\init_file_db_names.php(54): include('C:\\wamp64\\www\\W...')
#2 C:\wamp64\www\WLC_Artistry_158a\includes\application_top.php(214): require('C:\\wamp64\\www\\W...')
#3 C:\wamp64\www\WLC_Artistry_158a\index.php(25): require('C:\\wamp64\\www\\W...')
--> PHP Warning: Constant FILENAME_ABOUT_US already defined in C:\wamp64\www\WLC_Artistry_158a\includes\extra_datafiles\about_us_filenames.php on line 11.

[04-May-2024 13:00:16 UTC] Request URI: /, IP address: ::1, Language id not set
#0 C:\wamp64\www\WLC_Artistry_158a\includes\extra_datafiles\about_us_filenames.php(12): zen_debug_error_handler()
#1 C:\wamp64\www\WLC_Artistry_158a\includes\init_includes\init_file_db_names.php(54): include('C:\\wamp64\\www\\W...')
#2 C:\wamp64\www\WLC_Artistry_158a\includes\application_top.php(214): require('C:\\wamp64\\www\\W...')
#3 C:\wamp64\www\WLC_Artistry_158a\index.php(25): require('C:\\wamp64\\www\\W...')
--> PHP Warning: Constant FILENAME_DEFINE_ABOUT_US already defined in C:\wamp64\www\WLC_Artistry_158a\includes\extra_datafiles\about_us_filenames.php on line 12.

[lat9]

So, are you suggesting that I upgrade the db and then use only a clean 2.0.0? I know there are images and other files that need to copied over but I am not sure what folders are truly needed. I did use WinMerger to remove the old version of IH but the site gave me a 500 error until I installed the lastest IH. Then it appears to work.


So far, the only troublesome error I am getting is

[04-May-2024 13:00:16 UTC] Request URI: /, IP address: ::1, Language id not set
#0 C:\wamp64\www\WLC_Artistry_158a\includes\extra_datafiles\about_us_filenames.php(11): zen_debug_error_handler()
#1 C:\wamp64\www\WLC_Artistry_158a\includes\init_includes\init_file_db_names.php(54): include('C:\\wamp64\\www\\W...')
#2 C:\wamp64\www\WLC_Artistry_158a\includes\application_top.php(214): require('C:\\wamp64\\www\\W...')
#3 C:\wamp64\www\WLC_Artistry_158a\index.php(25): require('C:\\wamp64\\www\\W...')
--> PHP Warning: Constant FILENAME_ABOUT_US already defined in C:\wamp64\www\WLC_Artistry_158a\includes\extra_datafiles\about_us_filenames.php on line 11.

[04-May-2024 13:00:16 UTC] Request URI: /, IP address: ::1, Language id not set
#0 C:\wamp64\www\WLC_Artistry_158a\includes\extra_datafiles\about_us_filenames.php(12): zen_debug_error_handler()
#1 C:\wamp64\www\WLC_Artistry_158a\includes\init_includes\init_file_db_names.php(54): include('C:\\wamp64\\www\\W...')
#2 C:\wamp64\www\WLC_Artistry_158a\includes\application_top.php(214): require('C:\\wamp64\\www\\W...')
#3 C:\wamp64\www\WLC_Artistry_158a\index.php(25): require('C:\\wamp64\\www\\W...')
--> PHP Warning: Constant FILENAME_DEFINE_ABOUT_US already defined in C:\wamp64\www\WLC_Artistry_158a\includes\extra_datafiles\about_us_filenames.php on line 12.

The about_us page was added to the core in (I think) zc158. Simply delete that /includes/extra_datafiles/about_us_filenames.php file.

[g2ktcf]

Thank You!

[swguy]

> But I copy the old store files to the new folder and then copy 2.0.0 files on top of that. All the old bits still hang around.

Don't do that. Start with 2.0.0 and add in updated versions of the plugins you want.

Doing it your way will give you logs like the one from post #15.

[g2ktcf]

> But I copy the old store files to the new folder and then copy 2.0.0 files on top of that. All the old bits still hang around.

Don't do that. Start with 2.0.0 and add in updated versions of the plugins you want.

Doing it your way will give you logs like the one from post #15.

Yes, but I am following the very specific instructions at https://docs.zen-cart.com/release/2....how_to_upgrade.

Step III Create a new directory and copy your site into it
Step IV Then create a new database and load your old database in it
Step V Next, change the two configure.php files to utilize the new directory and database This way … when you attempt to upgrade you are “practicing” to see where the problems, if any will happen
Step VI Make sure all appears to be working on your temp site.
Step VII Now load the “new” version files to your new temp directory from latest downloaded ZIP
Step VIII Run the http://www.YOURSITE.com/zc_install
Step IX Choose the Upgrade Database option


am I reading these wrong?

[dbltoe]

That's just one of the ways to upgrade. The other is a database only upgrade.

I've found it easier (espeecially with sites that have had every other mod installed) to just drop the newest release into a test folder, create a blank database. Then, I use the zc_install to create the new site and populate the database.

You'll find a big red warning on the page but IMHO, the warning should be about bringing old problems into a new site. We have every right to be suspicious of any mod for 1.5.6 or earlier just do to the fact they were probably built to PHP 7.4 at best. It's been "dead" for almost two years and 5.6 has be dead for aslmost four. Many host have, or will soon, stopped supporting any PHP prior to 8.0. It's in the best interest of security that they do.

I wait on step 4 until after step 6

Step 6 of the setup is double work to me as it is so much simpler to just take the loaded files and the empty database and run the zc_install. That way, you know the configure.php files will be correctly done for your site. I temporarily leave the zc_install directory for later (never more than a few hours) use but I make sure to rename it to something that won't give it away.

Step 7 is not a problem if you setup the new test site "above" the root." IOW, if you site is at home/your_username/public_html/, setting up the new site at home/your_username/_test/ will allow any cPanel controlled site to assign a newer PHP version to your test site while letting your store continue to run on an older PHP>

Before moving in the old database, I make sure to load two mods. Lat9's Clone a Template and swguy's Mod List. Both are invaluable to me on an upgrade.

So, my "step 8" is to load the two mods and my favorite template (bootstrap). Both the mods above are run through the plugins manager in the admin as is the valuable Display Logs that's built in for several versions now.

Step 9 is to clone both the responsive_classic and bootstrap templates. Regardless of which one I decide to use, this gives me a return point if things really get munged.

Now, I can move the old database into the new and take the original step 8 after renaminng that folder back to zc_insatll.

This time I actually delete the zc_install folder, go to the admin, and set the template to the one I cloned in step 9.

Nest, I'll use the Mod List to tell me what items were not installed with my new 2.0 files. The information will lead you to the admin_pages, configuration_group, and configuration tables to gid rid of the old mods. There's no need to worry about old files. They are not there because you loaded just the fresh 2.0.0 files.

After this, you have a 90% operational 2.0.0 site ready to take on new mods and your image files from the old site.

The images are fairly easy if you have a cPanel file manager. Just go to the old stores root and copy the images from your email folder (you did change the old ZC header, right?), the includes/images, the includes/templates/YOUR_OLD_TEMPLATE/images, and the admin/images folder.

Doing the same copy from the old includes/languages/english/html_includes/YOUR_TEMPLATE to the new site's location leaves you with a working site that only needs a payment module or two to start selling.

This is the place where you make backups of everything.

None of this is scary to me, but trying to continue on with all the extra mods you want to throw at the store is VERY scary if there's no backup to get me out of a bad mod load. I timestamp backups for every mod load so I can revert back to any point I need to to recover.

Admittedly, anything seems easy after doing it as many times as I have. The only portion with any real difficulty is cleaning up the database after you update it. Mod List is your saviour in that regard.

There's a more thorough step-by-step explanation at https://myzencarthost.com/index.php?...th-cPanel.html It was written with 1.5.8 in mind but works just the same with 2.0.0. Step H of those instructions would be where the two mods and bootstrap are loaded and the templates are cloned.

pess on