Issue upgrading from 4.0.2 to 4.1.0

[clnsdev]

Hello people,

unfortunately, my installation still can't digest the update starting from 4.0.2.

I first tried to update to 4.1.0, but even with version 4.1.1 get the following error messages (as in install.log):

successfully initialised DB Upgrade
verifying/creating constructive tasklist
checking field: banners append
found field append
checking field: zones prepend
found field prepend
checking field: zones append
found field append
#! database integrity check detected problems with the database
#! 3 fields to change

Installation "entry point" (OX) follows:

Name   From Version To Version Status Date    install_2.8.2 --- 2.8.2 UPGRADE COMPLETE  2011-01-31 18:17:40

What else could I try to solve?

Thanks in advance and keep up the good work!

[Matteo Beccati]

@clnsdev Could you please post here just the definition of the append/prepend fields in the banner and zones table? I.e. from SHOW CREATE TABLE ox_zones

[Richard Cook]

I upgraded using 4.1.1. I got no errors during the upgrade process. 

When I go to the product upgrade screen to view the version number I see.

 

You are currently using Revive Adserver v4.0.2 (warning: database is stamped as v4.1.1) 

 

Rich

 

[gabrielt]

@Matteo Beccati Just to confirm that the new 4.1.1 version solved the issue. Many thanks for fixing this promptly. PS: on the downloads page, the link to the 4.1.1 tar.gz version is pointing to the 4.1.0 version.

I am not facing the issue mentioned by @Richard Cook above. For me opening /www/admin/updates-product.php shows:

You are currently using Revive Adserver v4.1.1 running on nginx 1.12.1, PHP 7.1.11 and MySQL 5.6.37-82.2-log.

Cheers.

Edited October 29, 2017 by gabrielt

[mibert]

Hi Matteo,

 

thank you very much!!
Version 4.1.1. has performed the upgrade without any problem as usual.

Best regards and have a great Sunday

Michael

[clnsdev]

@Matteo Beccati

Hello Matteo,

those are the definitions of the fields:

banners:

`append` varchar(255) DEFAULT NULL,

`prepend` varchar(0) DEFAULT NULL, (I've once set it to 0 to avoid some SQL injections we had in our installation and strangely doesn't fire any warnings)

zones:

 `prepend` varchar(255) DEFAULT NULL,

 `append` varchar(255) DEFAULT NULL,

Thanks and have a nice day

[Matteo Beccati]

@clnsdev The field type definition should be "text NOT NULL", that's why Revive is complaining.

It is possible that varchar(0) is wrongly treated as being a text field, and if so that would be a bug.

[clnsdev]

@Matteo Beccati

Seems to be the right thing to do, thanks Matteo. I'll try an update tonight and report the result.

[clnsdev]

@Matteo Beccati

Hello there,

I confirm that after changing the fields mentioned above the update worked without a problem.

Cheers!