Customizing SMF > Portals, Bridges, and Integrations
MediaWiki 1.18.1 Integration Problems using PHP 5.3.8
Illori:
you would actually be best to keep to this topic, as that thread is not really for support. also we dont lock threads unless there is great reason to do so.
danielwmoore:
Very well then.
Here's my actual problem now, if someone can help.
I've set up the LocalSettings.php per the instructions, removed the '&' from line 265 which fixed compatibility with my PHP 5.3.8, and the Wiki loads fine, however, I can't log in. It redirects to an SMF login page, but I never get logged in. I'm always a guest.
If I use
--- Code: ---$wgSMFLogin = false;
--- End code ---
Then I get "password error" message every time I attempt to log in from MediaWiki (the password is correct.)
If I use
--- Code: ---$wgSMFLogin = false;
--- End code ---
then I have the problem of not being able to log in at all, with no error message given.
I'm using MediaWiki 1.18.1 and SMF 2.0.2.
I have set $wgCookieDomain correctly I am sure.
Andre N:
But that script looks like it is for SMF 1.13
You are using 2.02
ajbaldwin:
I'm also running into this issue - I've configured the bridge per the instructions, but am continuously getting a "No such user exists" error (when I'm certain that the account does exist and the password is correct). It's as if there's no actual bridge to my SF auth store happening at all. I'd certainly appreciate any help that folks could give us.
I've got no entries in my error log that I can show people, sadly. I'm running the same setup that Daniel is (MW 1.18.1, SMF 2.0.2) and the bridging code available at github.com/SimpleMachines/smf-mw-auth
Couple of small things that I noted (which probably aren't related, but I figured that I'd mention them):
- The README file for the bridge code mentions "If you encouter an issue be sure to read the known issues below", but there's only one thing below that entry that it could be actually referencing (page caching issues). Is that intended?
- One entry mentions: "NOTE: Make sure to configure the wgCookeDomain below" - the correct variable is wgCookieDomain (just a typo), but I wasn't sure if I was supposed to be referencing the same cookie name for both my SMF forum and the MediaWiki installation? Doing so seemed to clobber both sessions (which made sense), so right now that cookies are named independently of each other.
danielwmoore:
--- Quote from: ajbaldwin on January 19, 2012, 07:51:17 PM ---- The README file for the bridge code mentions "If you encouter an issue be sure to read the known issues below", but there's only one thing below that entry that it could be actually referencing (page caching issues). Is that intended?
--- End quote ---
I've tried that both ways myself, to no avail.
--- Quote from: ajbaldwin on January 19, 2012, 07:51:17 PM ---- One entry mentions: "NOTE: Make sure to configure the wgCookeDomain below" - the correct variable is wgCookieDomain (just a typo), but I wasn't sure if I was supposed to be referencing the same cookie name for both my SMF forum and the MediaWiki installation? Doing so seemed to clobber both sessions (which made sense), so right now that cookies are named independently of each other.
--- End quote ---
The wgCookieDomain is the domain name that the cookie is stored under. The browser will store the cookie by domain name, then under the cookie name in the domain name. Give the correct domain here, and the Auth is supposed to get the cookie name from SMF's Settings.php, then read the cookie.
I have put test code within the SMF_Auth.php script, and verified I am reading the cookie correctly. I have been unable to determine where it fails.
--- Quote from: andre nickatina on January 19, 2012, 04:29:53 PM ---But that script looks like it is for SMF 1.13
You are using 2.02
--- End quote ---
No, that script is for 2.0 only, and is not backwards compatible with 1.13. The version of the Auth script is 1.13, it is not a reference to the SMF version whatsoever.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version