Forum Replies Created
- AuthorPosts
Jay
ParticipantI have the same problem. Has anyone been able to sort it? Thanks
Ben
ParticipantI having [message] => Internal API server error.
What’s up? Any fix?
Doug
ParticipantGreat. Really need an alternative to Jetpack Publicize!
angel
ParticipantI also having same error.
Any solutions???
Yes, it’s coming. No ETA yet.
November 28, 2016 at 6:29 pm in reply to: Blogger Issue, cannot create new blogger account in snap #522567Will be fixed in the next release.
November 28, 2016 at 1:37 pm in reply to: Parse errors testing posts to self-hosted WP sites #522521Anna S
ParticipantAny more help please? My ticket has gone unanswered, and I’m not sure where else to dig up clues or answers. This problem has been ongoing since Nov 1.
I now have WP Plugin Version: 3.7.7 API Version: 2.24.16.
PHP is at 5.6 on my source site.
Database collation is at utf8_general_ci…and tables are at utf8mb4, consistent with the WP version.I still get the same parse error when trying to submit test posts to target self-hosted WP sites on different servers.
Array ( [pgID] => [isPosted] => 0 [pDate] => 2016-11-28 18:10:26 [Error] => -=ERROR=- parse error. not well formed )
Damien
ParticipantHi, that doesn’t work anymore. I can’t reproduce that.
Please have a look: https://nervousblazecrown.tumblr.com/post/153681068503/hastag-testRegards. Damien
Dino Ciuffetti
ParticipantThat did the trick. Clicking on “Authorize Your Facebook Account” link on the plugin config panel solved the problem.
Thanks.
Facebook does not restrict accounts for posting or overposting. It usually happens when several people click “Report This Post” link. Which means some people in some of those groups consider your posts spammy or irrelevant.
No, you currently can’t do that, but thanks for the suggestion. We might implement that in a future.
November 16, 2016 at 2:55 pm in reply to: Parse errors testing posts to self-hosted WP sites #520184Anna S
ParticipantCould you specify where I should look for this info?
wp-config.php has charset defaulted to utf8 for as long as i can remember.
I took a quick look at the databases and tables, and they all seem to be utf8mb4 on both source and target.
Also, I attempted to send a test post from target to source…and it worked with no errors.
As a result of digging around in the back end, I noticed some subtle differences between source and target hosts:
Source server:
PHP Version 5.5.36
MySQL Version 10.0.27-MariaDB-cll-lveTarget server:
PHP version: 5.6.23
MySQL version: 5.6.30
Bobby
ParticipantSomeway figured out a fix..I limited the posting with WP Cron and do not autopost more than one post every 2 hours..
If anybody has similar..The above fix will hopefully work for you.
November 16, 2016 at 6:38 am in reply to: Parse errors testing posts to self-hosted WP sites #520082AlexG
Participant-=ERROR=- parse error. not well formedThis error can occur because of wrong character encoding of the blog.
Please make sure the encoding are the same on both blogs (source and target).
Bobby
ParticipantEvery single post is being skipped posting by SNAP Pro as it sees every post as ‘Uncategorized’ – which it is not.
It does not pick up any of the other categories, so essentially misses every single post.
Frustrating problem and I have gone through every setting and filter checking it. It seems to be only picking up the default ‘uncategorized’ posts and nothing else.
- AuthorPosts
