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've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Archive /

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

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

/db/build problems and Authentication errors, and more


Go to End


4 Posts   2555 Views

Avatar
tmcw

8 Posts

21 July 2007 at 5:22am

Edited: 21/07/2007 5:47am

(reposting)

I'm having a problem using /db/rebuild. When I go to that, I enter all my possible password combinations, and none of them work. Also, as a sidenote, this asks for a "username", while all other parts of the CMS refer to a firstname, nickname, and email, but never a username.

So, I try to reset the password by /admin/security/ and when I try that, nothing happens (when I click save), but there is a response from the Ajax call - just

ERROR:There has been an error
.

Is there any way to fix this or debug it? It's fairly serious because it might mean that I'm locked out of my own install when my cookie expires.

Avatar
tmcw

8 Posts

21 July 2007 at 5:56am

Edited: 21/07/2007 5:56am

Both bugs are temporarily averted by escaping from requireLogin() and just returning true.

Avatar
Willr

Forum Moderator, 5523 Posts

21 July 2007 at 1:33pm

you can also avert that problem by using dev mode while you need to do db/build. You can do this by adding this in the _config.php - Director::set_environment_type("dev"); you can read more about dev mode - http://doc.silverstripe.com/doku.php?id=devmode.

Avatar
Sigurd

Forum Moderator, 628 Posts

27 July 2007 at 2:42am

Edited: 27/07/2007 2:44am

Its possible the users set up in your member table are not quite right, and that the code to check you're an admin here, is different to the admin check elsewhere....

I suggest going into the code and seeing which part is returning false in terms of that user being an admin ... (if you have time!).