OpenCart Community Forum - Discuss shopping cart and e-commerce solutions.
https://forum.opencart.com/
Agreed.... leaving bad builds available has always caused problems. At this point I'd almost say skip 2.3 and remove all traces from the download list and jump straight to 2.4 to avoid any further confusion.Johnathan wrote:Daniel or James: when you release a fixed 2.3.0.2 build, please remove the 2.3.0.0 and 2.3.0.1 links from the download list. People seem to still download old versions even when the newer one is available, for whatever reason.
I definitely agree to that ...Qphoria wrote:Agreed.... leaving bad builds available has always caused problems. At this point I'd almost say skip 2.3 and remove all traces from the download list and jump straight to 2.4 to avoid any further confusion.Johnathan wrote:Daniel or James: when you release a fixed 2.3.0.2 build, please remove the 2.3.0.0 and 2.3.0.1 links from the download list. People seem to still download old versions even when the newer one is available, for whatever reason.
Will github's Clone or download work for e.g. the 2.3.0.0 or 2.3.0.1 tags? Or has it the same problem with the missing bugfixes?Qphoria wrote:I've just confirmed many of the fixes over the past month on the release candidate did not make it into the 2.3.0.0 or 2.3.0.1 builds. Do not use these. The changes are in the repo but for some reason the zip file that was created wasn't made from the correct version.
It will now. The issue was there were a bunch of fixes that weren't accepted for merge. TortoiseGit shows any committed change to the files so I was seeing it in the log, but the actual changes hadn't been accepted and merged into the master. It has been updated now so the current master trunk should be functional. New version should be released today. In my preliminary testing, upgrade worked fine and most other features at a high-level were working.JNeuhoff wrote:Will github's Clone or download work for e.g. the 2.3.0.0 or 2.3.0.1 tags? Or has it the same problem with the missing bugfixes?Qphoria wrote:I've just confirmed many of the fixes over the past month on the release candidate did not make it into the 2.3.0.0 or 2.3.0.1 builds. Do not use these. The changes are in the repo but for some reason the zip file that was created wasn't made from the correct version.
I already made mod suggestions to fix both of the issues you mention, and Daniel said he would add them to 2.3, but they were not added. The issue I reported was closed, so I assume they intentionally left the fixes I suggested out.Dreamvention wrote:Hi guys! Glad to see a new release.
1. one thing that I have noticed was the backwards compatibility thing - it would not support install and uninstall methods in the older modules controllers.
this is because the compatibility event would simple drop these methods off and only load the index.
I have made a simple fix.
https://github.com/opencart/opencart/pull/4715
2. also there is the permission issue - now it would add permissions to the new modules folder structure but not to the old.
so permissions will never be given to module/[codename] or payment/[codename] etc and only to extension/module/[codename] etc.
the fix is in this pull request by OpenCartAddons https://github.com/opencart/opencart/pull/4712
Please add this to the next release since without this I will need to ship a vqmod/ocmod patch with all of my modules and that really sucks. i am sure lots of developers will appreciate it.
Opencart v2.3.0.2 is the stable version, so far.slavib wrote:Please tell which version is stable to start work
The ones listed in the downloads list, other than v2.3.0.0 and v2.3.0.1, are the official releases and the v2.3.0.2 is the latest. It would be best to wait until the version shows on the downloads list or announced on the forum before expecting future releases.slavib wrote:I had in mind expect soon a new version.
Someone mentioned to 2.4
The official statement is already written into the parentheses of the downloads list where it indicates: (latest version) . If this fact must be differed, eventually, an administrator will confirm it.slavib wrote:I understand completely.
But I think it's good to have an official statement.
A new version was just officially released today. There are no determined period to know when a new release will be unleashed until an official announcement has been made.slavib wrote:Hi
I do not ask what is the latest version.
Will there be a new version?
thats really sad. well then i guess vqmod/ocmod will still come in handyJohnathan wrote:I already made mod suggestions to fix both of the issues you mention, and Daniel said he would add them to 2.3, but they were not added. The issue I reported was closed, so I assume they intentionally left the fixes I suggested out.Dreamvention wrote:Hi guys! Glad to see a new release.
1. one thing that I have noticed was the backwards compatibility thing - it would not support install and uninstall methods in the older modules controllers.
this is because the compatibility event would simple drop these methods off and only load the index.
I have made a simple fix.
https://github.com/opencart/opencart/pull/4715
2. also there is the permission issue - now it would add permissions to the new modules folder structure but not to the old.
so permissions will never be given to module/[codename] or payment/[codename] etc and only to extension/module/[codename] etc.
the fix is in this pull request by OpenCartAddons https://github.com/opencart/opencart/pull/4712
Please add this to the next release since without this I will need to ship a vqmod/ocmod patch with all of my modules and that really sucks. i am sure lots of developers will appreciate it.