Bug #6718

UnexpectedValueException thrown in file Session.php

Added by Georg Ortner over 11 years ago. Updated about 11 years ago.

-- undefined --
Start date:
Due date:
% Done:


Estimated time:
PHP Version:
Has patch:


Object not found
6 SplObjectStorage::offsetGet(F3\Test\Domain\Model\Category_AOPProxy_Development)
5 F3\FLOW3\Persistence\Session::getIdentifierByObject(F3\Test\Domain\Model\Category_AOPProxy_Development)
4 F3\FLOW3\Persistence\Session::unregisterReconstitutedEntity(F3\Test\Domain\Model\Category_AOPProxy_Development)
3 F3\FLOW3\Persistence\PersistenceManager::persistAll()
2 F3\FLOW3\Core\Bootstrap::run()
1 require("/var/www/mydomain.dev/Packages/Framework/FLOW3/Scripts/FLOW3.php")

This happens when the remove() Method of a repository is called. But still the Object is removed afterward.

public function createAction() {
$object = $this->objectManager->create("F3\Test\Domain\Model\Category");

public function removeAction( \F3\Test\Domain\Model\Category $category ) {

I'm using latest revision at this time and mysql as persistance backend.


Updated by Karsten Dambekalns over 11 years ago

  • Status changed from New to Accepted
  • Assignee set to Karsten Dambekalns

Updated by Karsten Dambekalns over 11 years ago

  • Status changed from Accepted to Needs Feedback
  • Target version set to 1.0 alpha 8

Please test with current SVN, this sounds familiar and should be fixed as of now.


Updated by Georg Ortner over 11 years ago

Thanks this seems to be fixed now, but there is something broken with the Session now.

Object "F3\FLOW3\Object\SessionRegistry" is not registered.
5 F3\FLOW3\Object\Container\AbstractObjectContainer::get("F3\FLOW3\Object\SessionRegistry")
4 call_user_func_array(array, array)
3 F3\FLOW3\Object\ObjectManager::get("F3\FLOW3\Object\SessionRegistry")
2 F3\FLOW3\Core\Bootstrap::run()
1 require("/var/www/mydomain.dev/Packages/Framework/FLOW3/Scripts/FLOW3.php")

Updated by Karsten Dambekalns over 11 years ago

  • Status changed from Needs Feedback to Resolved
  • % Done changed from 0 to 100

Great to see that fixed. The SessionRegistry problem is known and will be fixed by middle of next week at the latest (but it's unrelated to this particular issue).

Also available in: Atom PDF