Greetings.
I apologise, this is not a true development question. It does involve the internals of XOOPS security however and I was not getting any responses posting in some of the other forums. I hope that by posting here, someone with knowledge of XOOPS internals might be able to help.
Can someone please explain to me what this is doing?
if (!$GLOBALS['xoopsSecurity']->check()) {
redirect_header($_POST['not_redirect'], 3, implode('<br />', $GLOBALS['xoopsSecurity']->getErrors()));
exit();
}
More specifically, what is the call to $GLOBALS['xoopsSecurity']->check() doing?
I just noticed that on one of my sites, I cannot register a request to be notified of events (like the Global "Notify me of blah blah blah" or sub-global-level like "Notify me when a new comment is posted for this item.").
When I hit "Update Now", it winds up re-directing me without saving the notification request.
I've traced it through this far:
When I hit "Update Now", the form executes notification_update.php from the XOOPS root.
I get as far as this section of notification_update.php:
if (!$GLOBALS['xoopsSecurity']->check()) {
redirect_header($_POST['not_redirect'], 3, implode('<br />', $GLOBALS['xoopsSecurity']->getErrors()));
exit();
}
where it takes the "true" path.
The call to $GLOBALS['xoopsSecurity']->getErrors() is returning an empty array (as near as I can tell).
I don't know enough about the internals of XOOPS to understand why this is failing. I have this working properly on another site. The biggest difference I can see between the two sites is the site that is working was a full install of XOOPS 2.0.13 whereas the site with broken notification is an upgrade to XOOPS 2.0.13.
Any help would be much appreciated. Thanks.
JP
