Problems with publicize after updating to 4.2.1

Resolved someoneoutthere
(@someoneoutthere)

7 years, 8 months ago

Hello,

Actually I’ve used the contact form to contact for Jetpack support directly, but because I saw Jeremy Herve is currently active answering on forums maybe you can help me with this problem I’m experiencing.

So basically I have two problems:

1. Publicize does not work at all after updating to 4.2.1 earlier today. No posts were made at all to all the services I’ve connected to.

I’ve tried:
– disconnecting + reconnecting all of the publicize modules
– disabled + reinstalled jetpack
– disabling publicize module directly and reenabled it again

But still it won’t work. The last time it worked was yesterday, or the day before I updated into 4.2.1.

I don’t know what caused it but I’m planning on reverting tomorrow in case the problem still persist in hope that it would auto post at least to both Twitter and Facebook while I’m waiting for a solution for the Google Plus connection because after I noticed it isn’t posting updates at all, I had to manually post all of my posts into Twitter, Facebook, and Google Plus which is too tiring.

2. I couldn’t connect to Google Plus using my page name. Previously it is working, but because I’m trying to troubleshoot on why the publicize module won’t post anything at all, I removed all the connections and tried to connect them all again once by once … and this is where the problem appear. I couldn’t connect to my Google plus as my page at all again.

I’ve tried:
– returning to previous jetpack (4.2)
– disconnecting wordpress in apps setting in google plus both as business page and personal
– removing wordpress from the accounts page (accounts.google.com) under apps both page and personal
– waited for 1++ hour in case the connection was cached by wordpress and/or google but still no go.

Thank you very much for your help.

https://wordpress.org/plugins/jetpack/

Viewing 15 replies - 16 through 30 (of 31 total)

← 1 2 3 →

Plugin Author Jeremy Herve
(@jeherve)

Jetpack Mechanic 🚀

7 years, 7 months ago

I have a curl configured to fetch /wp-cron.php (without args) once every minute but not /wp-cron.php?doing_wp_cron=rand_numbers because if there’s args then the scheduled post won’t get posted at all

wp-cron.php?doing_wp_cron should be enough.

Using the add_filter you described at other’s post

The filters are indeed necessary right now, when WordPress’ Cron system is disabled and when you use your own custom Cron. We’re working on a more permanent solution, that won’t rely on the filters. It will be part of the next release.

I made another scheduled post (scheduled to be posted within 2 minutes) and it won’t get posted at all to my G+.

Could you send us more information about that post via email, so we can take a look at our logs for that post?

Thanks!

otechwebmaster
(@otechwebmaster)

7 years, 7 months ago

After few years with jet pack I’m Considering to delete the plug-in the reason for that being never ever ever works properly and correctly always gives errors and slows down the site.

And replacing it with Rss feed + https://ifttt.com = less headache

Plugin Author Jeremy Herve
(@jeherve)

Jetpack Mechanic 🚀

7 years, 7 months ago

@otechwebmaster If you’re running into issues right now, could you please start your own thread, as per the Forum Welcome, and give me some details about your site, your set up, and the issues you’re having?
http://wordpress.org/support/plugin/jetpack#postform

I’ll be happy to help!

Thank you!

Thread Starter someoneoutthere
(@someoneoutthere)

7 years, 7 months ago

Hello Jeremy,

I’ve tried many times (in fact I lost count because I’ve tried so many times) disconnecting from both plugins page in my site or wordpress.com/sharing page then disconnect in the G+ Apps under settings and then reconnect again even with the filter added into functions.php and also curl running once every minute fetching /wp-cron?doing_wp_cron. Also I’ve tried disconnecting from jetpack and then reconnect jetpack again. All of them aren’t working.

