Have you updated to 1.2.5? I changed the way the access token retrieval works to fix a bug in 1.2.4.
After updating, you will need to regenerate the access token using the link in your WPBook Lite settings page.
Hi John
I initially posted this prior to 1.2.5 coming out, and have updated it since, regenerate access token (which says it has been saved and to view blog, which then loads the blog in the window as i would expect) … from there I have then tried posting again, and am still getting the same error.
What is the next step to try and problem solve this issue
Thanks
b
Have you checked (see other threads in this forum) to see if your Facebook application has “deprecate offline_access” checked?
When you visit your WPBook Lite settings page, does it say a token has been stored, and if so, does that token end with any “expires=” info?
Hi again
In terms of the advanced settings, i have them as follows (which i believe havent changed since it stopped working)
Remove Deprecated APIs: Enabled
Stream post URL security: Disabled
deprecate offline_access: Disabled
Timezone-less events: Enabled
iframe Page Tab: Enabled
Forces use of login secret for auth.login: Disabled
Use Titan to handle gigaboxx requests: Disabled
Include recent activity stories: Disabled
New mailbox backend: Disabled
Encrypted Access Token: Enabled
Enhanced Auth Dialog: Disabled
page_hours_format: Disabled
Graph Batch API Exception Format: Disabled
In terms of the token, it is currently saved as
Stored access token = AAADA0oO3FLIBAJyFBDPaqyHvZAUYBMeAII8HuLNkwz8qUB9vzY4zQE0LcLdLejuov4UxgecqvplkdWgB6EJ00fpsLTwcZD
In terms of the section Select how your app integrates with Facebook
i currently only have the website option ticked as on, with appropriate details … do I need to fill out any of the other setions, I didnt believe so, but as far as i can tell thats the only other variable that may be causing the issues.
The bit that has confused me is it was working, and then stopped, which Id assume either had something to do with the 1.2.4 bug that fixed in 1.2.5 or something to do with FB changing things up again.
I moved over to WPBOOK Lite due to the lack of https option on most of my blogs, got it working, and then it stopped sometime in the week following … so just trying to work out what has caused it …
@bleideritz – not sure what else to try here.
Is it possible you changed your Facebook password after granting access?
Some folks on stack overflow have seen this just come and go randomly: http://stackoverflow.com/questions/5972901/getting-error-validating-access-token-from-facebook-for-some-users
You can actually check your access token here: http://developers.facebook.com/tools/debug
Which tells me it is valid, never expires, has offline_access and stream_publish permissions.
But what worries me is where you said:
I have recently been using wpbook lite on a few different blogs, and yesterday one of the users reported the following error on one of them
The access_token is tied to you as a user – specifically it is tied to the combination of your Facebook profile ID AND the Facebook Application ID. It enables this app to do these things for this user.
Are the other users of blogs where you’ve installed this trying to use the same access key? Are they generating their own access keys and storing them?
Is the access key you posted above found in your WPBook Lite Settings page?
Finally, are you trying to publish to a profile, a page, or a group inside Facebook? page access_tokens are different than profile/group ones.
Hi again
I havent changed the password and neither has the client, when I got it working, she also had it working with no worries, which is why I thought it odd that it had stopped again.
I had not realised it was a single user situation, however if it is, that may explain the issue, however why would it have been working prior (it was working when I first moved from WPBook to WPBook lite, which I think was the first or second release of it) … however I did mention at the time for my client to go through the same process so maybe that is the conflict being caused? (though again we both had it working at the same time with no worries) … I have also got the same error happening on one of my other blogs, which I am the only user on it.
in all cases we are trying to publich to a page (fan page or whatever they are calling it this week) rather than a profile or a group.
I shall have a read of the stack overflow thread and see if i can make any sense of this.
I really like the WPbook setup, and want to keep using it, but need to get it working again asap or I may have to find an alternative for a short term solution until I can get to the bottom of this.
Thanks for your help thus far
b
Sorry it’s not working for you, I really don’t understand why.
WPBook and WPBook Lite both assume that they store an access_token (one per WordPress install) which enables the blog to post to an individual profile, and (if manage_pages permission is granted) it retrieves an access token to publish to that page.
If multiple blog authors are changing this setting, I’m not entirely sure what will happen – it should succeed for the most recent person and fail for the others, I would guess.
Facebook’s API is just plain unreliable – I have no idea why they would mark an access_token as invalid via the API if it checks out fine via their own API test tool.
