On Feb 28, 2009, at 1:36 PM, Michal Charemza wrote:
A bit more to report... I found http://fabien.potencier.org/article/9/php-serialization-stack-traces-and-exceptions and I think I can store the validation report if I modify AgaviValidationReport to implement Serializable and include: public function serialize() { return serialize(array($this->argumentResults, $this->result, $this-incidents));} public function unserialize($serialized) { list($this->argumentResults, $this->result, $this->incidents) = unserialize($serialized); } (This removed the PDO exception, but I've still not managed to get the page after redirect to show the errors)
I fail to see why you'd want to store the validation report. However, the reason for the error is that somewhere in the code, a reference to a pdo object is stored. It may be that you're using an AgaviSingletonModel which would be in the request or that a validator stores a reference to an object that has a reference to a PDO connection. Hard to say without a look at your code, a detailed descrition or a minimal example. If you think this is an agavi bug, please send us instructions of how to reproduce this behavior - does it happen with all validators, a specific one, maybe even a custom one. Which type of database connection are you using etc. If you can check out the sampleapp and modify it to show your error, that would probably the best thing you could do - short of writing a unit test.
cheers felix
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
