Seeing as my provider has hit a wall and I've been unable to locate anything similar here thought I would open it up and ask if anyone has come across this little nugget? Any assistance I can pass on to them would be appreciated.
Description of Problem:
Building an intranet site and upon installation all appears well bar the table 'modx.site.content' isn't created therefore I am unable to add content to the site. I can create templates etc, just not documents.
Steps to Reproduce:
My provider has replicated the error externally and we think it is down to the charset element of the install being blank
For MODx to create database for tables, the mysql connection user needs to have db creation privileges. This is rarely seen with shared hosting plans (if I presume right) and the DB needs to be created manually before install of any php app really.
It's on a dedicated in-house server so there are should be no issues with it being shared hosting. I have purchased a server and configuration as per the specs through my providers whom have also installed the relevant MySQL; PHP and then loaded ModX. Evidently they came upon an issue with the database, created it and then progressed and whereas it does say completed successfully it appears not to have.
I'm pretty sure it's a case of not being able to see the wood for the trees (as the saying goes) and will revert your comment about db creation privileges although all other tables appear to have been created which would suggest that isn't the issue?
This bug bit me on installing new on MySQL 5.6.11. Apparently there are some BC breaks in that release regarding the behavior of sql_mode=STRICT_TRANS_TABLES and/or truncating max key length. You can disable the STRICT sql_mode or correct the key length of the uri column (set to 1000 but gets auto-truncated to 333 when using utf8 collations) to install successfully.
I'll get a fix in for a 2.2.8 patch release shortly.