☆ A M B ☆
MODX Staff
This is exactly the problem I’m having and is definitely related to my session problem, my version of PHP is 5.1.6. (I managed to finally find my error logs on my mac, lol)
Quote from: Mark at Dec 21, 2006, 01:57 AMWhich PHP 5 version is this?
A clean install on PHP 5 (under MAMP) renders the following error on every page, manager or frontend
Fatal error: Call to a member function bindValue() on a non-object in /Applications/MAMP/htdocs/modx_alpha/core/xpdo/xpdo.class.php on line 1482
[Sat Dec 23 01:28:23 2006] [error] PHP Warning: Memcache::get() [<a href='function.Memcache-get'>function.Memcache-get</a>]: cannot find connection identifier in /Library/WebServer/Documents/svn097/trunk/core/xpdo/cache/xpdocachemanager.class.php on line 124
[21-Dec-2006 22:47:52] PHP Warning: Unknown(): Unable to load dynamic library './php_pdo_mysql.so' - ./php_pdo_mysql.so: cannot open shared object file: No such file or directory in Unknown on line 0
and also that if you log in, use the manager message center to send me (Scotty Delicious) a message letting me know you were there.
Username:modx
Password:modx1234
MODX Staff
The bindValue error means that native PDO is configured but the PDO MySQL driver is not initializing properly. You need to work this out with your MAMP install. Unfortunately, I can’t fix the fact that they do not know how to compile PHP properly with the things they are distributing.
This is exactly the problem I’m having and is definitely related to my session problem, my version of PHP is 5.1.6. (I managed to finally find my error logs on my mac, lol)
This error is also showing up but doesn’t seem to be causing any fatal issues so far:
[Sat Dec 23 01:28:23 2006] [error] PHP Warning: Memcache::get() [<a href='function.Memcache-get'>function.Memcache-get</a>]: cannot find connection identifier in /Library/WebServer/Documents/svn097/trunk/core/xpdo/cache/xpdocachemanager.class.php on line 124
Hope that helps,
Garry
MODX Staff
MODX Staff
Well, I’ve done some basic testing of PDO (found at: http://wiki.cc/php/PDO_Basics) and I can access the database fine outside of MODx. Looking at my phpinfo, both the PDO and PDO mySQL driver appear to be loaded as well. Is there anything else that could cause issues with PDO?
The bindValue error means that native PDO is configured but the PDO MySQL driver is not initializing properly. You need to work this out with your MAMP install. Unfortunately, I can’t fix the fact that they do not know how to compile PHP properly with the things they are distributing.
The system settings have been there since the beginning so this is definitely an issue with the bindValue() error.
Also, the session problem should simply be related to the missing system settings. If you add those and clear all your cache files and try again, that problem should go away, unless again, it is being caused by the bindValue() error, which means PDO MySQL is not configured properly even though PDO is.
The warning is because apparently, you have the memcached extensions configured for PHP but your machine is not really running memcached? Is this running on a web cluster, or did someone just configure the memcached extension for no reason?Memcached is included in the Entropy distribution I’m using but I’m not using it ... so that’s okay.
As long as it doesn’t cause any serious downstream problems then I’m happy!
MODX Staff
The problem is with the PDOStatement class, which depends on the driver specific to a db. Did you try one of the examples that creates a prepared statement? This is where the failure point is occuring. For some reason, the queries are not producing a PDOStatement object...and I’m at a loss.
Well, I’ve done some basic testing of PDO (found at: http://wiki.cc/php/PDO_Basics) and I can access the database fine outside of MODx. Looking at my phpinfo, both the PDO and PDO mySQL driver appear to be loaded as well. Is there anything else that could cause issues with PDO?
I just need to change the way the db caching implementation is determined. Currently, if it sees that the memcached functions exist, it tries to automatically use it for caching database results. That’s actually a very good catch...
Memcached is included in the Entropy distribution I’m using but I’m not using it ... so that’s okay.