I've got the 2.0b bridge installed between SMF 2.0RC1.2 and Mambo 4.6.5. Once I did that, I tried registering via the bridged registration, but got a 500 error. I went directly to SMF and was able to register successfully. Any ideas?
You should probably upgrade to SMF 2.0 RC3 as it fixes many bugs and security holes. Regarding your 500 error, take a look here possibly:
I remember hearing that the bridge had problems with RC3. Is this still the case?
I was using Firfox when I got the 500 error. I switched over to IE and received the below error:
Please try again. If you come back to this error screen, report the error to an administrator.
Where did you get the 500 error?
I receive the error after clicking the send registration button on the "/index.php?option=com_smf_registration&task=register" page.
I've tried it on 1and1 with SMF2RC1.2 and RC3.0 as well as locally via uWAMP with both versions of SMF as well. Same errors each time.
Hum, check file permissions. Folders should be 755 while files should be 644.
I'm unaware of that page too. What mods do you have installed?
also, please confirm that the mambo db user has access to the smf db, and vice versa
Killl Em All, Other than a couple of mods put out by mh2design being installed on my test sites with SMF2RC1.2, I don't have any others installed. RC3 is currently only using the bridge. The file permissions should be set correctly; if I disable the bridge, I can register with each site normally.
Kindred, I've tried two differant methods for db usage. My RC1.2 sites are sharing with Mambo, and via separate install of Mambo, RC3 is not sharing a db with Mambo. For my testing, I've been using root.
Bump. can anyone help with this?
the only thing I can think of is that you have a permissions problem with one or more of the files...
Maybe try running this script attached to the first post.
I ran the script, and it came back with
QuoteWrite this down!
In some cases, SMF 1.0.x does not detect your FTP path correctly. This tool has successfully used the (possibly detected) path below. You may wish to write this down, and make sure to use it when installing mods.
This problem should be resolved in the next major release of SMF.
After trying to register, it still shows the error
Please try again. If you come back to this error screen, report the error to an administrator
As far as permissions, what's the best method to update permissions for the files already on the host's webserver?
Try running this script?
I hate 500 errors, I also hate white screens. They are both a pain.
So I ran the sript. It found a few .php files that had the whitespace after the ?>. I fixed them, but still didnt jive.
some info I have been prompted to pass on,,,,
First: None of the bridges will work with SMF 2.0 RC3. Until there is a release with the integration hooks fixed, they just won't work. So upgrading to RC3 is a bad idea, regardless of security. Just having the forum integrated in Mambo and not accessible directly will help with most XSS vulnerabilities, anyway. All input is passed through Mambo and cleaned before SMF gets a chance at it, so there's a better chance at averting XSS attempts.
Second: It seems that your problem is likely to be database permissions, not files (as I first suggested). The error is a Mambo-generated error, not a PHP error. Keep in mind that on a local WAMP server, if the database user names are different, it won't actually perform the switch properly. (and sometimes, even if the database users LOOK the same, they are actually different on many of the non cpanel site panels)
Third: Make sure you have the SMF_header_include mambot published. This is very important.
Fourth: You are using bridge registration. That component was never updated for the 2.0 bridge, and should be deprecated by now. Most users choose SMF or Mambo registration, anyway. Mambo registration with the SMF_register mambot published is the most secure method.
Hmm... On the test site located on 1and1, I'm using SMF 2.0 RC1.2 where it's sharing the database with Mambo with the same username/pw. I have the SMF_header_include mambot published.
I verified the databases between both and they are both pointing to the correct database with the same username.
Mambo registration with the SMF_register mambot published, Im still getting the database error, however, I noticed in the user manager in Mambo that the test account did populate, but didnt send a confirmation email. The account isn't showing up in SMF either.
Should I just downgrade to SMF 1?
you can not downgrade and keep existing data.... there is no "reverse" script written for upgrade.php.