macgeekgab

and how about WordPress 4.9? We’re running it on that, but I’m getting a little concerned about the fact that this hasn’t been updated for 7 months. Hrm.

We’re in need of this, too. Right now the like/dislike buttons eat up a *ton* of vertical space, and like @bumpycase, we’d like to collapse that next to a line with reply/datestamp/etc. Any advice you can give us on perhaps taking what we’re doing with that and embedding it alongside your display?

We just began experiencing this, seemingly out of the blue, though I’ve used computers long enough to know that we obviously changed something, even inadvertently.

We noticed it on our production environment first, which was updated to 4.8, and then tested on our development environment (same server), which was still on 4.7 (I know…). Same issue. So we left our dev environment at 4.7 and disabled all of our plugins and reverted to the 2016 theme and… it still happens. We get “missed schedule” within 60 seconds of the time that it should fire.

We get plenty of traffic to the production environment, and other cron-dependent things fire off just fine, so it’s not the low-traffic-causes-cron-to-be-missed issue. Despite that, though, we tried it by manually triggering wp-cron.php and it behaved exactly the same.

Thinking it must have something to do with our server environment, we tried it on another, existing WordPress site on the same server that gets zero traffic and is still on 4.7. It’s using the default theme and also has no plugins. On this one it works perfectly, and scheduled posts go live as scheduled.

Any thoughts?

• This reply was modified 7 years, 9 months ago by macgeekgab.

I started getting this error this afternoon, and even wordpress.com/sharing can’t connect (nor can any of my sites). Our xmlrpc.php file appears to be accessible just fine.

Is something amiss with JetPack or WordPress.com at the moment?

Saw this and then saw the post at https://www.ads-software.com/support/topic/publicize-outage/ … didn’t seem to be able to delete this comment.

• This reply was modified 7 years, 9 months ago by macgeekgab.
• This reply was modified 7 years, 9 months ago by macgeekgab.

I noticed this, too. Moving from RSS publication to API publication with this plugin resulted in this going missing. Here are screenshots from our Apple News page with the differences. It’s just a link to the canonical URL. Seems Apple was putting it in automatically for RSS-based articles, but leaving that formatting up to you/us for API-based ones… and I’d love the option of putting it back in. ??

An update: 4.2-rc4 fixes the issue and re-allows Publicize to work on Custom Post Types.

I think I’ve also found the hole on the main issue.

If the user that is publishing the post does NOT have Publicize enabled for themselves (i.e. if they have not attached one of their own accounts via Publicize), then Publicize will post to *all* of the accounts I have linked to my account (shared and not-shared alike).

But, if someone has attached just one account to their Publicize settings, then THAT account gets the post plus all of my Shared connections, but none of my unshared.

So this issue seems very much to be related to the way Publicize handles things if the posting user has NOT signed up for Publicize. That make sense?

Just circling back on this. I saw Version 4.2-rc4 get pushed and we’ve updated to that. Should we be seeing fixes to the custom post types bug or the publicize/sharing issue?

Thanks for giving that a try!

Could you try clicking on “Perform Full Sync” at the bottom of this page?
https://wordpress.com/settings/

Once you’ve done so, try publishing a new post and let me know how it goes.

I looked but don’t see the “Perform Full Sync” option at all. I tried a few accounts that have different Jetpack-enabled sites and… still don’t see it. It asks me to select a site, and then when I select it I get a screen full of different options, but nothing about Sync. Maybe I’m looking in the wrong spot?

@jeremy –?perhaps worthy of a different thread, but since installing the beta, Publicize no longer works at all on our custom posts. Regular posts, however, are still going out to all (even unshared) connections.

Thanks, Jeremy. And no problem. We installed the latest beta (4.2-rc1) and then reset the unshared connections. Still the same result: full tweets went out everywhere. What else can we try to help narrow this down?

We disabled the Edit Author Slug plugin, no change. Unshared accounts still get everything published by anyone.

In case it helps, here are the other plugins we’re running:

Advanced Custom Fields PRO
Kismet
Basic Comment Quicktags
Google CSE
Gravity Forms
WooCommerce
WordPress Social Login
Yoast SEO and News

Additionally, we have added some of our own functionality through a single, custom plugin. @maccast knows more about the specifics of that (because he wrote it!). We can dig into it, of course. Can you tell us what hooks we should be looking at to see if we broke something there?

As I mentioned, the Publicize UI on the edit post pages all looks fine: authors only see Shared or their own. It’s just when publishing that all of them get used.

Thanks so much, Jeremy!

Thanks, Jeremy. We’ll run a test today. As for the steps, it’s really nothing different than I’ve done on any other wordpress install. We populate the content, of course, and then hit Publish. Sometimes we edit the date to schedule a future post, sometimes we click “Edit Details” on Jetpack’s Publicize to change that, but other times we leave them all at defaults. I don’t *think* we’re doing anything out of the ordinary on this.

Sure thing, and thanks!

I removed and re-added the unshared connections, and it’s still happening. https://www.macobserver.com is us, and this tweet should not have been posted (because the article was published by someone else).