mattsaler

Ah, glad to hear it! We ended up going with a different solution, however. Good luck, @tgakk!

Excellent news! Thank you!

I had this same issue with a client site. The unblock links users received didn’t work, and neither did the unlock mechanism in the WP admin. I ended up having to delete the locked user rows from the database to free up a corporate IP range. I disabled the lockout feature for now.

As of this morning, looks like we’re all set. Thanks!

Ah, looks like it went to Spam. Thanks!

I also went ahead and purchased the Pro version of the plugin. Thanks!

Hi Ben,

My message get through okay? Thanks!

100% sure, yes. I’ll send you a message now.

In the browser, I get a 405, with this notice: “XML-RPC server accepts POST requests only.”

That’s always been the case, though. Even syndication was working.

What type of request to the XMLRPC file does the plugin make? Our host by default only allows POST requests to the file, but I may be able to get them to move on that. I’ve confirmed that the response to POST is 200.

I’ve reset the user account password again and still receive the same error. On the plugin screen, it reads after a manual pull: “Access denied to server. Your subscription may not be active OR your login details are incorrect.” That’s not true, though, and it’s always said that for manual pulls. But the post-publish push worked until after 5/19.

I’ll have to discuss disabling the user role plugin with my developer—the site is in production and the URE plugin is a key piece.

I reset the password on the Syndication account last week to make sure the plugin had the correct information. We’ve gotten that username/password error on manual syncs since we started using the plugin—but the automatic transfer of content at post publication was working before this issue, so we weren’t too concerned about it.

The user was added on 5/17. The last successful content pull/push was 5/19. In that timeframe, there have been no new plugins added. Just routine maintenance updates to existing plugins. No new development on either site has taken place either. The Syndication plugin debug log has what looks to me to be a normal entry for 5/19, then there is no entry until 5/23:

[23-May-2016 12:32:19 UTC] This is a message from your Content Syndication Toolkit wordpress plugin.

There was an error when trying to get new syndication posts from the content creator. All posts in this import will need to be reimported.

Please login to wordpress and make a manual content pull request using the plugin tools under “Settings -> Content Syndication” in the wordpress admin area.

Here is the error message:

“failed to import: post [username].”

Again, “[username]” is the user from 5/17. That error repeats until the 25th, when I reset the index. Then we started getting:

[25-May-2016 13:17:26 UTC] This is a message from your Content Syndication Toolkit wordpress plugin.

There was an error when trying to get new syndication posts from the content creator. All posts in this import will need to be reimported.

Please login to wordpress and make a manual content pull request using the plugin tools under “Settings -> Content Syndication” in the wordpress admin area.

Here is the error message:

“Problem contacting the server. Please confirm your API Username and Password are correct. Error: transport error – HTTP status code was not 200”

The new user is a normal human user with the Author user role. We have some modified user permissions through the User Role Editor plugin so that “Author” is not identical to WP’s default “Author”.

The Syndication plugin is still running through the account assigned to the Syndication Sub role. That has not changed.

So there is no way to hook into the future_posts status and add a capability? Scheduled posts are not published. Prior to December 2015, users who were allowed to edit posts that hadn’t yet been published could also edit scheduled posts. So something changed.

Bump. Anyone? I can’t be the only person who’s wanted to change the Press This panel…