Modx ошибка 500 при установке

Common Problems¶

First off, make sure:

• You have eAccelerator disabled during install. eAccelerator can cause problems when doing the heavy lifting during the install process.
• You followed all the directions here for your distribution.
• You are using at least PHP 5.1.1+, but not 5.1.6 or 5.2.0
• You are using MySQL later than 4.1.20, but not any iteration of MySQL 5.0.51 (including 5.0.51a).
• Clear the core/cache/ directory entirely before starting setup; sometimes improper file permissions can cause issues.
• Clear your browser cache and cookies

PDO Error Messages¶

If you are getting PDO-related error messages during install, before proceeding to specific error messages as below, please confirm that your PDO configuration is setup correctly. You can do so by running this code (replace user/password/database/host with your setup):

<?php
/* Connect to an ODBC database using driver invocation */
$dsn = 'mysql:dbname=testdb;host=localhost';
$user = 'dbuser';
$password = 'dbpass';

try {
  $dbh = new PDO($dsn, $user, $password);
} catch (PDOException $e) {
  echo 'Connection failed: ' . $e->getMessage();
}
?>

If this fails, then your PDO setup is not configured correctly.

Common Errors¶

Here are some common problems that might occur during installation and their solutions:

«I get a blank white screen instead of the options page!»¶

You probably copied config.inc.tpl to config.inc.php, which is incorrect. Make the config.inc.php file an empty, writable file.

If you renamed the config.inc.tpl to config.inc.php, rename it back to config.inc.tpl and create a blank file named config.inc.php that is writable.

«I clicked install and got a blank white screen!»¶

Make sure your memory_limit setting in php.ini is set to at least 32M. For slower servers, you might need to up it to 64M.

«Cannot connect to database» in the database options page¶

One of the common causes of this problem is that you’re using a non-standard port for MySQL. Try putting this syntax into the hostname field (replacing the data with your mysql server’s host and port):

my.database.com;port=3307

