-
- 289 Posts
Strange. Perhaps you should try a different charset when updating/installing MODx. When you install it, you can select it when you get to that step. When you update, select the advanced update option and try another DB encoding scheme. You should savely backup your data (MySQL) before you do so.
@MarkGHErnst
Developer at Adwise Internetmarketing, the Netherlands.
-
- 24 Posts
Yep, that was me. Same exact issue today attempting a clean install of RC4 on a brand new server.
-
- 24 Posts
Update: Like pumkin, I was also able to install 2.0.8 without a hitch on both of my servers.
The commonalities is see here are php 5.3.6 and Apache2 on CentOS (I’m running 5.5 final). Should I report this as a bug?
If your character set is blank in the config file, you need to fix that before upgrading. That is an old bug and the $database_connection_charset variable should never be blank. This is revealed as a bug only in recent updates to PHP (i.e. 5.3.6) where a bug in PDO_mysql driver was fixed to actually send the charset from the DSN to the driver. Now that it does this, a blank value is invalid, even though the error never appeared before because the charset was not being set by the driver.
-
- 7 Posts
Hi Jason
Thanks for the reply, may I just clarify whether you’re talking about the MODx config file or a config file for my sql / php settings on the server? Just to be clear, I am installing a new version in a totally clean db, not upgrading.
-
- 7 Posts
I’m a bit out of my depth here so forgive me if I’m asking silly questions. I’m just wondering, how does the installer ascertain the character set in the first place?
I’m used to the modx install process being: 1. Enter db host, username, pwd etc., test connection and get character sets/collations. Then step 2. Select char set and collation.
I’m not getting as far as step 2, it’s failing on 1, at which point there is no config file in core/config, and I haven’t told it which char set to use- so I guess my question is what defines the char set in step 1?