New language not appearing

Hello all,

I've been in a hurry to get my old webshop cloned over to the new v4.x version (because god forbid my host allows PHP7.4) but i've already run aground at the first stage; translating it to my language (dutch).

The way I've done it on my old 3.0.2.0 build is I just copied the default 'en-gb' folder in '../catalog/language/' and renamed it 'nl-nl', then id just go through each php file translating it by hand. Then id rename 'en-gb.php' to 'nl-nl.php' and made sure all the local flags in it are set correctly. Only this time it doesn't seem to take hold, as it does not appear as an option in 'System > Settings > -mystore- > Local > Language'..

Does anyone have a clue where it could have gone awry? Did I forget something? Anything that could help would be appreciated.

- Sven

I honestly hope that you got a backup of your old 3.0.2.0 shop. OC 4.0.0.0 is not suitable for a live store, and an upgrade from 3.0.2.0 to 4.0.0.0 is almost certainly bound to fail. Extensions and themes, including language packs, written for 3.0.2.0 won't work on 4.0.0.0 unless they have been specifically ported by their authors to that new version. And they may have to be changed again for the upcoming 4.0.1.0 release. The best approach in your case will probably be using the 3.0.x.x_Maintenance branch which works for PHP8 and should be compatible for your current theme and extensions.

JNeuhoff wrote: ↑

Sun Jul 31, 2022 9:13 pm

I honestly hope that you got a backup of your old 3.0.2.0 shop. OC 4.0.0.0 is not suitable for a live store, and an upgrade from 3.0.2.0 to 4.0.0.0 is almost certainly bound to fail. Extensions and themes, including language packs, written for 3.0.2.0 won't work on 4.0.0.0 unless they have been specifically ported by their authors to that new version. And they may have to be changed again for the upcoming 4.0.1.0 release. The best approach in your case will probably be using the 3.0.x.x_Maintenance branch which works for PHP8 and should be compatible for your current theme and extensions.

My old store is still up and running, but my webhost, and many others, are gonna kill off support for PHP7.4 soon since its going EOL by the end of november, so i'm just trying to stay ahead of the curve by reacting now, instead of bum-rushing a new build the last second, since neither opencart nor hosts will offer an acceptable timeframe to transition. My current store is heavily modified and switching it over to a new build is not a 2 day job.

I know 4.0.0.0 isn't ready for live yet, but i'm also not super comfortable with doing all this work to get it running on some unofficial jerry-rigged version of 3.0.x.x, so I really have no ideal option it seems.. Either I go with the maintenance version and be stuck with that the next 3 or 4 years, or I go with 4.0.0.0 and patch as it goes along.

For the record though, I'm not trying to shoehorn my 3.0.2.0 site into 4.0.0.0, I had already reluctantly committed to rebuild the whole darn thing from scratch (though I have not done much yet, just translations).

As a small caveat, my current site is held together with whats basically ducttape and prayers, VQmod has been throwing shitfits god knows what else is wrong with it.. It works, but backend gets ugly here and there.. So i'm not sure if that will come out looking that great if I transfer that across to this maintenance build. And my php/twig skills are very basic, so if it gets too complicated and google hasn't got an answer, im screwed. With that said, is this maintenance route still a good idea? Should I just plonk all my mods and themes into a copy of it to see if it turns over, VQmod bugs and all?

Sorry if I sound a little agitated, im just running out of time and options at the moment.

Just give it a try with 3.0.x.x_Maintenance branch which is basically 3.0.3.8, with some bugfixes and support for PHP8.
If it works, it will give you some breathing space, because, as you rightly said, it will take more time to do it with a OC 4.0.x.x. BTW.: I expect Daniel to have the 4.0.1.0 released very soon, which should actually be usable.

JNeuhoff wrote: ↑

Mon Aug 01, 2022 12:17 am

Just give it a try with 3.0.x.x_Maintenance branch which is basically 3.0.3.8, with some bugfixes and support for PHP8.
If it works, it will give you some breathing space, because, as you rightly said, it will take more time to do it with a OC 4.0.x.x. BTW.: I expect Daniel to have the 4.0.1.0 released very soon, which should actually be usable.

You've convinced me, I guess its easier and safer to roll with maintenance for now. Assuming it works on PHP8.1 and not just PHP8.0, because my host is a bit of an ass about it.. Honestly, with my 1G duplex fiber connection im half tempted to just hypervisor a PHP7.4 box in my homelab just to not deal with this..

I'll give the maintenance build a go on my testbed and feed it the highly customised themes and mods one by one to see which one needs fixing, because boy was it finicky to get working the last time I built it. I had to remove ex.tax pricing from product pages (in 4.x you can do that right from stock build, apparently!), make some choice dropdowns show full price instead of the additive, other dropdowns had to show the actual picture backend lets you add to the options (or else whats the point?), and add a company field to the address table. All sounds simple, but with twig it felt like knitting steel wire. Not to mention the endless CSS fighting to get the @#$ image to stop spilling out of the !@## div everytime the page rearranges itself, and things like that.

But I digress. Maybe 3.0.2.8 has seen some tweaks that might make my plight slightly more bearable. I hope it will stop bombarding my shipping slips with seemingly unstoppable and meaningless php errors atleast, im tired of "print selection only".

One last question though; Might it be worth waiting for 4.0.1.0 to come along, or is that gonna be so close to the deadline I wont be able to get it on rails before my current live build dies?

Thanks for weighing in on this, work has been a bear recently, and I want to do the least amount of work to keep the webshop trucking along.