osCmax 2.5.3 Released

[ridexbuilder]

Caution: When I uzipped the package, the directory permissions have been set as 700, rather than the usual default of 755. This may give issues when uploaded to your server.

[RodneyB]

I went back and restored the database and then done the update again. It worked this time. I did do the update from the admin panel.

[ridexbuilder]

I went back and restored the database and then done the update again. It worked this time. I did do the update from the admin panel.

Well done - thus proving the full worth of backups.

[michael_s]

Caution: When I uzipped the package, the directory permissions have been set as 700, rather than the usual default of 755. This may give issues when uploaded to your server.

Not for me.

I just dl'd, unzipped to a server and all dirs are 755 all files 644 as always. Not seeing any differences anywhere.

[ridexbuilder]

Not for me.

I just dl'd, unzipped to a server and all dirs are 755 all files 644 as always. Not seeing any differences anywhere.

Hmm, weird. Is confused (easily done).

[tammynowa]

ok i did the update and this is what i got
1054 - Unknown column 'info_cg_hide' in 'field list'

SELECT information_id, information_title, information_url, information_target, parent_id, info_cg_hide FROM information WHERE visible='1' and show_in_infobox='1' and NOT find_in_set('0', info_cg_hide) and language_id='1' and information_group_id = '1' ORDER BY sort_order

[TEP STOP]
website is: A Whole Lotta Gourmet :
not sure what happen went from v2.5.2 to v2.5.3

[artrat]

Tammy, your post looks alot like rodneyB's above. Seems like the database wasnt properly upgraded. He sorted his TEP STOP by restore the backup he made then reran the database upgrade through the admin panel.

[tammynowa]

i did run upgrade thruugh the admin panel
5 times

[pgmarshall]

The upgrade script can not have run properly for you.

In the SQL for 2.5.2 to 2.5.3 file there is a line:

ALTER TABLE `information`

ADD COLUMN `info_cg_hide` varchar(255) NULL after `language_id`; Which obviously has not run on your store. You can run this line in phpMyAdmin or similar but I suspect that if this line did not run then the others will not have either. Not sure which version you installed originally ... 2.5.2? Can you restore the database to prior to the upgrade by using the backups ... then re-run the installer. If you have already tried this (ie. restoring the old version) then we may need to go down the phpMyAdmin route to manually patch your database. Regards.

[michael_s]

Tammy, Please provide some information regarding error output from the admin panel upgrade screen.

If queries are not executing, the error should be displayed in the output of the upgrade script when you run it. Restore your database backup and run the upgrade again. This time make sure to get the output of the upgrade script and post it here.

Please provide the mysql version your server is running.

Also, you should be able to look at your mysql server error log for the exact error that occurred during the script run. If you can provide that, it would be very helpful.