Mambo <-> SMF installation oddity

[Kindred]

Hey, Orstio...   

I normally don't like to make new topics, but this is not really so much of a bug as something strange. So, rather than bury this in the other thread, I'm doing the evil thing and starting a new one.

I was helping Nexius with his Mambo-SMF integration and while testing it, came across something with has me a little confused.

You mentioned a check box, etc feature that you added to the 2.04 version of the mod.
So, I install and modify the bridge to get it owrking for Nexius...  register a new user to test it out and see the checkbox screen...
and now I realize what everyone else was commenting about earlier.

The reg page appears to be completely within SMF. It uses the SMF theme, withour wrapping the Mambo stuff around it. and when you've completed the registration, it drops you into the SMF menu, outside of mambo.

Now, this was odd, because I'd never seen this behaviour.
So, I went back to my site to test it out and got even more confused.
When I register as a user on my site, it takes me to (what appears to be) the mambo internal registration page. Definitely within the mambo wrappings and when completed, it dumps to a mambo page that reminds me that I need to check my email for an activation letter.

The only thing that I can think to account for the differences is Nexius installation is a clean one, at 2.04.  I have been upgrading as the releases came out from 2.00 up... (uninstalling the old and then installing the new.)

Any explanation on why this could be happening or how to work around it?

And while I'm on the topic...  You mentioned someone had integrated the SMF bridge into the Community Builder components...    are you going to work within that framework as well?

[Orstio]

The reg page appears to be completely within SMF. It uses the SMF theme, withour wrapping the Mambo stuff around it. and when you've completed the registration, it drops you into the SMF menu, outside of mambo.

That's completely wrong.  The registration should look like the Mambo registration, not the SMF registration.  When you click on the registration link, it should take you to http://www.your-url.com/index.php?option=com_smf_registration&task=register.

When I register as a user on my site, it takes me to (what appears to be) the mambo internal registration page. Definitely within the mambo wrappings and when completed, it dumps to a mambo page that reminds me that I need to check my email for an activation letter.

That is correct.

I just went through all the readme's, and you're right, there is a part missing from the login module readme:

Recommended:

In your SMF Theme, you'll probably want to change in index.english.php:

$txt['welcome_guest'] = 'Welcome, <b>' . $txt[28] . '</b>. Please <a href="' . $scripturl . '?action=login">login</a> or <a href="' . $scripturl . '?action=register">register</a>.';

to:

$txt['welcome_guest'] = 'Welcome, <b>' . $txt[28] . '</b>. Please login or <a href="http://www.your-mambo-installation.com/directory/index.php?option=com_smf_registration&task=register">register</a>.';

You may also want to search through your index.template.php, and make the following changes:

change:

action=login2

to:

action=mambo_login

change:

action=logout

to:

action=mambo_logout

I'll make sure this is included.

And while I'm on the topic...  You mentioned someone had integrated the SMF bridge into the Community Builder components...    are you going to work within that framework as well?

As far as I know, (unless you are referring to Marcnyc's work), that project is altering both SMF and Mambo to work together.  I don't mind changes to themes and templates, which are meant to be changed, but I do not want to get into altering SMF source or Mambo core files.  Once you start getting into modifying sources, it creates a bigger mess as soon as either software gets upgraded.  With talk of Mambo 4.5.2 in development, and the release of SMF 1.0, all those modified sources would have to be updated as well.

I would rather just a bridge, so that if an end user decides to upgrade his Mambo or SMF, and the bridge breaks, at least both Mambo and SMF are still functional on their own. 

[Kindred]

Damn... I should have remembered that too...


Well, that part is fixed, but another has arisen... but this one is an easy fix.

the action login2 exists in more than just index.template.php.
specifically, in Boardindex.template.php, Login.template.php and Wireless.template.php

If you do not change these to mos_login, then there will be cases where your user will be logged in to SMF but not to Mambo.

(specifically, this was encountered after logining in with an incorrect name. This brings the user to the SMF Login page, with a login box on the top (header) and a login box in the center of the screen. If the user enters his information into the header-box, then everything is cool...   if the user enters his information into the main screen box, then the disconnect occurs.)

This is solved by changing all references to login2 to call mos_login.