Forum Replies Created

Viewing 14 replies - 16 through 29 (of 29 total)
  • Thread Starter tedmaster

    (@tedmaster)

    As far as I can tell this is actually a shortcoming (or feature) of the Twitter API. They don’t reveal the email address associated with the account since, in their words, there is no guarantee that the entity behind the account is actually a person with an address (or something to that effect).

    HTH,

    [ Signature moderated ]

    Thread Starter tedmaster

    (@tedmaster)

    Thanks a lot for the feedback. Indeed the images are considerably larger than the window width so I think we’re covered. My concern was that non-retina devices would see images that are far, far too big but then I thought about it for a while, and everything makes sense. Non-retina displays will simply be downloading extra information they won’t be able to do anything with, but the size will be whatever is set in the HTML.

    Thanks again. Nothing like a responsive developer!

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    Hi dan. Thanks SO MUCH for posting this here. I haven’t tried the fix yet but it looks reasonable. I sure hope the plugin developers find the time to update the plugin but if not, it’s not that hard to do yourself.

    Thanks again.

    Ted Stresen-Reuter

    Thread Starter tedmaster

    (@tedmaster)

    @alex.hruzewicz I too had my app approved but was unsuccessful associating my wordpress user account with my Facebook account. Although I could see the links in the plug-in control panel, clicking them (when logged out of Facebook) would allow me to log in to Facebook, but then nothing apparent would happen. If I was already logged in to Facebook, clicking the link to associate the account would appear to do nothing.

    HTH,

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    It seems Facebook did an about face on app approval. Scroll to the end of this page:
    http://www.nextscripts.com/known-issues/facebook-issues/

    I doubt this will impact, much, our situation.

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    So I just logged in to my Facebook application and see that my request for the publish_actions was DECLINED ROFL.

    I’m hoping it was declined because, as the documentation states, I don’t need it but it would be so helpful if Facebook would specify that in their response.

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    Ok so, maybe I lied. I can’t resist a good puzzle and while perusing the documentation, I found this gem:

    “Note: If the only people who are ever expected to log into your app are the people listed in the Roles section of your app, you do not need to submit for review. For example, if you use the Facebook for WordPress plugin to publish your blog posts to Facebook, you do not need to submit for review to be able to grant the manage_pages or publish_actions permissions as long as the person logging into the app is listed in the Roles section of your app’s dashboard”
    https://developers.facebook.com/docs/facebook-login/overview/v2.0

    I think the bottom line is the current version of this plug-in is written against the previous version of the Facebook API. However, any Facebook application created after about April 1 is prohibited from accessing the Facebook 1.x API.

    So in other words, you may be able to get this to work making a few modifications to the existing code but I’m gonna guess there are some deeper issues that will need to be resolved before the plug-in works full force.

    In fact, I’ll bet that the two developers tasked with maintaining this plug-in are actively working on the 2.0 version as I write this, but they are prohibited from talking about it (and would probably benefit from having some beta testers).

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    @jessepearson indeed you seem to have found *a* problem :-). Honestly, if I had the time, I’d be all over this, but I find the Facebook documentation to be either outdated or sparse (few clear and working examples) and I just don’t have the time to wade through it… If, however, that changes, I’ll post my updates here.

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    @jessepearson, I am having the exact same experience.

    Thread Starter tedmaster

    (@tedmaster)

    @jessepearson I just used screen shots from wordpress (the publishing process), but if I recall, I found the steps on a web site somewhere… Sorry but I can’t find the URL.

    Thanks for sharing your experience.

    Remember: version numbers, list of other plug-ins, can all be very helpful to the developers (if they ever read this).

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    @pokr777, yes, more or less, this is the same issue. That said, I’m pretty sure that if you resolve a few issues on the Facebook app page you’ll see what I see. To do that, click the Debugger link in the Facebook menu of your wordpress installation. You’ll see which items you need to resolve.

    However, as we’re both experiencing, even if you do resolve those issues, it still doesn’t work and as you can see in my case, you may end up with two links, neither of which works.

    Please, developers, point us in the right direction.

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    @pokr777 How do you know there is a plug-in conflict? Have you seen a bug report or have some other kind of debugging output that confirms this? If so, any idea which plug-ins are conflicting? Downgrading is not an option for me at this time.

    Everyone: I’m sure the developers would find it extremely helpful if you could follow the steps I’ve detailed above and and either confirm or contrast your results, including version numbers (wordpress, plug-in, PHP, and maybe even list other plug-ins you have active).

    I would try to debug it myself but I simply do not understand the Facebook side of things (not sure what is supposed to happen and what output I’m supposed to see). In other words, in my case, it’s not for a lack of tools but rather a lack of in-depth documentation (Facebook API documentation).

    Thanks,

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    Hmmm… I had Publish an Article selected as that is what some documentation I read somewhere suggested I do. I’m doing the other one now, though, just in case.

    Ted

    Thread Starter tedmaster

    (@tedmaster)

    Hi,

    Thanks for the reply. I think I’ve done that. The application has been approved and all the additional fields required for for Facebook Login (as described here) have been filled in (I am not seeing any errors in the Facebook Debugger).

    Just out of curiosity, how are you “requiring” publish_actions? Where are you seeing these error messages?

    TIA,

    Ted

Viewing 14 replies - 16 through 29 (of 29 total)