..or should I upload new bakery 1.84 files to modules and after that upgrade manually? I was wondering that why should I do that because there is 1.84 installed already?
is it possible for you, to take a look into the database or into the database backup file?
If yes, go to mod_bakery_general_settings
- right place is directly behind the field "zip_location
correct name of the new field is "no_revocation
definition for this field: VARCHAR(50) NOT NULL DEFAULT 'e-goods'
from my view, the best solution is:
#1 change the version number of bakery in database Table _addons
. Use 1.70 instead of 1.84
#2 start the manuell upgrade for bakery (Addons -> Modules -> Advanced -> manuel Upgrade -> Choose Bakery - RUN)
#3 check the "new" versionsnumber after the upgrade under Addons -> Module -> Details (must be 1.84 after the upgrade)
add the missing field directly in your database
# go into the database
# open table "mod_bakery_general_
# click on "Structure" in top menu of this table
# add one row (at the end of the table list), choose zip_location as field in the selectbox
# insert fieldname "no_revocation"
# select VARCHAR as field type
# insert 50 as field lenght
# select in the row "Standard" the option "defined as: " (not sure, was it is in english)
# insert "e-goods" in the textfield
or use this code in the SQL-Codebox - be sure, that you use the correct table prefix (see red marked part)
ALTER TABLE wb_mod_bakery_general_settings ADD no_revocation VARCHAR(50) NOT NULL DEFAULT 'e-goods' AFTER zip_location
.or should I upload new bakery 1.84 files to modules and after that upgrade manually?
no, it will not help, because, you have the new version number 1.84 already in your database and the upgrade is only possible and will start only, if you have a older version
I was wondering that why should I do that because there is 1.84 installed already?
your error message say's: Unknown column 'no_revocation' in 'field list' - that means: the missing field was not added by a former upgrade.
It's not possible for me, to say, why the code from upgrade.php was not working in the past - one possible answer was the strict mode from mysql - maybe, it was on at this time, when you start the upgrade, but only hypothetic
in summary - the field is missing now and there is only one way to repair it (at the moment)
one other solution: waiting for the next upgrade
one other solution: writing a php-file with the upgrade-code and call it in the browser. With this solution, it's not needed to work in the database, the script do it for you
but there is no chance to repair it without some work in files or database. add the field in the database is the fasted solution