Forum Replies Created
- Posts
Well folks, as I said in another post, I finally reached my tipping point. Thus, I decided to have a look at the “FS Poster” plugin, as had been recommended by another user here. After exchanging a few emails with the developer of the “FS Poster” plugin, and asking them a few questions, I decided to take a chance with it. Thus, I made a one-time payment of $45.00 for a lifetime license. After some initial setup confusion — probably because I was new to the plugin — I finally figured everything out. So, I am happy to report that I can now simultaneously autopost to the social networks listed below, using the “FS Poster” plugin. Once I am certain that “FS Poster” will continue to work, I intend to terminate my annual subscription to SNAP Pro. Quite frankly, I think I have given Ludwig and his team sufficient time to work out the various issues I have been having for many months now, as well as time to improve their level of support, which has been dismal as of late. With “FS Poster” I am autoposting to these social networks:
Blogger
Facebook timeline
Facebook group
Facebook page
Instagram
LinkedIn
Pinterest
Twitter
TumblrI also want to note that version 4.3.20 continues to work normally with Facebook.
I am aware of that. In fact, as I believe I pointed out in earlier posts, after reading about 4.3.20 still working, I did downgrade to it. Initially, it did work, at least for my FB page and my FB group, as I recall. However, for some reason which still remains unknown to me, eventually, even 4.3.20 stopped working, so that I was not able to post to my FB timeline, page or group.
Add to that the longtime problems with autoposting to Tumblr and Blogger, and the very poor support we have been receiving as of late, my frustration with NextScripts continued to grow. So, it is no surprise that I finally reached my tipping point, and I decided to look into the “FS Poster” plugin, as recommended by another user here.
Well, after exchanging some emails with the developer of that plugin, and asking a few questions, I decided to risk the one-time payment of $45.00 for a lifetime license, and I paid for FS Poster.
After a bit of initial confusion, because I was new to the plugin, I finally figured things out, and I can now simultaneously autopost to the following using the “FS Poster” plugin:
Blogger
Facebook timeline
Facebook group
Facebook page
Instagram
LinkedIn
Pinterest
Twitter
TumblrOnce I am certain that this will continue to be the case, I intend to terminate my annual subscription to SNAP Pro. I think I have given Ludwig and his team sufficient time to work out the various issues I have been having, as well as time to improve their level of support. They have done neither, so …
Excuse me, but that is clearly NOT true. Autoposting to Blogger and Tumblr may be working for you, but they are definitely NOT working for me.
I just updated to 4.3.25, as per your instructions, and doing so has made NO difference. I STILL cannot autopost to the following social networks:
Facebook timeline
Facebook page
Facebook group
Blogger
TumblrAs I already reported, I can only autopost to the following social networks:
Instagram
LinkedIn
Pinterest
TwitterYou will find a link for it on page 1 if the comments for this topic.
However, let me point out that while 4.3.20 worked for me for several days, so that I was able to simultaneously autopost to my FB timeline, page and group, immediately after Facebook had that hours long global outage a while back, SNAP Pro once again stopped working completely on Facebook for me.
In other words, I can no longer autopost to my FB timeline, page or group. So it was a short-lived victory.
In contrast, SNAP Pro still autoposts to Twitter, Tumblr, Pinterest, LinkedIn and Instagram.
Actually, downgrading for me is VERY easy and just takes a minute, the reason being that I run my own web server.
All I have to do is unzip the old version, and then drag the resulting folder over to the plugins folder on my other iMac where I run my web server.
I just let it overwrite the 4.3.23 folder, and 4.3.20 immediately takes effect.
It doesn’t even involve FTP.
I just wanted to remind everyone that if you temporarily downgrade to 4.3.20, you need to remember to disable the automatic update option for the SNAP Pro plugin on the main plugins page. Otherwise, WordPress will update the plugin right back to 4.3.23 again, thus recreating the same FB autoposting problem.
This is exactly what happened to me. Thus, I had to reinstall 4.3.20 again, and then immediately disable automatic update for the plugin.
I have the same problem. It happened after the update to version 4.3.21 of the plugin and later to version 4.3.23. After downgrading to version 4.3.20, everything works.
Hello. Thank you for this solution. This problem actually began after Facebook experienced their hours-long global outage. It was right after that, on October 7th, that I could no longer autopost to my Facebook timeline, page or group. I immediately opened a new support ticket here concerning it. Ludwig has yet to respond. I just updated my ticket to let him know that this temporary solution works.
Thanks again for figuring this out for us. Much appreciated.
Hello Ludwig. You wrote:
UPDATE (Sept 11, 2020): Most of the issues associated with New Facebook Design were resolved in the API version 4.5.1. Connection with session, postings to Profiles, Pages and Groups as well as “Comments import” should be working now. Please go to the Help/Support page in the plugin and click “[Check for API Update]”.
Well, sad to say, but even though I am using plugin version 4.3.20 and API version 4.5.14, and even though my session ID is current, after eight months, I am still unable to autopost to my Facebook timeline. Posting to my FB group and my FB page continue to work fine. It is just the timeline which refuses to cooperate.
I just tried manually again by going to a WP post and clicking on the “Post Now” button for my FB Timeline. This is what I got:
ERROR FB #7 (POST|u|I):Array ( [data] => Array ( [story_create] => ) [errors] => Array ( [0] => Array ( [message] => A GraphQL error field_exception occured. Check server logs for details. [severity] => CRITICAL [code] => 1357010 [api_error_code] => -1 [summary] => Oops [description] => Something went wrong. We’re working on getting it fixed as soon as we can. [description_raw] => Something went wrong. We’re working on getting it fixed as soon as we can. [is_silent] => [is_transient] => [requires_reauth] => [allow_user_retry] => [debug_info] => [query_path] => [fbtrace_id] => FvNog6Z7QdI [www_request_id] => Ad_OBsU0UP7frL6ku3Bdu9J [path] => Array ( [0] => story_create ) ) ) [extensions] => Array ( [is_final] => 1 ) )
On SNAP Pro’s log page, it says the following for my attempt to “Post Now”:
| WHERE (flt = “snap” OR (flt = “cron” AND (type = “E” OR type=”W”))) |
[2021-05-30 17:46:40] [User ID:1] – [Error] [Facebook – BBB Blog – Facebook Timeline] – -=ERROR=- ERROR FB #7 (POST|u|I):Array ( [data] => Array ( [story_create] => ) [errors] => Array ( [0] => Array ( [message] => A GraphQL error field_exception occured. Check server logs for details. [severity] => CRITICAL [code] => 1357010 [api_error_code] => -1 [summary] => Oops [description] => Something went wrong. We’re working on getting it fixed as soon as we can. [description_raw] => Something went wrong. We’re working on getting it fixed as soon as we can. [is_silent] => [is_transient] => [requires_reauth] => [allow_user_retry] => [debug_info] => [query_path] => [fbtrace_id] => FvNog6Z7QdI [www_request_id] => Ad_OBsU0UP7frL6ku3Bdu9J [path] => Array ( [0] => story_create ) ) ) [extensions] => Array ( [is_final] => 1 ) ) IS SCIENCE BETTER THAN THE BIBLE? — a Bill’s Bible Basics ArticleFacebook is such a pain in the butt!
BTW, when I check for an API update, the progress wheel just spins and spins and spins and never seems to connect to your site for some reason.
Alexander, I don’t know if you ever resolved your issue being as this thread seems to have died. But, IMHO, the version of PHP that you are using is rather old. I suggest that you upgrade to 7.4.8. Maybe doing so will resolve your issue, if it isn’t resolved yet.
Please disregard my previous message. While I still don’t know why Reposter wasn’t working with Facebook for the past 19 hours, a short while ago, I updated to the latest version of WordPress — 4.5 — updated a few plugins that needed it, updated two themes, made sure that the wp-cron.php file still has the correct path to my PHP interpreter in the shebang line, and then rebooted my server. I am happy to report that Reposter is once again working with Facebook. In fact, it is working with Blogger again as well. But now there is an issue with it not reposting to Tumblr. Does this ever end? 🙁
I can confirm that while Facebook is working if I use the “Post Now” button on an already published post, and while the “Submit Test Post to Facebook” option in my Facebook account settings in SNAP Pro is also working, Facebook is definitely NOT working with AutoPoster at all, even when using NextScript’s premium API.
Furthermore, Blogger stopped working again on March 26, and has not autoposted since that time.
I am using:
Plugin Version: 4.3.13 [Pro]
(One User, Multiple Accounts)
API Version: 4.4.54Hello Ludwig. Yes, I was already using HTML to enclose the %URL% tag. However, somehow I had gotten my HTML code wrong. I just now fixed it and it is now working fine, and producing a clickable link on Blogger. 🙂
Excellent! After seven long months, my blog is finally syndicating to Blogger once again. The only problem I see currently is that while the %URL% operator is replaced by the actual page URL in my posts on Blogger, it is not a clickable link. It is just plain black text. I don’t know if this is because of the way that Blogger is parsing it or what. In contrast, if I include clickable URLs in my WordPress blog posts, they DO appear as clickable links on Blogger.
I wanted to add an important point here regarding something I recently figured out concerning Reposter. While some of you mention that Reposter is not working for you, you do not mention which networks you are specifically trying to use it with.
The reason why I am mentioning this, is because while Reposter may appear to not be working, as I discovered myself, it may in fact be working, but the network where you are trying to repost is actually blocking the post, giving the impression that Reposter is not working.
More specifically, what I have proven to myself beyond a shadow of a doubt is that some social networks — in particular, Tumblr and Twitter — will prevent you from posting the same image over and over again.
For example, in the case of Tumblr, if Reposter attempts to repost a blog post which contains an image I have posted to Tumblr before, the post will be posted to my Tumblr dashboard, but it will NOT be posted to the public URL for my Tumblr blog. I have clearly confirmed this point.
On the other hand, if I make a new blog post on my WP blog which contains a brand new image which I have never posted to Tumblr before, in both cases, whether I use Autoposter or Reposter, the post will be posted to the public URL for my Tumblr blog.
With Twitter, it is a little different. If I make a post on my WP blog, if it contains an image I have posted before on Twitter, regardless of whether I use Autoposter or Reposter, Twitter will post the text portion of my blog post, but not the image itself.
In short, both social networks have in place a mechanism — probably part of their algorithm or filters — which prevent the double-posting of images.
To reiterate, the problem is not with Reposter in these scenarios. The problem is that the social networks are blocking the images. If you want to check out my expanded comments regarding this issue, please visit the following URL:
Glad to hear you got it working.
Do you also syndicate to Twitter? If so, are your images showing in your Twitter posts? As I explain in one of my BBB Blog posts — https://www.billkochman.com/Blog/social-networks-vs-the-people/ — if you have already posted a particular image to Twitter, when you repost to Twitter using Reposter, Twitter will block the image, unless you first alter the image and re-add it to your blog post. Apparently, this is the only way to convince Twitter that the image is new. In other words, Twitter rejects any images which have been previously posted.
