Yes, I tried it twice. It succeeds with no errors.NaN wrote:
Did you even execute the upgrade.php after uploading the files of CMSms 1.7.1?
PHP error after upgrading to CMS 1.7.1 and PHP 5.2.13
Re: PHP error after upgrading to CMS 1.7.1 and PHP 5.2.13
Re: PHP error after upgrading to CMS 1.7.1 and PHP 5.2.13
So if the column "secure" is still missed in your db Rolf migh be right that something does not work properly on upgrade. You might not have sufficient DB permissions to add columns etc. by scripts? I'm not that familar with DB settings but i've seen this several times with some providers. Upgrade scripts of modules etc. sometimes did not work because of limited DB access.
Or in some cases something got lost when uploading the files.
Maybe the file that is for upgrading the DB sheme is missed.
What value is stored in the table "version"? (should be 33 - just to be sure you check the right DB and/or all upgrade scripts has been executed)
Go to your table "content" and select "Structure".
At the bottom of the structure table you see "Add ... field(s) at/before/after ... ".
Select "Add 1 field at the end of the table".
Name it "secure" (column "Field").
Select "tinyint" as "type".
Leave the rest as it is.
Click "Save".
Since it will be only 1 or 0 that will be stored there the settings of the field are trivial.
The only really important thing is the Fieldname.
I cannot tell why exactly the upgrade script wasn't able to add the column maybe you should do some more investigations and/or talk to your provider since this will cause always trouble on updgrades when the db sheme is changed.
Or in some cases something got lost when uploading the files.
Maybe the file that is for upgrading the DB sheme is missed.
What value is stored in the table "version"? (should be 33 - just to be sure you check the right DB and/or all upgrade scripts has been executed)
You don't need a default value. You can just add the column by yourself using phpMyAdmin.tmar89 wrote:
Does anyone have the default value for this column so maybe I can just create it manually with default values?
Go to your table "content" and select "Structure".
At the bottom of the structure table you see "Add ... field(s) at/before/after ... ".
Select "Add 1 field at the end of the table".
Name it "secure" (column "Field").
Select "tinyint" as "type".
Leave the rest as it is.
Click "Save".
Since it will be only 1 or 0 that will be stored there the settings of the field are trivial.
The only really important thing is the Fieldname.
I cannot tell why exactly the upgrade script wasn't able to add the column maybe you should do some more investigations and/or talk to your provider since this will cause always trouble on updgrades when the db sheme is changed.
Last edited by NaN on Sun Aug 08, 2010 4:00 pm, edited 1 time in total.
Re: PHP error after upgrading to CMS 1.7.1 and PHP 5.2.13
33NaN wrote: What value is stored in the table "version"? (should be 33 - just to be sure you check the right DB and/or all upgrade scripts has been executed)
This worked and fixed the problem. Thanks!NaN wrote: You don't need a default value. You can just add the column by yourself using phpMyAdmin.
Go to your table "content" and select "Structure".
At the bottom of the structure table you see "Add ... field(s) at/before/after ... ".
Select "Add 1 field at the end of the table".
Name it "secure" (column "Field").
Select "tinyint" as "type".
Leave the rest as it is.
Click "Save".
Since it will be only 1 or 0 that will be stored there the settings of the field are trivial.
The only really important thing is the Fieldname.