Modx Default Admin User Not Created after Successful Install. Can someone provide SQL Insert Statements (Tables, Columns) to create the Default Modx Admin User.
Background: After about 6 installs (traditional & advanced), providing write access to recommended directories and then setting all for write access; created database with User (all privileges). Whether using User account created or mySQL root password during install -- Always end up with NO User Account in Table: Manually inserted user via SQL into xxx_user <table>; then inserted into xxx_user_attributes (name, email). At Login Modx was able to Reset Password via email (email sent/pw changed) - Still no access to manager - but No Error, just remains at Login.
Install Notes:
database name & table prefix Changed from default (config's reflect this properly)
location: not in web root, installed within its own directory: www.mydomain.com/myModx/
System: VPS - Redhat Enterprise Linux 4ES; Apache version 2.0.64; MySQL client version: 5.1.45; Server version: 5.1.55; PHP 5.2.17; per server requirements docs: all extensions installed; configuration options verified (safe_mode off, register_globals off, magic_quotes_gpc off; memory_limit = 128M / Max_Execution_Time=120).
Can't wait to get this up and running - looks great. Assistance appreciated. Thank You. --Barbara--
Same problem here with a new Revo 2.2.4 install.
All tables are created, a user with id 1 is created but without username or email. password is a hash but seems not to be connected to the one entered for admin user on install.
All server requirements checked and ok.
Ok, after changing username in db via phpmyadmin i could log in using the username plus an empty string as password.
Than in the manager go to users and change password.
Problem fixed for me but I'd still say: that's not the way it should work.
[ed. note: chris@crnm last edited this post 14 years, 3 months ago.]
-
MODX Staff
- 2,502 Posts
Chris, this is the first time I've heard this report on an install. I'd love to hear more about any errors or server specs. Are you able to take a look at the server logs for the installation and see if there is anything that stands out? PHP or DB related errors? Are you able to reupload and do a clean install in another directory on your server to see if it occurs again? Failed installs are typically a sign of missing or corrupted files, incorrect permissions or incompatible server configs.
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub
Jay, I think I've seen a couple other reports of this same issue. It seems impossible that MODX could successfully create the user with no username or password, but apparently it can happen.
------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone:
http://bobsguides.com/modx.html
-
MODX Staff
- 2,502 Posts
Thanks Bob.
Chris, we'll need to see if we can't track down the source. We need the circumstances of the installs and full environment information for the servers/systems.
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub
Hi smashingred: sorry for getting back to this topic so late.
I did the same today again on the same server environment and had the same outcome: username blank and pw blank in database (that is: the pw hash in the db correlates to a blank pw).
So it is writing sth. into the db, but those strings are empty. The db is not running on localhost, but 127.0.0.1., port 3307. Collotation is utf8_unicode_ci, connection utf8. MySQL: 5.1.63-0+squeeze1
The install process before was rather bumpy: I had to manually chmod 0777 the config and cache dirs, had to manually copy the config.inc.php etc. And, maybe more important: I setup a wrong db name first and corrected it when the collotation could not be checked.
I could set you up with admin access to the modx install if you write me a pm w/ your mail address for you to could check all further system&environment settings in the manager.
Oh my dear. Now I'm seeing that php is loaded as a module, not via cgi as it should be for modx. That explains all the chmod problems I'm had. Don't know if it explains the problems in user creation as well.
[ed. note: chris@crnm last edited this post 14 years ago.]
My first guess would be mod_security.
------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone:
http://bobsguides.com/modx.html
Thanks BobRay. I'm not running mod_security ...
On our new fancy pants NGINX server we have this...
http://pastebin.com/vTu3Q4GC Here is my error log from install. WHat I had to do was grab an install that I know to be good, go in and grab the HASH and SALT and set the username. in the table there is an entry for user 1, but no info.
Current setup is CentOS / phpFPM NGINX / Rackspace Cloud Database
Just noticed this last few weeks.. this is fresh install on 2.2.6