Looks like you will have to clear your current sessions. Check https://github.com/zendframework/zf2/issues/3700 and http://zend-framework-community.634137.n4.nabble.com/Release-Process-td4659063.html
Marco Pivetta http://twitter.com/Ocramius http://ocramius.github.com/ On 7 February 2013 10:08, avirdz [via Zend Framework Community] < ml-node+s634137n4659065...@n4.nabble.com> wrote: > I just updated to the new version and this exception was displayed. > > Stack Trace: > > Fatal error: Uncaught exception 'Zend\Session\Exception\RuntimeException' > with message 'Container cannot write to storage due to type mismatch' in > G:\virtual_host\dektacms\dk-library\Zend\Session\AbstractContainer.php:202 > Stack trace: #0 > G:\virtual_host\dektacms\dk-library\Zend\Session\AbstractContainer.php(404): > Zend\Session\AbstractContainer->verifyNamespace(false) #1 > G:\virtual_host\dektacms\dk-library\Zend\Stdlib\ArrayObject.php(82): > Zend\Session\AbstractContainer->offsetExists('identityData') #2 > G:\virtual_host\dektacms\dk-library\Zend\Authentication\Storage\Session.php(93): > Zend\Stdlib\ArrayObject->__isset('identityData') #3 > G:\virtual_host\dektacms\dk-library\Zend\Authentication\AuthenticationService.php(134): > Zend\Authentication\Storage\Session->isEmpty() #4 > G:\virtual_host\dektacms\dk-library\Dekta\Application.php(136): > Zend\Authentication\AuthenticationService->hasIdentity() #5 [internal > function]: Dekta\Application::Dekta\{closure}(Object(Zend\Mvc\MvcEvent)) #6 > G:\virtual_host\dektacms\dk-library\Zend\EventMana in > G:\virtual_host\dektacms\dk-library\Zend\Session\AbstractContainer.php on > line 202 > > This is my code, it was working in 2.1.0 version: > > $authentication = new AuthenticationService(); > $sessionManager = new SessionManager(); > $sessionManager->setName('sess_cookie'); > $authentication->setStorage(new Storage\Session('My', 'identityData', > $sessionManager)); > > $userModel = $serviceManager->get('Dekta\Permissions\UserModel'); > > if ($authentication->hasIdentity()) > { > $user = > $userModel->getUserById($authentication->getIdentity()->userId); > } > > Anyone has an idea to fix this error? > Thanks. > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://zend-framework-community.634137.n4.nabble.com/zf2-2-1-1-Container-cannot-write-to-storage-due-to-type-mismatch-tp4659065.html > To start a new topic under Zend Framework, email > ml-node+s634137n634138...@n4.nabble.com > To unsubscribe from Zend Framework Community, click > here<http://zend-framework-community.634137.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=634137&code=b2NyYW1pdXNAZ21haWwuY29tfDYzNDEzN3wxNzE0OTI1MTk4> > . > NAML<http://zend-framework-community.634137.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://zend-framework-community.634137.n4.nabble.com/Re-zf2-2-1-1-Container-cannot-write-to-storage-due-to-type-mismatch-tp4659066.html Sent from the Zend Framework mailing list archive at Nabble.com.
