Here are my Contexts. Not much there.
http://radified.com/_gfx/02/modx_contexts.png
Your video (at time = 11:40) does not include a trip to the Contexts page, so I don’t know what to expect.
Radified,
VPS guide, Revo 206 Traditional, PHP 534, suPHP, MySQL 5151, Apache 2217, CentOS 5.5 on Virtuozzo VPS.
I may have found the source of the problem. I searched for info on how to create a MySQL database using utf8_unicode_ci collation(just like you use) .. using cPanel and/or phpMyAdmin.
This was more difficult than I thought. So I just install REVO with the default latin1_swedish_ci. I had asked my web hosting provider about how to create a new database with utf8_unicode_ci.. They are friendly seem eager to help.
I think they went ahead and CHANGED the default collation my modx database (to utf8_unicode_ci) after I had already created it and installed REVO using latin1_swedish_ci.
Does that sound like it could cause the glitches I am seeing?
By the way, do you know how to CREATE a (new) MySQL database with utf8_unicode_ci collation using either cPanel or pbpMyAdmin? .. or even command-line, since I have a VPS with ’root’ access. I searched the web for quite a while, but came up empty-handed.
Radified,
VPS guide, Revo 206 Traditional, PHP 534, suPHP, MySQL 5151, Apache 2217, CentOS 5.5 on Virtuozzo VPS.
I would try and re-install. this will involve deleting the tables in the current DB but this should be easily manageable phpmyadmin.
Yeah. Probably easier to just delete the whole database and create a new one.
Radified,
VPS guide, Revo 206 Traditional, PHP 534, suPHP, MySQL 5151, Apache 2217, CentOS 5.5 on Virtuozzo VPS.
When you create a new DB in PhpMyAdmin, I think it will simply ask you what collation you want to use.
You may need to set the MySQL server variables as well, however, (before you create the DB or install MODx) in the my.cnf file. Unfortunatly, there are a bunch of them that relate to character sets and they all default to Latin1 and latin1_swedish_ci.
You can usually see them by clicking on Server Variables on the PhpMyAdmin home screen.
Tech sppt at my web host edited the my.cnf file to set default collation to utf8_general_ci
but when i created a new database, it was still latin1_swedish_ci
even after i set collation to utf8_general_ci in phpMyAdmin, a the bottom of the Operatons, page, the database STILL was latin1_swedish_ci, as reported by modx Revolution during the install.
if i tried to set the Revolution install settings to anything besides latin1_swedish_ci, it would error.
i could only proceed by selecting the defaults in the modx setup installation as latin1 char set and latin1_swedish_ci
latin1_swedish_ci works, but i would at least like to know how to make it work with utf8_general_ci or utf8_unicode_ci .. for my own personal info.
maybe i’ll stumble upon the secret to this later.
Radified,
VPS guide, Revo 206 Traditional, PHP 534, suPHP, MySQL 5151, Apache 2217, CentOS 5.5 on Virtuozzo VPS.
Okay, I deleted and installed a completely new installation of REVO to a completely new directory, using a completely new database.
I had exactly the same problems as before, with nothing listed under tab.
But then I reviewed the installtion instructions again:
http://svn.modxcms.com/docs/display/revolution/Fresh+Installation
and chmodded the directories mentioned there as per guidance here:
http://modxcms.com/forums/index.php/topic,43923.0.html
and Presto! - I now have the icons listed below the Resources tab.
But .. I still have nothing listed under System > Contexts
So?? Where to now?
Radified,
VPS guide, Revo 206 Traditional, PHP 534, suPHP, MySQL 5151, Apache 2217, CentOS 5.5 on Virtuozzo VPS.
Ut oh, I hit my browser’s refresh button and got this error, which won’t seem to go away:
Fatal error: Cannot access protected property xPDOQuery_mysql::$sql in /home/radif2/public_html/revolution/core/xpdo/om/xpdoobject.class.php on line 285
I was just starting to make progress.
Radified,
VPS guide, Revo 206 Traditional, PHP 534, suPHP, MySQL 5151, Apache 2217, CentOS 5.5 on Virtuozzo VPS.
I wonder if the tech remembered to restart the server after making the changes. It sounds like he or she didn’t and the changes didn’t take effect.
I wonder if the tech remembered to restart the server after making the changes. It sounds like he or she didn’t and the changes didn’t take effect.
you’re very insightful.
actually the mysql server had died cuz they set collation to utf8_general_ci but left character set at latin1 and utf8_general_ci is NOT a valid collation setting for latin1 char set.
none of my databases were working, which is how i found it.
working now.
databases are freaking black magic.
Radified,
VPS guide, Revo 206 Traditional, PHP 534, suPHP, MySQL 5151, Apache 2217, CentOS 5.5 on Virtuozzo VPS.