Hi,

I checked my installation and the return-string of the page where the CB login module is shown is the right one and can be printed out in the CB login module. It seems that the string is just not being processed.

I disabled the Joomla login with a dirty core hack by emptying the default_login.php-view in com_user.

Regards,
Karlja

Well, on the page originally showing the Joomla login in the body, the CB login module is also shown. So by just disabling the Joomla login view, I do not have to do a second redirect and should therefore be able to have access to the right return string.

With the Joomla login (now disabled) the return after login worked perfectly fine but seems not to be processed right in the CB login module.
I looked into the http header of the login post operation and found that a different return string is passed on.

What additional task are performed on the return string and why?

Regards,
Karlja

krileon wrote:

Again, CB can't redirect two URLs deep; which when trying to access a protected URL a user is redirected to the protection page.

It doesn't need to.

CB can't redirect back to the URL which was previously attempted to access as a new redirect was performed sending user to protected page, which then can't be accessed because user is now logged in; so user is sent to frontpage (should be at least in most cases).

You can obtain a Joomla plugin which redirects from Joomlas protection page to CBs login page if you like, but still won't remedy your issue.

But this is how Joomla works, core functionality, out of the box. krileon, what myself and other users are saying, is that the CB login module is lacking core functionality that Joomla already has.

If I am using Joomla's core login module and try and access a restricted page, then I am redirected to the page I was trying to access after logging in.

This does not happen at all with CB, even though the correct base_64 encoded URL is in the URL.

If you want to see what we're talking about, I can probably setup a demo to prove to you that the CB login module is in fact lacking/not performing/breaking core functionality that Joomla has out of the box.

- vince

If you output all GET variables in the login module when being redirected to the login from a restricted site, you get a return string, which can be easily decoded back to the original URL, but using CB login module version 1.2 RC3 from February 2010, it says in line 673:
[code:1]echo '<input type="hidden" name="return" value="B:' . base64_encode( $login ) . '" />'."\n";[/code:1]

So the CB login module modifies the return string further and there seems to be a problem with the encoding / decoding of that string.
I tried just sending the original return string, but this is also not decoded correctly when logging in.

So the redirect on login is not a problem of remembering two URLs (since there is no second redirect before login), but seems to be processed different in the CB login module / component than in the Joomla core.

Hope you can help on this problem and maybe have an idea on why this different way is used.

Thank you.
Karlja