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.

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

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

Login screen won't proceed to CMS (continuous loop)

Go to End

5 Posts   1614 Views


Community Member, 116 Posts

19 April 2011 at 12:48pm

Hey SilverStrippers,

Here's one that's got me stumped....

I've extended the Member object using DataObjectDecorator for a site I'm working on.

If I declare this extension in mysite/_config.php using Object::add_extension('Member','MemberExtension') - SilverStripe won't allow me to access the CMS. It just keeps telling me to login. (Yes I'm using setDefaultAdmin)

If I comment out the Object::add_extension line it lets me access the CMS fine.

See code here:

SS 2.4.3 / Mac OSX 10.5 / MAMP

Yes the session.save_path in Php.ini is writeable!


Forum Moderator, 1899 Posts

19 April 2011 at 9:06pm

Hi have you tried all the debugging methods?

there is probably an error that will give you a more descriptive description


Community Member, 116 Posts

20 April 2011 at 11:36am

Hi Swaiba,

Thanks for your post - I'm aware of all the debugging methods in SilverStripe.

Bump bump if anyone has any ideas - just confirming this is not an error, or code crashing. It's simply the Login screen not allowing me to "proceed" to the CMS as an admin user.

Something to do with using Object::add_extension on the Member object.


Community Member, 189 Posts

22 April 2011 at 3:00pm

I've had javascript/jQuery errors keep me from accessing the CMS in the past. Check firebug to see if there are any errors there. Just mentioning in case you were only looking for SS errors.

I would try a fresh 2.4.3 install with that same class and see if you get similar results.


Forum Moderator, 1391 Posts

25 April 2011 at 10:06pm

took me about 30 secs to test your code on my 245 test install - and it works like a charm, using defaultAdmin or not :-) So it must be something else ?