Warning: PDO::__construct() [pdo.—construct]: [2002] Argument invalid (trying to connect via unix://) OR «Checking database:Could not connect to the mysql server.»¶

This means your MySQL socket is incorrectly configured. Usually this can be remedied by adding to (or updating) your php.ini:

mysql.default_socket=/path/to/my/mysql.sock
mysqli.default_socket=/path/to/my/mysql.sock
pdo_mysql.default_socket=/path/to/my/mysql.sock

The login page keeps redirecting me back to the login screen with no error¶

This can happen with older Revolution beta installs. To fix it, delete the following 3 system settings from the DB table [prefix]_system_settings (where prefix is your table prefix):

• session_name
• session_cookie_path
• session_cookie_domain

Then delete the core/cache/config.cache.php file.

Unless, of course, you’ve changed these explicitly for some purpose of your own.

Things sometimes don’t load, the page flakes out, etc (eAccelerator)¶

Are you running eAccelerator? In some server configurations, this can cause problems. You might need to disable it. You can do so via your php.ini:

eaccelerator.enable = 0;
eaccelerator.optimizer = 0;
eaccelerator.debug = 0;

or in your .htaccess in the modx root directory, if your server supports php_flag server directives:

php_flag eaccelerator.enable 0
php_flag eaccelerator.optimizer 0
php_flag eaccelerator.debug 0

General weirdness in the Manager (not eAccelerator)¶

On some systems, especially with shared hosting, there can be a problem with the compress_js and/or compress_css System Settings. Go to System -> System Settings and type ‘compress’ (without the quotes) in the search box at the upper right. Turn the two settings off, then log out, delete all files in the core/cache directory, clear your browser cache and cookies, and log back in.

If the Manager is messed up enough that you can’t change the settings, see the note below about changing the two System Settings in the modx_system_settings table in the database with PhpMyAdmin.

Resource / Elements / File tree not appearing¶

Additional, page «flake outs» may stem from items stored within your own browser’s cache, which may result with the resource / elements / file tree not appearing due to old versions of javascript and other files being utilized on the client side. This can be verified by accessing the manager with a browser not previously utilized in doing so.

The simple fix: clear your browser’s cache, and log back into the manager.

A more complete solution:

1. Under System Clear Cache
2. Under Security Flush Permissions and then Flush Sessions
3. This will dump everything and log you out
4. Last step Clear your browser cache

I can’t login to the manager after installing!¶

If you’re redirecting back to the login screen every time, try setting this in your .htaccess file in the root of your MODX install:

php_value session.auto_start 0

Could not connect to the database server. Check the connection properties and try again. Access Denied¶

Often on shared hosting, if you create a username for your database with an underscore (_) in it, it will cause problems. Ensure your database username does not contain an underscore, and try again.

More common issues to come…

The manager displays as plain text after installation¶

The MODX manager loads compressed CSS and JS assets. Some server configuration See «JS Errors in the Manager due to Error 4

The Manager displays as plain text, Manager parts are missing, or there are JavaScript 400 Errors in the Manager¶

If your MODX manager is not loading properly due to 400 errors in the manager when trying to load the Google Minify-compressed JavaScript code, this is likely due to a server misconfiguration on your end. If this cannot be rectified from a server angle, you can manually disable JS and CSS compression the following way:

1. Go into the DB using PhpMyAdmin and find the table_prefix_system_settings table (table_prefix is usually modx).
2. Find the rows with key compress_js and compress_css and set their value to 0 and save them.
3. Empty your core/cache/ directory.
4. Clear your browser cache and cookies
5. Log in to the manager.

This will allow you to use the manager without JS and CSS compression.

Manager parts are missing, undefined language strings, or there are JavaScript 500 Errors in the Manager¶

1. Make sure your connectors/ folder has 0755 permission

Still Having Issues?¶

If you’re still having problems, post your error and your server environment information in our forums here, and we’ll try and address your issue as soon as possible.

Open COllective

Support the team building MODX with a monthly donation.

The budget raised through OpenCollective is transparent, including payouts, and any contributor can apply to be paid for their work on MODX.

Backers

Budget

$407 per month—let’s make that $500!

Learn more

Summary

MODX installer fails and produces a 500 error when STRICT_TRANS_TABLES is enabled in MYSQL. This issue was previously discussed here: #2085.

Step to reproduce

Enable Strict SQL Mode in MYSQL’s /etc/my.cnf file => global sqlmode='STRICT_TRANS_TABLES' . OS X users may also need to check /usr/local/mysql/my.cnf and /usr/local/Cellar/mysql/5.x.xx/my.cnf (if installed with Homebrew).

Observed behaviour

On localhost, the installer stops immediately and outputs : Fatal error: Class 'xPDODriver_' not found in <core_path>/xpdo/xpdo.class.php on line 1880. On a Virtual Host, the installer proceeds until the summary step and produces a 500 error on the next. In the latter case, some tables are created and others are not.

A few errors found in the installer logs:

[2015-12-31 03:51:27] (ERROR @ /setup/index.php) Could not create table `modx_system_settings`
SQL: CREATE TABLE `modx_system_settings` (`key` VARCHAR(50) NOT NULL DEFAULT '', `value` TEXT NOT NULL, `xtype` VARCHAR(75) NOT NULL DEFAULT 'textfield', `namespace` VARCHAR(40) NOT NULL DEFAULT 'core', `area` VARCHAR(255) NOT NULL DEFAULT '', `editedon` TIMESTAMP NOT NULL ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (`key`)) ENGINE=MyISAM
ERROR: Array
(
    [0] => 42000
    [1] => 1067
    [2] => Invalid default value for 'editedon'
)

[2015-12-31 03:51:28] (ERROR @ /setup/index.php) Error 42S02 executing statement: 
Array
(
    [0] => 42S02
    [1] => 1146
    [2] => Table 'modx.modx_system_settings' doesn't exist
)

[2015-12-31 03:51:28] (ERROR @ /setup/index.php) Error saving vehicle object of class modSystemSetting; criteria: Array
(
    [key] => access_context_enabled
)
...

A few errors found in the server log:

[Wed Dec 30 12:28:47.365884 2015] [:error] [pid 24378] [client 127.0.0.1:53329] PHP   7. xPDOManager_mysql->createObjectContainer() <modx_path>/setup/includes/tables_create.php:116, referer: http://modx.kleverr.dev/setup/index.php?action=summary

[Thu Dec 31 03:51:27.227113 2015] [:error] [pid 32129] [client 127.0.0.1:63055] PHP Notice:  Undefined index: primary in /<core_path>/xpdo/om/mysql/xpdomanager.class.php on line 462, referer: http://modx.kleverr.dev/setup/index.php?action=summary

[Thu Dec 31 03:51:27.232336 2015] [:error] [pid 32129] [client 127.0.0.1:63055] PHP Notice:  Undefined index: unique in <core_path>/xpdo/om/mysql/xpdomanager.class.php on line 462, referer: http://modx.kleverr.dev/setup/index.php?action=summary

Expected behaviour

MODX should be installable when MYSQL Strict SQL Mode is ON

Environment

MODX 2.4.x, Apache 2.4.16, PHP 5.5.X, 5.6.16, MYSQL 5.7.10 Homebrew, OS X El Capitan

Зачастую при необдуманном выборе хостинг-провайдера, в последующем, при возникновении каких-то ограничений или дискомфорта в использовании хостинга – многие решаются перенести свой сайт в другую хостинг-компанию, например, в Beget.

Но при, казалось бы, простом и успешном переносе сайта, находящегося на CMS MODX Revolution, можно столкнуться с рядом ошибок. Одна из них – «500 Error Site temporarily unavailable».

Эта же ошибка возникла и у меня при переносе, и сейчас я расскажу, как быстро с ней справиться.

1. Итак, первое, что вам необходимо сделать – это подключиться к вашему сайту по FTP.

2. Затем перейдите в папку /core/ и удалите в ней папку cache.

3. Третьим шагом будет проверка корректности указанных данных для подключения к базе данных. Для этого откройте файл config.inc.php в папке /core/config/.

Здесь нас интересуют эти строки:

$database_type = 'mysql'; // Тип базы данных 
$database_server = 'localhost'; // Сервер базы данных 
$database_user = ''; // Пользователь базы данных 
$database_password = ''; // Пароль базы данных 
$dbase = ''; // Название базы данных 
$database_dsn = 'mysql:host=localhost;dbname=название базы данных;charset=utf8'; 

Тип и сервер базы данных уточните у своего хостинг-провайдера, но чаще всего они именно такие, какие по умолчанию указаны в файле.

Пользователь и название базы данных чаще всего одинаковые, но этот момент так же уточните у своего хостинг-провайдера.

Обратите внимание, что в последней строке также указывается название базы данных. В моем случае все было сделано, но именно в ней я забыл указать название базы данных и из-за этого не мог зайти в панель управления сайтом.

4. И завершающим шагом будет прописывание корректного пути к папкам от корня сервера в файлах:

config.core.php (корневая папка /);
config.inc.php (папка /core/config/);
config.core.php (папка /connectors/);
config.core.php (папка /manager/).

Во всех файлах, вы ищите что то типа:

/home/s/pandogecom/www.pandoge.com/core/

Здесь вам необходимо изменить часть «/home/s/pandogecom/www.pandoge.com» на правильную.

О том, как узнать полный путь от корня сервера, читайте в этой статье.

В некоторых файлах замену нужно произвести в нескольких местах. Не торопитесь, будьте внимательны – и все у вас получится!