upgrade or start again? 1.58 to 2.0.1
ok so after an accidental erasure and restore from backup i have a few issues made worse by trying to add accessibility tags to currency selection menu on my live site.
Currently i'm on php 8 so it will allow me to run install in a subdomain. I tried to run a copy of the site with php 8.3 and the admin side would not load and the template triggered loads of deprecated warnings. i'm pretty certain my template will not survive the upgrade, or at least not without alot of tweaks... At what point is it better to start again, am i there?? :(
custom modules = qr tickets, push notifications, pwa setup and the xbox code delivery module (no longer used but working)
installed modules = structured data, ep4 (works but issue activating tax on inserted products) google merchant centre feeder 2... raft of modules that came with wokiee template.
I am also struggling to see my products in google shopping results. It's almost like i have dropped off the face of google for most search terms when looking for items i have in stock and unsure exactly why.
i have the install ready to go too but it seems to be setting the admin domain as crazygamer.uk instead of crazygamer.uk/subdomainfolder
trying to ensure my live site doesnt get overwrote by mistake and i could do with help clarifying the correct settings to enter...
Code:
Storefront HTTP Domain
https://www.crazygamer.uk
Storefront HTTP URL
https://www.crazygamer.uk/subdomainfolder
Storefront HTTPS Domain
https://www.crazygamer.uk
Storefront HTTPS URL
https://www.crazygamer.uk/zen2
Storefront Physical Path
/path/to/dom/crazygamer.uk/public_html/subdomainfolder
i feel like they should all end /subdomainfolder and leaving some set to main domain will result in an overwrite, yes??:wacko:
Re: upgrade or start again? 1.58 to 2.0.1
IMHO, 2.0.# was a rush to publish. Not due to Zen Cart, but do to the payment and PHP rapid changes at the time.
Both have seemed to settle for a bit and ZC 2.1.0 is presently in beta with actual release very soon. It is head and shoulders above 2.0.# and has been in beta test for a while.
I would wait till 2.1.0, do a database only upgrade to the new files, load only essential payment/shipping modules, and let it make some money while you use a test site and copied DB to gradually get your "extra" mods brought up to speed.
I would start by adding Clone a Template and Bootstrap to the main files. Clone both responsive_classic and bootstrap and copy that to a test folder before you add any mods.
Work from there until you get it back where you want it.
Re: upgrade or start again? 1.58 to 2.0.1
Quote:
Originally Posted by
dbltoe
IMHO, 2.0.# was a rush to publish. Not due to Zen Cart, but do to the payment and PHP rapid changes at the time.
Both have seemed to settle for a bit and ZC 2.1.0 is presently in beta with actual release very soon. It is head and shoulders above 2.0.# and has been in beta test for a while.
I would wait till 2.1.0, do a database only upgrade to the new files, load only essential payment/shipping modules, and let it make some money while you use a test site and copied DB to gradually get your "extra" mods brought up to speed.
I would start by adding Clone a Template and Bootstrap to the main files. Clone both responsive_classic and bootstrap and copy that to a test folder before you add any mods.
Work from there until you get it back where you want it.
Thankyou for the reply, I was seeing zen 2.1 was almost ready, issue i have is as you pointed out with the php issues, i see that php 8.03 has vulnerabilities a pen test tool picked up from checking my site, they was marked as critical issues and the recommendation was to switch to php 8.3 to resolve the issue. I just hope hostinger don't force my site onto php 8.3 as a result of those vulnerabilities. My modules seem to run fine on php 8 so im hopeful that they will simply drop in....
I do have a missing base64 class error that returned after my ssh accident on the push notifications module, think i need to make an autoload file and composer.json and maybe post it to code collab section so it can be fine tuned if it doesn't pass approval when submitted. the qr ticket module is wrote in a very odd way, works like a charm but i highly doubt it would pass contribution guidelines and may benefit from a rewrite, it was many weeks/months prompting chatgpt for code and i don't think PDO queries should be used for it to be contributable :blush:
My main worry there is that i may have issues with such things like npf's as i need that to add the required fields such as event_time, event_date ect :lookaroun
