Why does it attempt to crosspost on “save draft”?

I think a bit of extra information that I observed might help add some context to why it might be happening.

It appears that if you have any post type other than the default, it occurs. Further narrow down to posts that upon “save draft” don’t already have an image link present in the draft (say if you are using image type, or no video for video and so on).

But the problem still remains that while saving drafts, it shouldn’t be crossposting anything and jumping the gun to result in the error. SO waiting to actually crosspost when the intent is made is the proper solution as it shouldn’t be doing anything on drafts, that’s why they are called drafts and not posts. They may never get posted and it is generating tumblr ids on each save which is also not right. It is involving itself in the process way too much before it is time to appropriately invoke itself.

Since Tumblr supports drafts, you can indeed save a draft on both sides of the connection, WordPress and Tumblr. Cross-posting when a draft is being saved on WordPress is intentional. “It is a feature, not a bug.”

it is generating tumblr ids on each save which is also not right.

This is almost certainly because you have set your post format to something like Image but have provided no image; Tumblr rejects these posts as invalid. You should instead use a default placeholder image if you have none prepared, and then save the draft. This way Tumblr accepts the post and returns a Tumblr post ID back to Tumblr Crosspostr.

It is also not clear why we need an add to queue checkbox when it should only be posting when you publish the post

The Queue checkbox is used to support the Tumblr Queue feature, which is a publishing feature that WordPress does not share. A “queued” post is something different entirely; it is not a “published” post, not a “scheduled” post, and not a “draft” post.

TL;DR: Consider reading up on Tumblr’s featureset to learn more about why I made these various design choices in the plugin and it will become less confusing to you.

Sorry for the delay getting back to you, had to deal with some personal health issues.

Since Tumblr supports drafts, you can indeed save a draft on both sides of the connection, WordPress and Tumblr. Cross-posting when a draft is being saved on WordPress is intentional. “It is a feature, not a bug.”

While I appreciate that you have intended it as a feature to cross create drafts on both the site and tumblr, and some may want that; there should really be an option to disable this “feature”. I rather not have a draft mirrored constantly with their servers until I am actually done and publish it.

This is almost certainly because you have set your post format to something like Image but have provided no image; Tumblr rejects these posts as invalid. You should instead use a default placeholder image if you have none prepared, and then save the draft. This way Tumblr accepts the post and returns a Tumblr post ID back to Tumblr Crosspostr.

Of course that’s the reason, I already said so. But it is not a feature when you have to add components to the post that are not organic to it just to avoid the hassle of either facing errors or creating placeholders – when the post is developing organically and trying to make accommodations for the shortcomings of tumblr’s system or your intended feature that is not working nicely with their limitations or design.

Especially in both cases, if you are only sharing excerpts, it really doesn’t need to keep a constant draft mirror with them, it makes no sense from efficiency perspective either.

The Queue checkbox is used to support the Tumblr Queue feature, which is a publishing feature that WordPress does not share. A “queued” post is something different entirely; it is not a “published” post, not a “scheduled” post, and not a “draft” post.

I get that, but I just can’t see the use-case where the queue would be separately necessary outside of the already implemented, publish and schedule. That’s what I was asking clarification on, not what the queue option is on tumblr. If you are going to post something on tumblr, it will and has to be posted on the site as well, right? If so, why is the publish and schedule not sufficient for this?

TL;DR: Consider reading up on Tumblr’s featureset to learn more about why I made these various design choices in the plugin and it will become less confusing to you.

Thank you for what I can only take as a backhanded insult, but I know enough about their system to fit my needs, I don’t have any desire beyond that to know the inner working of their system, that’s why I use this plugin. But understanding how the plugin works in the context of my site is more important to me than how it is replicating tumblr features ?? Thanks.

While I appreciate that you have intended it as a feature to cross create drafts on both the site and tumblr, and some may want that; there should really be an option to disable this “feature”. I rather not have a draft mirrored constantly with their servers until I am actually done and publish it.

Then you should write a patch (or get someone else to do so) and submit it to me for inclusion in a future release.

trying to make accommodations for the shortcomings of tumblr’s system

You should consider filing a complaint with Tumblr. I have done that many times. I have a feeling I am probably more familiar with Tumblr’s technical shortcomings than you are. Complaining to me about Tumblr’s fascistic API does neither of us any good. ˉ\_(ツ)_/ˉ

Especially in both cases, if you are only sharing excerpts, it really doesn’t need to keep a constant draft mirror with them, it makes no sense from efficiency perspective either.

I disagree and have no intention of spending any more of my time debating why with you or anyone else.

