Why would a new install have alpha and beta history? #6388
Replies: 6 comments
-
It's a bug. It only occurs for new stores. It has been fixed. |
Beta Was this translation helpful? Give feedback.
-
No, it still has not been fixed. This line of "correction" does not fix the issue as identified in the original discussion. Specifically: zencart/zc_install/sql/install/mysql_zencart.sql Line 3499 in 54c5acd Which still has
|
Beta Was this translation helpful? Give feedback.
-
Corrected by (not yet associated to a PR) commit: 47c45a3 |
Beta Was this translation helpful? Give feedback.
-
Corrected by the re-tagged 2.0.0 release. |
Beta Was this translation helpful? Give feedback.
-
Thanks for catching this @mc12345678. I have added YET MORE reminders to the build docs to triple check these values. |
Beta Was this translation helpful? Give feedback.
-
Day one of new release, download from the main page of https://zen-cart.com, via https://github.com/zencart/zencart/archive/refs/tags/v2.0.0.zip. Select to install a new store. Review database information and see that although this is a brand new install, there is history indicating that the main files are beta1 and the database as alpha1.
Go into the master branch of the software and while the code reflects just being version 2.0.0, the database of a new install seemingly incorrectly identifies a history to alpha.
This is bound to cause issues for users new to Zen Cart when upgrading to
2.0.12.0.0a or similar when zc_install is not required/not expected to be used. History would show that it was "done" in the past (upgrade within a primary version), so obviously should be done again, right?Correction applied about version upgrade as for some reason 2.0.0/2.0.1 seemed so different from 1.5.8/1.5.8a. rolling eyes
Beta Was this translation helpful? Give feedback.
All reactions