Re: roles unserialize exception after upgrading to 1.1.3
"Danny" <[email protected]>
| Newsgroups | gmane.comp.cms.xaraya.user |
|---|---|
| Organization | Xaraya |
| Message-ID | <[email protected]> |
Any news on this topic? After upgrading to 1.1.3 I also have no access to the modify config tab in roles, it throws out the following error: http://mydomain.com/index.php/base?code=8&exception=At:%20/is/htdocs/wp1073613www/modules/roles/xaradmin/modifyconfig.php%20(Line:%2045)%0AUndefined%20variable:%20adminpriv&product=App%20-%20Core&component=Roles&func=systemexit Thanks, Danny "Ryan Walker" <[email protected]> schrieb im Newsbeitrag news:mailman.1378.1179161447.5440.xaraya_user-gn8pmO+6nsymdvSpIQae8A@public.gmane.org > update: I was able to get my registration form working. Still can't > access the modify config tab in roles, but it's not urgent anymore... > > > > Ryan Walker wrote: >> After upgrading a site from 1.0.1 to 1.1.3, I'm getting an unserialize >> exception in the modify config tab in roles: >> >> base?code=8&exception=At:%20/path/to/modules/roles/xaradmin/modifyconfig.php%20(Line:%20121) >> %0Aunserialize():%20Argument%20is%20not%20a%20string&product=App%20-%20Core&component=Roles&func=systemexit >> >> This bug looks to be relevant: >> http://bugs.xaraya.com/show_bug.cgi?id=5911 >> >> So apparently an attempt was made to fix this prior to the 1.1.3 release, >> but it looks like there's still a problem. I reopened the bug but I'm a >> little desperate for a quick fix, because I'm probably not going to be >> able to get my registration form back online without the modify config >> tab in roles (?). >> I have DD in my registration form. Still getting my head around how to >> get the DD fields back in my reg form... it might just be a matter of >> moving things from roles templates to registration templates, but I'd >> feel better about my progress if I could see the modify config in roles. >> >> Please let me know if you've run into this and if there's a fix I can >> implement. I tried an earlier patch attached to the bug, but it didn't >> help. >> >> Many thanks, >> Ryan >> >> >> >> > > > -- > Ryan Walker > www.WebCommunicate.net: > Insights and resources for effective websites. > >