3
I'm probably not understanding you correctly, so I apologize if this post wastes your time.
Yes, there is a session created by XOOPS during authentication. The session look like this on my local debugger:
Beyond that, once you've included '/mainfile.php' at the top of any given php page, XOOPS sets up all kinds of nice object variables that contains important information. Specifically, there is an object called $XoopsUser that looks like this:
Notice that the 'vars' array contains both the user id and the hashed password of the current user. This is retained from page to page via the session. So, if a user comes to your XOOPS site, logs in, and then follows a link to another php page that, technically, isn't really apart of your XOOPS site, then all you need to do is include the mainfile.php file at the top of each of your php pages in your other application. You can then do things like:
$uid = !empty($xoopsUser) ? $xoopsUser->getVar("uid") : "";
$upw = !empty($xoopsUser) ? $xoopsUser->getVar("pass") : "";
to get access to these values.
For extra credit, if you've already gone to the trouble to add in an include for mainfile.php, you might as well give the site the
appearance of being a XOOPS module. You can do this with 2 more lines. In general, you can wrap any html (or php) page into your XOOPS layout by doing the following:
include_once '../mainfile.php'; // Load basic XOOPS environment (required).
include_once XOOPS_ROOT_PATH.'/header.php'; // Load page header (required).
?>
include XOOPS_ROOT_PATH . '/footer.php'; // Load page foot (required).
?>
Hope this helps...
