Perhaps I am looking at this wrong. Will this work if I setup my website with a dedicated IP and SSL certificate and then force SSL logins and SSL admins according to this?
http://codex.wordpress.org/Administration_Over_SSL#To_Force_SSL_Logins_and_SSL_Admin_Access
I have run into the same problem.. have you found a fix for this?
I do prefer using SSL on FB as when I travel I am often forced to use less secure connections… as soon as I enable the secure option in my FB account settings however, the FCB publish function breaks down.
Try it with the newer 0.999 version in beta testing here:
http://plugins.svn.wordpress.org/simple-facebook-connect/branches/new-sfc/
You’ll need to remove the old SFC and delete its files, then put these newer ones on the site.
This new SFC uses the Facebook Graph API and JS SDKs for everything, so it should be more compatible than the older Connect libraries.
I can’t seem to get past the
If you can see this, then there is some form of problem showing you the Facebook publishing buttons. This may be caused by a plugin conflict or some form of bad javascript on this page. Try reloading or disabling other plugins to find the source of the problem.
error with that version..
Other then NGG and the automatic update plugins I have very few other plugins..
WordPress has automatic updating built in. If you have an older plugin for that, it has been known to cause issues. Remove the plugin and do a re-install with the normal automatic updater.
I have disabled all plugins other then SFC and Akismet and am still getting the bad javascript error.. I have ran the reinstall, to no avail. I have tried in both Chrome and FireFox.
I apologize for the JS issues.. this seems to have been caused by a misconfiguration on my part (I did many years ago).. get_locale was returning ‘en’ and thus the FB API could not be found on the localized address it was looking at.
It seems to work fine now. I have just 1 remark: if you are not logged into FB and you login through the popup in WP, SFC does not – after logging in – show the publish buttons; it will still show the login button (there is no indication it was in fact successful). Instead you have to refresh the entire page for the publishing buttons to show.
Nicely done btw.. I especially like how all the functionality is behind a checkbox on the settings page rather then a separate plugin.
You shouldn’t have to refresh manually. It should just show the buttons. check your javascript error console, maybe you have something interfering there.
I get 2 “Unsafe JavaScript attempt to access frame with URL” errors:
– the first to access the FB frame (https://www.facebook.com/login.php?api_key=…) from my WP page (upon clicking ‘connect with FB’)
– the second to access what I assume is the FB login validator (http://static.ak.fbcdn.net/connect/xd_proxy.php?version=3#cb=f662f4ga1c&origin=…) from my WP page (upon logging in)
And finally I get a “Uncaught ReferenceError: sfcShowPubButtons is not defined” which obviously means the function to show the buttons isn’t called for some reason..
Make sure your URL is properly defined in the facebook application. It has to match what’s in your URL bar exactly. Case even matters.
I get the “unsafe JS” errors only in Chrome.. IE and FF don’t show any errors at all.. could this be because Chrome hides the initial “http://”?
Even though IE and FF show no errors though, I still have to refresh the page, so I think it s not related to the unsafe JS errors. The URI of my blog is http://jan.milants.eu/wp-admin/… and the FB app has site URL set to “http://jan.milants.eu/” and site domain set to “jan.milants.eu”, so all should be good.
The final “Uncaught ReferenceError: sfcShowPubButtons is not defined” error I think is the problem.. I have looked for this function in all source files and the only reference I can find is in the onlogin property of the FB connect button. I can’t find a function declaration though..
Where is this supposed to be defined, is this in a JS file that s not part of the SVN checkout or so maybe?
Looks like this got broken last week. I’ll revert it.
