mysql auto_increment settings and modx

[mightydok]

Summary

With MySQL server settings:

# Autoincrement
auto_increment_increment=2
auto_increment_offset=2

Default modx installation don`t work

Step to reproduce

Add settings below to my.cnf:

# Autoincrement
auto_increment_increment=2
auto_increment_offset=2

Restart mysql
Install MODx

Observed behavior

After install i get 503 error at main page with error below in error.log:

[2017-04-24 00:03:15] (FATAL) The requested resource has no valid content type specified.
[2017-04-24 00:03:24] (FATAL) The requested resource has no valid content type specified.
[2017-04-24 00:16:16] (FATAL) The requested resource has no valid content type specified.
[2017-04-24 00:16:18] (FATAL) The requested resource has no valid content type specified.
[2017-04-24 00:16:47] (FATAL) The requested resource has no valid content type specified.
[2017-04-24 00:16:48] (FATAL) The requested resource has no valid content type specified.
[2017-04-24 00:16:48] (FATAL) The requested resource has no valid content type specified.
[2017-04-24 00:16:48] (FATAL) The requested resource has no valid content type specified.
[2017-04-24 00:16:48] (FATAL) The requested resource has no valid content type specified.

Expected behavior

Site with modx works

Environment

MODx 2.5.7
Centos 6
MySQL 5.5
ISPConfig 3
PHP 5.4

[OptimusCrime]

I belive this is because MODX expects the first content type to have ID 1 and be HTML. Perhaps it could be possible to use the last_insert_id instead of hard coding this dependency. However, may I ask why you have these partcular settings? Are there any reasons for having them?

[mightydok]

@OptimusCrime sometimes when using master-master replication in MySQL, you need to use these options if the second master server also writes data.

[OptimusCrime]

Okey, I was just wondering. I guess the error comes from this default value in the modResource table:

revolution/core/model/modx/mysql/modresource.map.inc.php

Line 50 in 72104bd

'content_type' => 1,

Unless this is changed upon creating a resource it will trigger the error you are seeing. I suggest the following changes:

• Have either a system setting for default content type, or hard code this to be text/html
• If you attempt to delete a content type, check if any resources have the content type assigned and disallow deletion

Comments?

[mightydok]

BTW this file already have

revolution/core/model/modx/mysql/modresource.map.inc.php

Line 15 in 72104bd

'contentType' => 'text/html',

contentType definition. Why MODx need second one?

[OptimusCrime]

Hmm, that I do not know. I'll take a look when I have more time. I am not sure how the handling there is implemented. May be some BC stuff?

[Mark-H]

That's legacy from evo iirc.

Is the fatal error happening on all resources or only the one created by the installer?

[mightydok]

@Mark-H did not check

[pixelchutes]

That's legacy from evo iirc.

content_type does not appear to be a valid column from Evo. The only Evo columns containing "content" are these 3:

Compared to Revo's:

According to the code, it seems to be a simple join back to modx_content_type table (e.g. modContentType):

[Mark-H]

So contentType is the legacy from evo, and content_type is the newer one that points to the content types as we know them today ;)

[pixelchutes]

So if the problem is indeed with content_type default value of 1 on modResource, how does that involve the auto inc setting(s) in question?

@mightydok what IDs do you show in modx_content_type? (e.g. do you have odd numbers?)

[OptimusCrime]

I belive the content types start with ID 2 (offset) and are incremented by 2 every time (increment). Either way, it is pretty obvious that hard coding the resource type ID here is a bad idea.

[mightydok]

@OptimusCrime agreed
@pixelchutes Optimus wrote correct info