I have a problem while trying to install MODx on an official host. There I'm allowed to create a new database only from the account admin'a page. I did create it there but when I install MODx I can see only this ref: "Creating DB and testing selection from it" (the messages I cite here may be some different from English ones because I give them in back translation into English). Of course, the script could not create any datebase there, so it showed me this recommendation: "Checking database: MODX cannot create a database. Pls create yout database manually and then try to continue." But I cannot go on because since the script did not pass the test, there is no button "Continue", only "Back". Does anybody know a way to avoid this obstacle?
-
☆ A M B ☆
- 24,524 Posts
If MODX cannot connect to the database you specified in the form, it will try to create it. That is why you are getting that error.
To connect to the database, you must have the server the database is on (usually "localhost", but not always), the username and password for the database, and the name of the database.
Some systems, when you create a database, adds its own parts, for example I may create a database with the name "modx", but the system will create the database with the name "sottwell_modx", and the username also will have the "sottwell_" added.
Sometimes MODX has trouble connecting to a database if your PHP does not have the correct date/timezone setting.
-
☆ A M B ☆
- 24,524 Posts
Most of the time it's an error of some kind in either the host, username, password or database name.
Check your server's error logs, the PHP error log and the MySQL database error logs, they may give some idea of where the problem is.
-
☆ A M B ☆
- 24,524 Posts
After it accepts the database, you need to provide a Manager login, email, and password.
-
☆ A M B ☆
- 24,524 Posts
So after you pass the two connection tests, the form for the manager user, email and password doesn't appear at the bottom of the page?
It didn't. But at last I decided to install an older version -- 2.2.6 instead of initial 2.2.13. Everything went smoothly and without any problem. Looks like it's an error in the installation script for the version 2.2.13.