Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

Archive /

Our old forums are still available as a read-only archive.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo

2.3.0 RC1 Upgrade


Go to End


5 Posts   1846 Views

Avatar
Fuzz10

Community Member, 791 Posts

13 November 2008 at 10:27pm

Hi ,

Maybe it's just me , but I can't upgrade any of our sites to 2.3.0 RC1 .... A clean install works perfectly , but upgrading an existing site seems impossible.

On some sites , the front-end site will run correctly, but on all sites it refuses to let me login to the system (so no db/build and no login to the CMS) .. It throws a generic "The website server has not been able to respond to your request."....

Is this upgrade supposed to be 100 procent backwards compatible or do I need to change things I don't know about ? ;-)

Avatar
Fuzz10

Community Member, 791 Posts

18 November 2008 at 4:46am

Edited: 18/11/2008 4:47am

Okay. Got a bit further with this.

Discovered 1 thing :
- It seems you need to force the system in <DEV> mode before trying /dev/build , otherwise it will try to run a query on the member table which includes the "LockedOutUntil" field , which does not exist because it gets added by running /dev/build.. HarHar.. ;-)

Currently upgraded 1 site including the blog-module on our development server, it seems to run fine.

Having troubles with the gallery module , but I did not spend time on finding a solution to that.

Will update this thread with my findings....

Avatar
Ingo

Forum Moderator, 801 Posts

29 November 2008 at 9:34pm

Hey Lars,

> Is this upgrade supposed to be 100 procent backwards compatible or do I need to change things I don't know about ? ;-)
Not necessarily, as its a major release. Of course it would be ideal, but not always feasible. Your best shot is to check http://doc.silverstripe.com/doku.php?id=upgrading - although that page needs some attention as well before 2.3 release. Another option is http://open.silverstripe.com/wiki/ChangeLog/2.3.0, so you can at least see all the API changes and "deprecated" messages.

> It seems you need to force the system in <DEV> mode before trying /dev/build , otherwise it will try to run a query on the member table which includes the "LockedOutUntil" field , which does not exist because it gets added by running /dev/build.. HarHar.. ;-)
Changeset in question is: http://open.silverstripe.com/changeset/53466 - which was indeed not in 2.2.3! I've added a bug in http://open.silverstripe.com/ticket/3171

> It throws a generic "The website server has not been able to respond to your request."...
We're now forcing dev-mode through the installer, so if you're using it to upgrade you should see those errors.

Avatar
Fuzz10

Community Member, 791 Posts

1 December 2008 at 10:40pm

Hi Ingo,

Thanks for the feedback.

I really feel we should try to keep everything backwards-compatible. Upgrading all of our sites to 2. 3 is going to be quite a bitch for us ...

For example when phasing out classes , please do not throw them away (e.g. Email_Template).
Why not just deprecate them and phase them out slowly ?

Avatar
Ingo

Forum Moderator, 801 Posts

5 December 2008 at 5:52pm

> It seems you need to force the system in <DEV> mode before trying /dev/build , otherwise it will try to run a query on the member table which includes the "LockedOutUntil" field , which does not exist because it gets added by running /dev/build.. HarHar.. ;-)
Thats fixed now :)