rclinton

Since I regularly keep WP updated, it was the last version of WP 4, whatever that was.

Armando – I did not change the WordPress salts. The plugin simply stopped working with the upgrade to WP 5.0.3 for me. It is good to know that it was a credentials problem even though the plugin gave no error message and claimed the credentials were properly saved.

Bob

Armando:

Even though the plugin said the credentials were saved, reentering them somehow fixed the problem. Thanks for the help.

Bob

Authentication now works but plugin fails to post photo images (which is what I am trying to use it for). Thanks for fixing the authentication issue. Check cybershutterbug on photo.social to see the results from the plugin.

With very little help from the developer, I finally resolved the problem. Turning off and on a number of options (other than the debug option) in the settings several times and saving the changes each time finally got the plug-in up and running again. Apparently the problem must have been some sort of corruption in the plugin settings file. Anyone experiencing a similar problems might try this approach, rather than contacting the developer who was simply insulting and, as this thread suggests, provided little to no help.

I first noticed the donation option when I started poking around trying to figure out why the plugin was not working. I was not, as your nasty reply suggested, trying to purchase your support. So apparently, you are unwilling to assist those who both like your product and try to support it. Based on this experience no one else should try to support you if you are unwilling to assist those who like product and try donate to it. Nevertheless, despite the donation, I am left with a non-working plugin and a developer unwilling to help or support it. Definitely not a good situation nor a strong recommendation for your otherwise excellent plugin (when it works)!

I think I did answer your question and I do indeed know precisely what the debug.log is for. While I am not a programmer, I used to manage computer networks at my regular job as a professor, teaching among other things cyberspace law. Thus, there is no reason to be insulting to one of your fans and donors. What I said in my prior post is that after turning the WordPress debug option on I got normal debug output into log when posting a picture uploaded as a draft before that 400 error. After erasing the debug.log so I could follow the activity on a newly created draft I got absolutely no activity on the posting of the draft for the newly created post. There was no communication with Tumblr, no indication of any effort to do so, and no information reflected in the debug.log. It was as if Tumblr Crospostr was not there or active (when, of course, it was).

When I publish drafts that had been saved before that 400 error, I get a debug output and they publish normally. When I create drafts or publish any post created after that 400 error, there is no debug.log output at all; it is as if the Tumblr Crosspostr plug in were not there even though it is active and works fine for any post originally created before the error occurred. Incidentally, this test just exhausted the last such draft post created before the 400 error.

Turning on the debug mode and trying to save a draft photo post to my website failed to produce either any evidence of upload of the draft to tumblr (which previously would happen) or any debug.log which I checked on my host server’s file manager. Absolutely no evidence of any activity at all!