Fatal error on install help

Hi,

I’m getting this error on install (below).
Been through all the FAQs, all directories writeable etc.

Any thing else I can try?
1.02 working fine.

Fatal error: Call to a member function execute() on a non-object in /directory/core/xpdo/om/mysql/xpdomanager.class.php on line 135


Installation Summary
Pre-installation tests were successful. Click Install below to continue.
Checking PHP for zlib dependency: OK!
Checking for SimpleXML: OK!
Checking PHP version: OK! Running: 5.2.11
Checking MySQL server version: OK! Running: 5.0.77-log
Checking MySQL client version: OK! Running: 5.0.77
Checking if memory limit is set to at least 24M: OK! Set to 128M
Checking if sessions are properly configured: OK!
Checking if core/cache directory exists: OK!
Checking if core/cache directory is writable: OK!
Checking if core/export directory exists: OK!
Checking if core/export directory is writable: OK!
Checking if core/packages directory exists: OK!
Checking if core/packages directory is writable: OK!
Checking if core/config/config.inc.php exists and is writable: OK!
Creating connection to the database: OK!

Can you provide more details about your environment, including platform and how the LAMP stack was installed? The information in the checks looks good, so I’m not sure what the problem might be. Although this looks curiously similar to http://modxcms.com/forums/index.php?topic=47456.0, I can’t imagine the same problem would be affecting 5.2.11.

Make sure you’ve checked http://svn.modxcms.com/docs/display/revolution/Troubleshooting+Installation (especially re: disabling eAccelerator), and if you uploaded files via FTP, that all files were uploaded properly (FTP failures cause more problems than you can imagine).

Thanks for the response,

I’m using a shared hosting environment. http://www.webfaction.com, who have never let me down and who I run multiple 1.02 installs on.
But with this I can’t control too much how the LAMP stack is installed.
I’ll register this with them also.

I’ve been through all the trouble shooting docs, changed what I can, including disabling eAccelerator via the .htaccess method shown.
Re: ftp’d and checked permissions. Same issue.

Will continue playing around.

Might have a look at http://modxcms.com/forums/index.php/topic,47389.msg279174.html#msg279174 and see if this is related.

Just tried the file changes as suggested by Garyn in that thread with no change in the error.

I have the same problem.
Worked through missing xpdo with the help of my host (quess).
Then the current problem.

I now get through preparation for setup, but it fails after everything passes the pre-install tests.
What does not happen is the creation of any database tables.

Here are two error messages from the setup logs for my failed install.

[23-Apr-2010 15:17:20] PHP Fatal error: Class ’xPDOManager_’ not found in /home/dviews/public_html/core/xpdo/xpdo.class.php on line 1152
[24-Apr-2010 22:17:23] PHP Fatal error: Call to a member function execute() on a non-object in /home/dviews/public_html/core/xpdo/om/mysql/xpdomanager.class.php on line 135

From what I can see looking at the source code, it appears that the missing element is the dbtype variable which should append after xPDOManager_. (line 1152/1151)
Is there a missing parameter somewhere?
That is as far as I have gotten tonight.

Make sure you’ve gone through everything at http://svn.modxcms.com/docs/display/revolution/Troubleshooting+Installation -- it sounds suspiciously like APC or eAccelerator are involved based on the errors you are reporting. Also, please confirm your PHP/MySQL (client and server) versions, what package of 2.0.0-RC1 you installed, and provide any other information that might be relevant.

I don’t know about eAcceleartor; not sure where to look for it.
But I think maybe the Zend Cache is running.

I am not sure how to turn that off.
Would header "no cache" directives have any affect on script caching?
(Seems unlikely, but I thought I would ask.)

modx-2.0.0-rc-1.zip

MySQL server version: 4.1.22-standard
MySQL client version: 4.1.22
Apache version: 1.3.41
PHP version: 5.2.10

@mei: TBH, I don’t know what to tell you, but I would not recommend using Revolution if you are stuck with old technology like MySQL 4.x. Why anyone would run MySQL 4.x alongside a reasonably up-to-date PHP version like 5.2.10 is beyond me.

You can just ask your hosting company to update MySQL ? I’ve did this recently...