It is also causing the "other" languages to crash.Daniel wrote:i will not be releasing 1.5.5.1 because soem peoples extensions aren't working!
very easy to fix the extension to work with my changes.
When upgrading to this version all 3rd-party extensions stop working to.
Why in the world would you make such changes WITHOUT mention this or discuss this first?
You have a responsibility to all the people who depend on OpenCart.
You are not programming just for Daniel anymore, you are programming for 10.000+ users AND builders that use OpenCart.
Such changes should be well discussed and mentioned BEFORE a release!
People will tear there hair out (again) because they run into issues because you "just" changed something!
Norman in 't Veldt
Moderator OpenCart Forums
_________________ READ and Search BEFORE POSTING _________________
Our FREE search: Find your answer FAST!.
[How to] BTW + Verzend + betaal setup.
as for the reasons why i did the changes its because i'm planning on changing the loader class to a hook type system. i wanted people to switch to stop using it for loading languages.
OpenCart®
Project Owner & Developer.
Except that those extensions using the return array present in previous versions will not have their language work. I'm not sure the prevalence of using this method, but I know a number of well-known developers (including myself) that uses this method.MarketInSG wrote:I think changing $this->load->language to $this->language->load for all modules will do the trick.
Personally, I'm going to start skipping the language class altogether, and use my own instead.
open all files and do a search and replace for load->language to language->load
then get the language library class and include it in your extension to replace the new one with the old one.
OpenCart®
Project Owner & Developer.
I'm glad I've build my new store in 1.5.4.1.
atm. I'm really disappointed (again) in the way the release of 1.5.5 is done.
And the worst part is: update to extension I just bought will be probably only for 1.5.5.
Can you imagine how much work it will cost to have them also updated for 1.5.4.x and older?
Norman in 't Veldt
Moderator OpenCart Forums
_________________ READ and Search BEFORE POSTING _________________
Our FREE search: Find your answer FAST!.
[How to] BTW + Verzend + betaal setup.
Maybe it would have been better to include this change to an 1.5.6 version, but we are updating our extensions to language->load and it's just a little while to do it. We don't worry about this change and we are looking forward to see opencart improved.
Regards,
Daniel
I will stick in my modified 1.5.3.1
Thanks for the good work, but i better be oldschool.
1.5.5 Loader::language Fix
Use this vQmod to fix "Call to undefined method Loader::language()" error at OpenCart 1.5.5, while using 1.5.4.1 and earlier extensions.
2DEVS: You may include this file to your distributions or even include it into your vQmod files. It is made in special way to not harm earlier OpenCart versions and stack (be applied several times) safely.
Download - http://www.opencart.com/index.php?route ... n_id=10158
Cartless (free) - "buy" button instead of "add to cart"
Stripper (free) - strip parts of OpenCart

Most of them have chances to work. But there are another changes at OpenCart 1.5.5 that may affect extensions functionality.elektroarena wrote:So with that vqmod all extensions and themes from 1.5.4.1 will work?
Cartless (free) - "buy" button instead of "add to cart"
Stripper (free) - strip parts of OpenCart

Question - if I do this and get everything "perfect" on my local machine, how hard is it to then update my live stores? Do I just need to upload my local machine files (except config files of course), and run any upgrade scripts on the database?
Running Opencart v3.0.3.2 with multi-stores from https://www.labeshops.com which has links to all my stores.
Users browsing this forum: No registered users and 20 guests