I get that, but I just can’t see the use-case where the queue would be separately necessary outside of the already implemented, publish and schedule.

That sounds like a personal issue.

Thank you for what I can only take as a backhanded insult, but I know enough about their system to fit my needs, I don’t have any desire beyond that to know the inner working of their system, that’s why I use this plugin.

That’s right. You decided to let someone else do the work of learning the ins and outs of Tumblr’s system for you. That person happened to be me. I’m sorry you don’t feel like I made the choices that were best for you. If you want something done the way you want it done, maybe you should consider doing it—or paying for it—yourself next time, instead of taking advantage of free software you didn’t write and then dictating how it “should” work for other users while simultaneously admitting you have no real interest in learning more than you care to about the details of how what you choose to use actually works. Food for thought.

Then you should write a patch (or get someone else to do so) and submit it to me for inclusion in a future release.

I really don’t understand the hostility and lack professional conduct here. I know you are self admittedly homeless and do what you want when you want but you are either serious about the credibility of what you do or you are not; being dismissive and rude is hardly a mature response.

You should consider filing a complaint with Tumblr. I have done that many times. I have a feeling I am probably more familiar with Tumblr’s technical shortcomings than you are. Complaining to me about Tumblr’s fascistic API does neither of us any good. ˉ\_(ツ)_/ˉ

Again, their “fascist” API didn’t make you force mirror using your extension when it is not necessary or offer an option to not do it and causing issues that require accommodation. That was YOUR choice. You probably are more familiar with it, because you chose to be, no one forced you to do it; but to say because you have, somehow you get to be dismissive shows low moral character since we are being blunt apparently and you don’t seem to favor civility of intelligent discussion.

I disagree and have no intention of spending any more of my time debating why with you or anyone else.

Now who is being a fascist? Refusing to have an intelligent discussion where you can explain to those who don’t have mind reading capability as to the reason for the logic chosen. If you can’t explain it, lest defend it, then it shows you already know it is wrong and hiding behind belligerence because your ego can’t handle admitting that it is probably a bad approach.

That sounds like a personal issue.

Again, explaining a feature is the basic tenet of a good project, not a personal issue, unless you are referring to yourself.

That’s right. You decided to let someone else do the work of learning the ins and outs of Tumblr’s system for you. That person happened to be me. I’m sorry you don’t feel like I made the choices that were best for you. If you want something done the way you want it done, maybe you should consider doing it—or paying for it—yourself next time, instead of taking advantage of free software you didn’t write and then dictating how it “should” work for other users while simultaneously admitting you have no real interest in learning more than you care to about the details of how what you choose to use actually works. Food for thought.

NO, I didn’t let or choose anything, you did. You wrote it, no one asked you to do it and now you are acting high and mighty when someone suggests that things could be done better. I didn’t ask you to customize shit for me, I am saying that there is a better way of approaching it that provides the most flexibility to the user intent without forcing YOUR behavior on everyone. That shows lack of integrity really and maturity to handle constructive input that is being provided at ones own time and expense. Nothing excuses your response or behavior because it shows you lack the temperament to be a developer or even responsible enough to entertain anything that doesn’t fit your view – by the way, the very definition of fascism in case you were wondering. What I said honestly and sincerely, unlike your approach, is that I don’t plan on developing for it so while I know fully the technical workings of it, I don’t need to drill it down to the level of writing logic for it. So please don’t presume to interpret what I mean and try to twist it to fit your tantrum.

I am sorry that I took the time to give you the respect to discuss this with you and will now move on accordingly and shun any piece of crap you make in the future. You clearly thrive on hostility and feed off negativity and chaos, I have no interest in that. That is probably a reason why you can’t hold down a real job and have to live off good will of others, which you apparently have no interest in earning either. Food for thought.

If you can’t explain it, lest defend it, then it shows you already know it is wrong and hiding behind belligerence because your ego can’t handle admitting that it is probably a bad approach.

Literally my first sentence in response to your post was the explanation. You just seem to not want to hear it; another personal issue, it seems. I’ll copy-and-paste it again, for your convenience:

Since Tumblr supports drafts, you can indeed save a draft on both sides of the connection, WordPress and Tumblr. Cross-posting when a draft is being saved on WordPress is intentional. “It is a feature, not a bug.”

Also, you wrote:

I really don’t understand the […] lack professional conduct here.

You aren’t in a corporate space; you’re not dealing with a customer support department. Surprise! That said, I’d be happy to refund you the full purchase price of this free plugin. ??

On that note, I’m marking this issue as resolved. Additionally, to the WordPress moderators, please close this thread. Thank you.

This matter is not resolved but given the lack of any competent response, I vote to have it closed as well.