@nmay1990 i tried that, also tried different browsers. To avoid running into this.
@Kovah Ah, yes. The last entry is 1.5.4. there. No higher version number…
But i thought of that yesterday, that the setup was not correctly executed when upgrading. So i set
DISABLE_SETUP=false
and
SETUP_COMPLETED=false
And was running the setup again. But no luck as it seems…
One thing i am not 100% sure if it is right: When i upload the whole folder with the new files and choose “merge” - the files that exist will be replaced, other files will stay there (for example my own templates). Afterwards i copy the changed custom.css and custom-pdf.css back from the 1.5.4 installation to the new 1.5.8
What about the version_sql_errors column besides the 1.5.4 entry? Is there a count or something.
Basically: the setup/updater just runs the database updates stored in the corresponding version files. After that the version is stored in the database. So I assume that the updater did not update all tables. Could you check if the ip_merchant_responses has a merchant_response_successful field? If not, run the following SQL commands:
ALTER TABLE `ip_merchant_responses`
ADD `merchant_response_successful` TINYINT(1) DEFAULT 1
AFTER `invoice_id`;
Then, to update your database to the latest version run the following SQL command:
What about the version_sql_errors column besides the 1.5.4 entry? Is there a count or something.
No, zero in every version_sql_errors column.
There was no “merchant_response_successful” field - so i ran the SQL commands. And now the version number is displayed correctly under “System settings → Updates”
Thank you!
So i can assume the update is now correctly finished? Can i double check that in some way?
Hello.
I have had the same bug and the database update stay at 1.5.5.
The problem come from unzipping. I don’t know why but in the folder
\application\modules\setup\sql
the last file was 028_1.5.5.sql
With a second unzip, the last file is correctly 031_1.5.8.sql
Hi, I just upgraded from 1.5.5 to 1.5.8 and I think I discovered a bug: removing a customer in the customer edit window, using the “delete” button doesn’t seem to work anymore and directs to a non existing page (and customer isn’t deleted)
Using delete from the options-dropdownbox in the view all customers window does work though.