my life

If you get this error running

After a recent upgrade of Wordpress on Debian, my blog started spewing these errors everywhere, despite having run the upgrade script. The problem is that there are 2 upgrade scripts. Why they don’t both get executed is beyond me.

To fix it, run http://example.com/wordpress/wp-admin/upgrade.php (Not, http://example.com/wordpress/upgrade.php, which you’ve already run).

Then, be a Good Samaritan, and help fix the 19,500 blogs broken by this error.

There’s no way to natively setup the starting offset for AUTO_INCREMENT columns in propel. Ideally, you would just set autoIncrement=”100000″ for an offset of 100000, but unfortunately they expect a boolean argument. To get around this, edit data/sql/sqldb.map and add an entry contrib.sql=propel and edit a file in data/sql/contrib.sql.

Add the following to the file:

configure mout points in /etc/exports and when done, run

If you are using ACLs, make sure you add the acl option to the exported filesystem options in exports.

Just run…

I upgraded to a newer version of Symfony today (v1.0.6) and had a hell of time getting the trivial task of connecting to the database working.

I was able to obtain a connection, by doing


$databaseManager = new sfDatabaseManager();
$databaseManager->initialize();
$con = $databaseManager->getDatabase('propel');


but that’s not the ideal way, and not the way symfony gets the database handle.


$con = Propel::getConnection('propel');
on the otherhand throws an excpetion.

First, it was important to check that config/schema.xml is correct

All that was good. But for some reason sfPropelAutoload was not geting loaded.

If I manually included it


include './lib/symfony-1.0.7/lib/addon/propel/sfPropelAutoload.php'It was clearly listed in the autoloader.yml


it would work, but still not desirable.

The following was in my autoloader config,

but it still wouldn’t load my sfPropelAutoload class. Adding the following made it start working…

I was getting this error today on a new Symfony project. The problem was that I had defined the schema in the schema.xml file, but there was a conflicting schema.yml file that sat empty. Removing (