Page 1 of 1
Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Mon Nov 08, 2010 11:12 am
by calonthar
Hi
After upgrading from 1.8.2 to 1.9 using the install/upgrade.php script, I get the following PHP notice on top of every page (I use PHP 5.2.x):
Notice: Modification of internal data is deprecated: myname in lib/classes/class.cms_variables.php on line 46
Additionally, I am not able to login to the admin panel anymore! Every time I enter my username and password and click on the submit button, the site reloads without displaying any message about what went wrong. Using the password recovery has also no effect; after entering the username, the login page gets loaded without any mail sent to me.
I'd be glad if anyone could help, because now my page design is a bit messed up and I am not able to correct it as I cannot use the admin tool.
Regards
Calonthar
Re: Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Mon Nov 08, 2010 3:01 pm
by forbairt
Having a similar issue .. only upgraded a production server though ...
I'm assuming it'll be due to
For security reasons, and because it is not good practice for modules, UDTs or plugins to modify internal CMSMS™ variables we have made some core API changes. The {$gCms} smarty variable has been removed, and it is no longer possible for third party modules to use $gCms->variables to store config data. Additionally, the configuration data is now stored in an object once loaded, and setting data at runtime into the config structure is deprecated, and that ability will be removed at a later date.
I'll have to take a look at it later on though
Re: Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Mon Nov 08, 2010 3:10 pm
by RonnyK
Upgrading CGExtensions should solve this issue.
Ronny
Re: Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Mon Nov 08, 2010 3:13 pm
by forbairt
@Ronny ... just came back to post exactly that
Was about to start disabling extensions
Re: Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Mon Nov 08, 2010 4:38 pm
by calonthar
Disabling the Extensions (via phpMyAdmin) solved the issue with the warnings, but i still cannot login to the admin mode (this page here:
http://dysign.ch/cms/admin/ as you can see, entering arbitrary username and password doest not provoke an error message, it just returns to the same page)...
Re: Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Tue Nov 09, 2010 9:34 am
by forbairt
strangeness ... no errors when you were uploading the new files ?
Re: Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Tue Nov 09, 2010 9:59 am
by barboni
Tried to upgrade, but script stopped at page 1, showing blank page. Error log says: Fatal error: Class 'CMSModule' not found.
Then I tried to install and it went OK, but after that I was pointed to upgrade the schema, wich of course failed due to same 'CMSModule' error.
After that I made a fresh intallation and then imported old database, but again it forces me to upgrade schema...
The site is up, altho I had to remove some modules, but the encoding is messy, showing signs like Ä‘, and when I edit the content and replace the signs with regular ones they just don't change at front end.
One more thing: the Global Conten Block that exists in database just disapeared from admin, showing smarty error on front end.
I checked in lib/class folder and there is no class called CMSModule.
Re: Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Tue Nov 09, 2010 10:09 am
by Rolf
@ Barboni
Please check:
http://forum.cmsmadesimple.org/index.ph ... 822.0.html
It is a cetral post with problems and solutions with the 1.9 upgrade.
Hope this helps
Rolf
Re: Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Tue Nov 09, 2010 8:55 pm
by barboni
Yes it helped, thanks.
Re: Problems after Upgrading from 1.8.2 to 1.9 (Admin)
Posted: Thu Nov 11, 2010 2:11 pm
by calonthar
I was'nt able to solve the admin login issue with applying the update, so I installed the cms in a fresh new folder, connected to the existing db and now it works fine.
But it's still quite strange why it did not work on the update (I'll have to update a couple more 1.8 installations in the next days, hope that this will work without too much trouble...)