Su

As a minor note that I forgot to include, it only ever double-posts. It’s never done three, for example. Whatever information that might suggest.

Upgraded a bit ago and things seem to be behaving. Thanks for taking care of it.

It hasn’t been updated in five years. That’s probably your answer. I’ve managed to stick with it this long, but something in WP4.9 has started making it list piles of phantom posts that ruin the queue.

There’s another plugin, Auto Post Scheduler, that’s pretty similar in purpose. It’s missing a few features from A-SP here, but they’re generally the more obscure ones so it might not matter, and it adds a couple of things that might be good to have, as well.

All better. Thanks.

Commented at Github, where it seems more appropriate for this to continue. Guess you can close this out for cleanliness and anyone interested can follow along there.

All better now.

Following up as moderation didn’t allow me to fix the original message. To clarify: markup added in the WP field gets presented properly on the front end, with “Book Title” italicized. Tumblr shows as it is above, with the markup itself visible.

Same here.

If it’s somehow relevant, I do use ACF(4.4.2) in this install, but am not using Buckets in combination with it.

Confirmed fixed for me. Thanks.

Confirmed. Thanks for the quick work on this.

Unfortunately, there seems to be something more involved going on. See also my other thread about the previous version(3.7) still breaking with 4.2, but in a different way.

So, even though the blank screen is somehow related to the function I mention here, something about WP 4.2 itself might also be part of the problem.

I can confirm the problem occurs after 4.2.

I just found the option for this module on the PF preferences screen, and had no recollection of toggling it on, so to be sure I just threw together a completely new copy of WordPress 4.1, installed the latest PressForward and yeah, it’s definitely on by default over here.

Duplicated, though I think your reason is slightly off. The problem isn’t quite the date exactly, but the time. Can you confirm that setting the action into the future by an amount greater than your GMT offset works? (So, if your timezone is at -6:00, schedule for 6hrs in the future and it fails, but 6hrs+5min into the future succeeds.)

It looks like this was supposed to be resolved in this older thread but the reporter there never came back to confirm.

The 404 module was removed in version 2.3.0, with the feature moved to the top level of the plugin’s nav, though no idea why export disappeared. I was looking for it myself.