Forum Replies Created
The plugin identifying returning users is completely independent of and irrelevant to e-mail addresses (and in turn, a users’s e-mail visibility settings are completely irrelevant to a FB platform application being able to access their address). As you can see in the plugin docs (http://www.justin-klein.com/projects/wp-fb-autoconnect/) under “How it works,” the plugin uses WP usermeta to tag a given account to a given Facebook *userid* (not e-mail). The only time it uses e-mail matching is for first-time logins of existing WP users, but after that, the same user logging in over and over will not generate duplicate WP accounts under any circumstances – because they always have the same FB uid, and that uid is already associated with a WP account. If you’re getting duplicate accounts on your blog, that’s evidence that there’s something very fundamentally strange about your installation – though I wouldn’t be able to debug it without a full report, along with the information requested in a support ticket here: http://www.justin-klein.com/projects/wp-fb-autoconnect/#feedback.
I’m the author of WP-FB-AutoConnect; I just wanted to chime in & say that while I have no idea what’s going on with Rocio’s site, I can absolutely guarantee that my plugin does not create duplicate users. Perhaps she’s using an extremely outdated version, or has some other code that’s conflicting with it, etc, but in all the years I’ve been developing this plugin I’ve never received a report of duplicate users (nor have I ever seen them myself – and I still use the plugin on my own personal site, as well as a handful of others I administer).
@muratk / Mike: Could you please post your questions on the plugin site’s support section, so other users with similar questions can benefit from the answers: http://www.justin-klein.com/projects/wp-fb-autoconnect
(Soon I’m gonna stop checking this thread)
@Mike Can’t we keep the high school out of these discussions?
Thanks…I agree. Especially when he asks question after question that I’ve already taken the time to document thoroughly but he clearly hasn’t bothered to read
Note: the reason BP filters might be disabled for you is because you decided to use the test version, thus creating conflicts. For other users, it’ll properly detect if they’re using BP and select/deselect itself by default accordingly.
>>What are Buddypress filters? Should I enable them?
If you’re using BuddyPress, you don’t want to disable the BuddyPress filters. Debug options are just for development and 99.99% of the time you shouldn’t need to touch them.
>>What are these actions and filters? I see nothing about them in the settings area?
I’ve spent a great deal of time documenting everything extensively on the plugin homepage, often with examples. It already answers very many of the questions you’ve asked on here (including this one). Please make sure you’ve read it.
Your WP install doesn’t automatically tell you when a new version is in the repository? It should, 90% of the sites that were using the plugin had upgraded within the first 6 hours. I also announced it in the comments on the plugin homepage, and Greg announced it in this forum a day ago (“I’ve got version 1.0.8 with buddypress filters acvitated on my site if you guys want to try it.”). It’s up to 1.1.1 now. The changelog shows that it includes BP support. The documentation on my webpage also shows that it includes BP support.
From Andy’s test version it works quite differently; I didn’t document all the differences though as we’d asked that people not use the test version for the few hours it took me to get out a real one. In any case, there should no longer be any need to manually edit the plugin – there are filters and actions that let you accomplish whatever custom integration you want (and if you need another filter/action somewhere else, I can add it so there will never be a need to edit the plugin directly). I’m pretty sure the 2 actions & 1 filter I’ve included should be sufficient for most usual needs, though.
What are you talking about? Do what u like, but as far as I know you’ll be the only person using the unreleased test version. Dozens of others on BuddyPress are already using the real version, including ModemLooper’s link just one post above yours.
Both Andy and I have recommended several times not to use his test version; he just submitted it to me as an example of how to make correct BuddyPress usernames. There’s only one version available on the wordpress plugins repository. The advantage? That everyone else will be using the real version, that if you don’t use the real version you’ll be running unsupported code along with all the bugs that I’ve fixed since it was produced, and that obviously the documentation on my site will reflect the real plugin, not unreleased debug versions.
I think it’s pretty safe to install. I’m not really sure what’s going on with Greg’s site, but I’ve tried it on several dozen other pages which’ve successfully installed it (including the option to prompt for email). Aside from my own site, here’s just one more example: http://www.ozamiznon.com/
Edit: that example asks for email, but doesn’t require it. Here’s one that requires it: http://blogge.rs/
Edit2: I WOULD be interested to hear from Andy, who should be pretty good at detecting any buddypress-specific bugs that I can’t
No, the cause isn’t the API key and secret. If you haven’t saved a valid API key and secret, it won’t even render a Facebook button, nor will the login work with the email requirement switched off.
If the problem is that it won’t let him request an email address, the issue could only be the Email Domain setting on the Facebook application, as far as I know. I’m quite confident that functionality works on my end, as I’ve tried it on about 15 other sites since the 1.1.0 upgrade
Please make support requests on the plugin’s homepage; I’m trying to keep it all centralized there so others can benefit from the same answers.
By the way, when you installed it, did you have to change any settings? Specifically, was “Disable Buddypress Filters” de-selected by default? It should be checked by default on WordPress (it is), and un-checked by default on BuddyPress.
Nope not in the core, but you’re doing things like editing process_login.php and hacking the database and I’ll just end up adding pre-registration filters to enable user customization the “right” way (and include a default filter that changes usernames to ones that work with BP, as in Andy’s example code)
Peter: PS, most of what you’re doing will be irrelevant when I release a version that works with BP out-of-the-box, so u dont really need to spend the time hacking it Also, most of the questions ur asking (i.e. what if u want to require an email?) are all clearly documented on the plugin homepage.
Does anyone still have a zip of andy’s modified version? I accidentally deleted it before implementing one piece
You might just want to hang tight until I submit an “official” version that also includes Andy’s code. There’ll probably be a bit of restructuring to make it work well for both WP and BP.
All buddypress-specific code goes in Buddypress.php, which gets included if the “Include Buddypress Filters” option is checked.
As far as what Andy’s specific function does or what you need to do, that’s your job The plugin works in WordPress, and I don’t know what specific different criteria BuddyPress introduces, nor do I have a way to test it.
As far as how the plugin works, it’s documented pretty thoroughly both on http://www.justin-klein.com/projects/wp-fb-autoconnect and in its comments (you can ignore the adminpanel code which is obviously not *functionally* relevant…just for setting settings).
Greg: No, I definitely wouldn’t want to hassle the user with typing something in manually – the main purpose of this plugin was to make it all seamless, so they can just click “login” and they’re in. As soon as they start having to do stuff by hand it starts going way off-base
@Peter: See the discussion here, starting on comment 60: http://www.justin-klein.com/projects/wp-fb-autoconnect