Every single post that was posted to G+ since last week are all entered manually by me except 1 post that gets posted successfully a few days ago. So if you need to see which post that didn’t get autoposted, actually it’s all of them even for today’s post :(.

If you need to see my site, I listed it in ticket #2784644 (it’s already closed now without a solution).

Plugin Author Jeremy Herve
(@jeherve)

Jetpack Mechanic 🚀

7 years, 7 months ago

I see my colleagues Ryan and Carolyn have been working with you on that problem, and reported the problem to our developers. We’ll get back to you as soon as we have some news!

Thread Starter someoneoutthere
(@someoneoutthere)

7 years, 7 months ago

Okay thank you Jeremy, but is there anything else that I could try right now?

Also it’d be great if you could tell me what kind of error that is being displayed at Automattic side for my site, like Jetpack server couldn’t access my server or anything else? because in my error_log there’s nothing.

Also I’d like to mention that publishing right away also resulted in the post not being autoposted to social media. Another poster is also experiencing this at https://wordpress.org/support/topic/publicize-not-working-if-post-is-first-saved-as-draft .. but in my case, I don’t use any plugins that is listed there other than Jetpack.

I haven’t tested whether publishing right away without saving as a draft first would work, because I’d never do that in real situation.

This is what I always do: write -> save draft -> preview -> edit as needed -> save draft again -> preview -> is everything ok? -> then schedule.

Plugin Author Jeremy Herve
(@jeherve)

Jetpack Mechanic 🚀

7 years, 7 months ago

is there anything else that I could try right now?

I’m afraid not.

We do however plan on releasing a new Jetpack update later this week. Once you’ve installed the update, I’d recommend that you try resetting your Publicize connections, and then see if that helps.

If that solves the issue for you, please let us know!

Thread Starter someoneoutthere
(@someoneoutthere)

7 years, 7 months ago

I’ll be waiting for the update and going to install it right away after it comes out, and will let you know after 🙂

Thread Starter someoneoutthere
(@someoneoutthere)

7 years, 7 months ago

Just wanted to post an update. I merged the commits made by ebinnion over at https://github.com/Automattic/jetpack/pull/5036 to the current 4.2.2 that I’m using (because 4.2.3 is still not out yet), and so far 2 posts gets posted automatically to G+. Will be testing again tomorrow, and hopefully it’ll stay this way :D.

Thread Starter someoneoutthere
(@someoneoutthere)

7 years, 7 months ago

Everything is good now. Even on the new 4.3. Although there’s a problem with static.html because of some restrictions I’ve placed, but after I’ve made an exception for it so it can fetch the static.html file, everything seems to be okay.

Plugin Author Jeremy Herve
(@jeherve)

Jetpack Mechanic 🚀

7 years, 7 months ago

Although there’s a problem with static.html because of some restrictions I’ve placed, but after I’ve made an exception for it so it can fetch the static.html file, everything seems to be okay.

That’s indeed a known issue with Jetpack 4.3. We’ll get that fixed in 4.3.1. Could you let me know what plugin you used to add those restrictions on your site?

Thread Starter someoneoutthere
(@someoneoutthere)

7 years, 7 months ago

Hello Jeremy, sorry for the delay in response because I didn’t notice it until today. About the restrictions, actually it’s not a plugin but a server side adjustment (a WAF to be precise).

I noticed that because after updating and logged in, I get static html error message and so I checked the server log and saw that it was trying to fetch the html file using GET request. So I made an adjustment.

But after I saw that in 4.3.1 it’s been changed into file_get_contents rather than wp_remote_get again, I switched it back on again :).

Plugin Author Jeremy Herve
(@jeherve)

Jetpack Mechanic 🚀

7 years, 7 months ago

2. I couldn’t connect to Google Plus using my page name.

Google just replied, and the problem is now fixed. You should now be able to link Publicize to your Google+ Page!

Plugin Author Jeremy Herve
(@jeherve)

Jetpack Mechanic 🚀

7 years, 6 months ago

@adnanguney Google indeed made some more changes to their settings screens, and it’s currently not possible to manage existing connections or change privacy settings for connected apps.

We’re working with Google to find a work-around to this problem. I’ll post again here as soon as I have news.

Plugin Author Jeremy Herve
(@jeherve)

Jetpack Mechanic 🚀

7 years, 5 months ago

Hi there,

I have good news!

A few weeks ago, Google+ made some changes to their API. In doing so introduced some issues with Publicize. The module still worked, but the updates posted by the WordPress app on your Google+ Profile or Google+ Page were only visible to you.

In the past few weeks, we’ve worked with Google+ to start using a new API. That API works just like the old one, with one exception: publicized posts are now public. You can’t change the visibility of publicized posts to “My Circles”, or anything else.

If you’re happy to have Publicize publishing public posts to your Google+ Profile or Page, you can follow the instructions below to delete your old connection, and then reconnect your Jetpack site to your Google+ account:
https://jetpack.com/support/publicize/google/#reconnecting

I hope this helps.

Viewing 15 replies - 16 through 30 (of 31 total)

← 1 2 3 →

The topic ‘Problems with publicize after updating to 4.2.1’ is closed to new replies.

Tags