Forum Replies Created
-
Hmm…yeah this seems to still not work. I don’t have a BP install to debug on, so I’ll leave this one up to Andy – now that there’s a BuddyPress.php file for bp-specific filters, it’ll be easy to stick in whatever filters are needed once someone figures it out
Looks good – although you should delete all existing FB_xxxx accounts so we can see if they get created using Andy’s filter (or the user profile links still won’t work)
You need to delete the buddypress filters you’ve added manually, which are resulting in double-buttons
I’ve always tested with just two FB accounts: my admin account, and one other. You can use phpmyadmin to delete the usermeta manaully if you want to force the plugin to match by email hashes, or delete the WP account entirely if you want to simulate a first-time login.
Still much nicer to have all the discussion live on the plugin page (which is linked to from the download page on wordpress and the admin panel, so it’s where users will go for support usually)
Can I request that we move this discussion to my plugin homepage’s comments? It’s much easier to get notification everytime someone replies, and then other users of the plugin will be aware of it too
I’ll add a satellite php file with BP actions in the next version, conditionally included by an “Include BP Actions” option or something. Then it’ll be easy to paste any more you may think of in that file, without complexifying the main code
@Andy: I see what you’re saying, I guess. Keep in mind of course that any URL which is already publicly accessible on the web is pretty much public in the first place, so anyone (person or crawler) could stumble on it by accident – all I’m doing is pointing out to myself “Here’s where someone’s trying your plugin – let’s make sure it’s working right for them!” If the site happens to be hidden or inaccessible, then they’re on their own
Now that it seems stable, though, this probably isn’t as needed…but I should mention that it was purely because of it that I was able to find some critical bugs in early versions that prohibited it from working in 99% of cases.It seems to me that this is pretty much the exact same thing as how i.e. Google Earth sends usage statistics back to Google to help them improve their (free) software…
@Footballfantalk: Please post this question here, so other users who might be experiencing a similar problem can benefit from the discussion (and also so I can get notification of replies):
I just successfully logged in with it on your site. Could you refresh the page and try again – or even try it in a different browser? The only time I’ve seen that error is when I had a leftover Facebook session cookie from previous experimentation…like I changed my API key while I was still logged in, or something similar.
That’s because he specified “http://www.cfcommunity.net/” in his Facebook Application, but his website is identified as “http://cfcommunity.net/” by WordPress (see http://www.justin-klein.com/projects/wp-fb-autoconnect#faq11 )
Regarding the specific buddypress suggestions: I actually use WP myself (and have never even tried BP) so this is a bit outside the scope of what I’d planned for the plugin, but I did try to write it so that it’d be very easy to extend in a variety of ways.
For example, you can have it output additional Connect buttons anywhere you like (in addition to/instead of its built-in widget). See the “Custom Login Buttons” section here: http://www.justin-klein.com/projects/wp-fb-autoconnect#customizing
PS, so glad people seem to be liking it so far
Is that not okay?? Basically that’s how I’ve fixed 99% of the bugs in the plugin – when someone activates it, it tells me about it, so I can checkout their site and make sure everything’s working properly. Often I’ll find something that doesn’t work right, so I fix it and release an update, and let that user know directly. I’ve found that users almost never bother to report bugs, but are extremely happy when I contact them to let them know that i’ve fixed something just for them