any ideas on how to find a backdoor created by the site builders?

The plugin page for Gravatar Box has moved to here: http://ottopress.com/wordpress.....vatar-box/

I’m closing comments on this post. Please take any comments to the new site.

The plugin page for Simple Twitter Connect has moved to here: http://ottopress.com/wordpress.....r-connect/

I’m closing comments on this post. Please take any comments to the new site.

The plugin page for Simple Facebook Connect has moved to here: http://ottopress.com/wordpress.....k-connect/

I’m closing comments on this post. Please take any comments to the new site.

Twitter Apps are less complex than Facebook Apps, which is why I didn’t go into as much detail on them. Basically as long as you get those four settings the plugin actually tells you how to setup set properly, it works. More or less.

The four settings that count:
-Application Type must be set to “Browser”.
-Callback URL must be set to your blog URL (it gives you the exact value of this on the STC config page).
-Default Access type must be set to “Read and Write”.
-Use Twitter for login must be checked (enabled).

All the other fields like name, description, etc., just don’t matter. They need to be filled in, and they make the app look nice and such, but they don’t count for the actual functionality of the thing.

How to implement post thumbnails: http://markjaquith.wordpress.c.....il-images/

Anyone have any suggestions on where to read up on it? I will edit the code if I knew where to start in it… I attempted to write the theme creator but their website is in another language and the “Contact Us” link has a Captcha in another language. So utterly screwed.. haha

Just so that you know I looked for this tweet because I love the FB one so much!! thanks for creating that–It sure makes life a bit easier.

I’ve tagged 0.15 to fix the problem.

But without that, no, it’s not possible. The theme has to be modified to make space to put the buttons in as well as to mark the location of the form elements in order to hide them naturally.

If STC finds a get_shortlink function, it uses it automatically.

Forum topic: http://wordpress.org/support/topic/373077

I’m running into an issue with the SFC – Publish component. When I activate it, the publish box in the Post Edit window displays the following error msg:

Fatal error: Call to undefined function has_post_thumbnail() in [...]/wp-content/plugins/simple-facebook-connect/sfc-publish.php on line 186

This breaks the edit window, which no longer displays the main body of the interface.

I’m running on the latest/greatest WP & SFC.

Any ideas?

It appears that some how my cookie for my website had become corrupted and hung on to my FB session. Since I had not connected my facebook account to my profile it had no way of knowing that I was the same person.

Hope that this helps anyone else that runs into the same problem.

Appreciate you Otto for having this sounding board for users to iron out any wrinkles we run into!!

I edited my comments.php correctly, and the connect button shows in the comment area. When it’s clicked though I just get a popup window that goes to my blog’s home page.

I think it’s worth mentioning that originally when I clicked it the popup said that I had to set up my connect URL, and it’s after I rectified this that this has started to happen.

My blog is: http://blog.richardmilne.net

This is my first time working with XFBML, but I figured my connect URL must be the root to the blog, which contains xd_receiver.htm is this correct?

Hope someone can help!

No plans on making it use first name only, but it’s an easy change if you want to do so. In the sfc-comments.php file, around line 295, you’ll find this line:
$_POST['author'] = $user_details[0]['name'];

Change “name” to “first_name” and you’re done.

However, this is not necessarily a privacy issue. Facebook makes this information available publicly, to anybody, without any form of approval whatsoever: uid, first_name, last_name, name, locale, current_location, affiliations (regional type only), pic_square, profile_url, sex

Source: http://wiki.developers.faceboo.....rs.getInfo

I then over wrote the sfc-publish.php file from your trunk to my plugins folder and was able to publish both to my blog and FB automatically.

Let me know if you need more details.

One other unrelated question since you mentioned privacy… when commenting while connected w/ FB the comments show the commentors full FB name. Any plans to have an option to only show first name, like the fan box does?

thanks,
-dave

Note that my submit button in plugin_options_page() has no “name” on it. This is because I don’t care about it. Buttons without names submit no extra parameters, they just submit. But, give it a name, and it returns the value on it.

There’s two ways to do this.
1. Unique values
2. Unique names

The first way would look like this:
input type=”submit” name=”plugin_options[submit]” value=”Submit”
input type=”submit” name=”plugin_options[submit]” value=”Reset”

In this case, my validation function would get back an $input['submit'] which would be set to either “Submit” or “Reset”, depending on which button I clicked. You could take action appropriately. Note that you would probably not want to set $newinput['submit'] to return from this function, unless you wanted to store that value in the database for some strange reason…

Problem with this is that the “value” is what is actually displayed on the page. If you translate that into another language, your code now has to look for that value. It’s problematic.

Second way:
input type=”submit” name=”plugin_options[submit]” value=”Submit”
input type=”submit” name=”plugin_options[reset]” value=”Reset”

In this case, I will get either $input['submit'] or $input['reset'] back. Because only one will come back depending on what button is pressed, I can ignore the value and take action based on which one is set. Similarly, I’d want to not put this resulting value in $newinput, same as before.

http://plugins.svn.wordpress.o.....ublish.php

I removed the change for the privacy thing, to see if that solves the problem. I still cannot replicate the problem myself, but that was the only change I had made in that area, so backing out the change should resolve the issue.