Tumblr Crosspostr Mysteriously Stopped Working

Does turning on “Detailed debugging information” in the settings yield any additional information when you encounter the problem?

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!

Did you also turn on WP_DEBUG and WP_DEBUG_LOG in your wp-config.php file like the setting description clearly explains you need to do to get a debug.log file?

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.

You’re not answering my question, possibly because you don’t know what the debug.log file is for.

If that’s true, consider reading Debugging in WordPress and then re-reading my previous post.

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).

What I said in my prior post is that after turning the WordPress debug option on I got normal debug output into log

This is exactly the part of your prior post that was unclear. If asking for clarifications offends you, I’d really rather not bother trying to help you at all. Further, my records show you donated for your use of the plugin, which you say you’ve been using for years, moments before you posted your support request, so forgive me for being skeptical about whether I would have seen support from you unless you needed immediate support from me; you didn’t donate because you were using the plugin, you were “donating” because you were thinkink it of it as buying technical support service.

But technical support, like the plugin code in the first place, is not for sale. It’s all volunteer. If I wanted to have customers, I would have sold this plugin instead of giving it away as free software. But obviously I don’t because I didn’t, and it’s very insulting to be treated like someone trying to do something that one isn’t. Perhaps you know the feeling. ??

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)!

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.

As you can see from a quick browse over the rest of this support forum, not everyone has had the same experience as you. You might serve yourself well asking why you did not inspire much desire to support you when, clearly, others do.

Also, just about every WordPress plugin on this repository has a donation link on its readme page, and Tumblr Crosspostr and my other plugins include such a link *right in the description of the plugin in the list of plugins in your Dashboard,* among several other places like the plugin’s setting screen. I really don’t buy your “dog ate my homework” excuse that you first noticed its existence just recently.

Regardless, I’m glad to hear the issue is resolved. Thanks for sharing your solution.