SMF 1.0.3 + CPG 1.3.3: logout not working correct SMF 1.0.3 + CPG 1.3.3: logout not working correct
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

SMF 1.0.3 + CPG 1.3.3: logout not working correct

Started by Rasbelin, May 22, 2005, 05:55:21 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Rasbelin

Edit: site details removed as precaution.

Clicking to register or login via CPG works, but logout fails. Results in session verification error. As SMF 1.0.3 seemed to use a slightly different variable for login session requests, tried also changing it to the one used by SMF's logout routine. Didn't help.

Here are my changes to the SMF bridge file:


// Logout
function udb_logout_page()
{
    $target = 'index.php?action=logout;sesc=' . $context['session_id'];
    udb_redirect($target);
}


And the forum path change:


// Set this to the location of your Settings file:
$path = '../foorumi';


The rest is intact.

Any clues what I could do to get CPG pass on a valid session hash to SMF, so that it could verify I'm actually logged in and log me out as supposed to? :) Would really need this, as other than this, my SMF + CPG integration works great.

Joachim Müller

the logout link not working for cpg1.3.x bridged with smf (any version) is a know issue, sorry. It is being addressed in the devel version of coppermine (cpg1.4.x). For cpg1.3.x, there's no known fix. As a workaround, remove the logout link from your coppermine theme (edit themes/yourtheme/theme.php, find<!-- BEGIN logout -->
                        <a href="{LOGOUT_TGT}">{LOGOUT_LNK}</a>
<!-- END logout -->
and replace with<!-- BEGIN logout -->
                        <!--<a href="{LOGOUT_TGT}">{LOGOUT_LNK}</a>-->
<!-- END logout -->

Rasbelin

Okay, so the solution is what I pretty much expected it to be. :) Will go ahead and do that then. An update to 1.4-dev is out of question, as I want to wait until stable. Also requires working out the skin or wait for that one also to be updated by the author.

Thanks a lot! You can mark this solved now. :)