By Nick Russell on Thursday, 12 December 2013
Posted in Technical Issues
Replies 5
Likes 0
Views 816
Votes 0
I get the attached error message when posting new blogs... been happening all of today
Hello Nick,

You can try to disable either on autoposting and check whether the error still exist. Let say you have disabled facebook and the error is gone, you might want to check your facebook app setting. Here is the way to troubleshoot for facebook and Twitter:

Facebook:
1. Edit your Facebook application.
2. Check Site URL, App Domain make sure they are the same as your site domain (http://www.yoursite.com and http://yoursite.com make a big difference)
3. Reset the App Secret
4. Go to the EasyBlog -> Autoposting -> Advanced Settings page and revoke the access.
5. Go though the EasyBlog -> Autoposting -> Step by step guide and re-enter the new key and reauthenticate the Facebook access.

Twitter:
1. Edit your Twitter application.
2. Check website URL, Calback URL make sure they are the same as your site domain (http://www.yoursite.com and http://yoursite.com make a big difference)
3. Check if the Access level is Read and Write
4. Check if "Allow this application to be used to Sign in with Twitter"
is ticked under Settings
5. Reset the keys then refresh the page
6. Generate a new access token
7. Go to the EasyBlog -> Autoposting -> Advanced Settings page and revoke the access.
8. Go though the EasyBlog -> Autoposting -> Step by step guide and re-enter the new keys and reauthenticate the Twitter access.

Hope this helps.
·
Monday, 16 December 2013 10:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Nick,

This error is probably because one of the auto posting sites is having API issues. Did you setup any auto posting to any sites?
·
Thursday, 12 December 2013 09:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi

yes, i have dlvr.it posting to my facebook (fanpage) and twitter page - any reason this may have happened, and do you know how this can be fixed?

thanks very much!
·
Monday, 16 December 2013 08:05
·
0 Likes
·
0 Votes
·
0 Comments
·
thanks this is now fixed!
·
Thursday, 26 December 2013 20:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Nik,

You are most welcome. Glad that your issue is solved.

Thanks!
·
Thursday, 26 December 2013 22:42
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post