First things first. Fixing bugs and safety should always be a top priority. Let's hope that they'll speed up a bit with the next improvements.ADD Creative wrote: ↑Wed Jan 09, 2019 11:55 pmReading the comments here. https://github.com/opencart/opencart/issues/7130 While there are some important bug fixes in the latest release, many did not make it. The main purpose seems to be to add Google Shopping and update some payment extensions.
The ones I reported are all to do with Twig issues:
Twig ignoring template variables added by view/*/before events
Twig has no working auto-refresh
Twig doesn't accept changes from view/*/before events
My suggested pull request fixes all of that.
It basically makes OC 3.1.0.0 backward compatible for view/*/before events.
And it solves the problems with Twig caching, including auto-refresh, cooperates nicely with the theme editor changes. There is no more need for cumbersome lambda functions. And last not least, it can now automatically detect whether a template is twig or php before the rendering. Finally, the rendering time, therefore the overall page load time, is now faster, too.
Export/Import Tool * SpamBot Buster * Unused Images Manager * Instant Option Price Calculator * Number Option * Google Tag Manager * Survey Plus * OpenTwig
my extension:https://www.opencart.com/index.php?rout ... estshop24h
email :support@bestshop24h.com
site:http://www.bestshop24h.com
since OC changes in various Sections, from Subversion to Subversion again. And
nobody officially still works on older Releases anymore, if a new one arrives, since
OC has no free Ressources for such, but needs to concentrate on latest 'Things'.
In addition to the fact, that ANY upgrade Code would ONLY be capable, to function
with strictly DEFAULT OC Code, which is, in most of all OC-installations, just not the
case anymore.
It's the price, to pay, to get something for free, and without further Obligations ... :-)
So, better decide on a Version, where Extensions for your Needs exist, instead of
concentrating on Version Numbers, it would make much more sense !
Good Luck!
Ernie
My Github OC Site: https://github.com/IP-CAM
5'600 + FREE OC Extensions, on the World's largest private Github OC Repository Archive Site.
What he saidIP_CAM wrote: ↑Sun Feb 17, 2019 2:10 pmWell, better forget the word UPGRADE, when it comes to OC, it has no meaning,
since OC changes in various Sections, from Subversion to Subversion again. And
nobody officially still works on older Releases anymore, if a new one arrives, since
OC has no free Ressources for such, but needs to concentrate on latest 'Things'.
In addition to the fact, that ANY upgrade Code would ONLY be capable, to function
with strictly DEFAULT OC Code, which is, in most of all OC-installations, just not the
case anymore.
It's the price, to pay, to get something for free, and without further Obligations ... :-)
So, better decide on a Version, where Extensions for your Needs exist, instead of
concentrating on Version Numbers, it would make much more sense !
Good Luck!
Ernie
Jim
https://www.carguygarage.com
Yahoo Store since 2006 moved to OpenCart on January 24, 2020
I think you'll find a lot of improvements by switching from Yahoo. If you need any assistance, let us know. We have a lot of years of experience working with Opencart.head_dunce wrote: ↑Thu Apr 11, 2019 6:30 pmThis is very encouraging to see. I'm attempting to move my 13 year old Yahoo Pro Merchant Solutions store to OpenCart. It's only been a few days now, and I'm further along than I had anticipated. Very nice to see the core team is doing commercial support and the product is always being improved upon. I hope all goes well and other Yahoo store owners I know make the jump too. Thank you.
ELEV8TE Website Development
Available for hire - please contact me at https://www.elev8your.com/contact
https://www.elev8your.com
Good Luck!
Ernie
My Github OC Site: https://github.com/IP-CAM
5'600 + FREE OC Extensions, on the World's largest private Github OC Repository Archive Site.
Looking forward to hearing for 3.1.0.0
Daniel wrote in July 2018, that the release of OC3.1 is imminent after a brief alpha and beta phase. Obviously there were/are many bugs to fix...and I'm totally happy, that the focus is on a stable version before releasing a version with many bugs left.
I keep my fingers crossed for the developers (and also for us shop-owners), that the tasks can be completed in a timely manner.
Now to my question:
We are in a dilemma, since we run a well-attended shop, but with OC1.5.6.4 increasingly aging. Unfortunately, a further development to a newer OC-Version is very time-consuming and costly for us, because we had to program an individual solution for our complex configurable products in the frontend.
So, on the one hand, we want to wait for a current OC version to make the further development...on the other hand, we want to leave behind the increasing problems with OC1.
I know that the project managers of OC, for understandable reasons, don't like to write anything about release dates. But I also hope that the OC-project managers can understand the situation of some shop owners and are willing to make at least a rough statement. Something like "in the next quarter", "at the end of the year" or even something like "in no case this year" would be a very helpful, to make a decision.
Apart from that, I am certainly not the only one, who is very grateful for the great work of the programmers.
So thanks a lot and kind regards
Kiu
By providing that type of information to the public, since OC also connects with service providers, for payment and shipping reasons, then each PCI compliance email dates where developers would receive updates about would also need to be known which is unlikely possible in order to adapt the change into multi OC releases.I know that the project managers, for understandable reasons, don't like to write anything about release dates. But I also hope that the project managers can understand the situation of some shop owners and are willing to make at least a rough statement. Something like "in the next quarter", "at the end of the year" or even something like "in no case this year" would be a great decision-making aid.
Dedication and passion goes to those who are able to push and merge a project.
Regards,
Straightlight
Programmer / Opencart Tester
Well, you seem to be waiting for the ultimate Thing, for a good while already,
as it looks! But I'm afraid, that's not gonna work out, as planned, because OC
is a steady ongoing Project, a latest FINAL Version will therefore never exist.
But just don't take it personally, and don't be upset, because, they owe you nothing,
not even an explanation, because OC still comes for free, and without obligation. And
if you would really have a Problem with your v.1.5.6.4, why did you never write about
it around here? Others like me would sure like to know about, if really one exists, related
to OC, and not only some Mods. Or you could at least have updated the ~20 Files, slightly
changed in the last v.1.5.6.5_Release-Candidate, to still fix existing 1.5.6.4-Version
Misses !?
https://github.com/opencart/opencart/bl ... angelog.md
Then, you would have a proven working System, except for, if you changed or added
some third-party Code. Which then would still not be an OC v.1.5.6.x Problem either ...
Ernie
PS. Nothing personal, I just heat up a little, if my beloved Version is beeing
talked down, for most likely no good reason at all ...
My Github OC Site: https://github.com/IP-CAM
5'600 + FREE OC Extensions, on the World's largest private Github OC Repository Archive Site.
Users browsing this forum: No registered users and 7 guests