someoneoutthere
Forum Replies Created
-
Thanks for the update. Although I haven’t experienced any problem after I marked this as resolved (except two days ago when Automattic disabled G+ connection probably deploying the new version, but that got fixed by the next day based on my local time), but thanks for letting me know. I reconnected into G+ again and saw that I don’t need to use 3rd party password and the post is automatically set to public by default which is good 😀 (back then I had to manually adjust the post setting to public on G+ setting everytime I disconnect/reconnect).
- This reply was modified 9 years, 7 months ago by someoneoutthere.
- This reply was modified 9 years, 7 months ago by someoneoutthere.
It is a known problem unfortunately. In the meantime you can do follow this to fix the issue https://ww.wp.xz.cn/support/topic/problem-with-publicize-after-updating-to-421/#post-7682854
Your domain name is currently in redemption period probably because it was expired on July and you didn’t extend. To solve it, you need to contact the registrar where you bought that domain name.
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 :).
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.
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.
I’ll be waiting for the update and going to install it right away after it comes out, and will let you know after 🙂
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://ww.wp.xz.cn/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.
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).
Just an update, it’s been a week since I first reported and I’m still having the same problem. I was told via email by Jetpack support staff that they currently don’t have ETA for this issue because they can’t reproduce it and so I decided to post this over at forums again, because one of the post made by Jeremy here at https://ww.wp.xz.cn/support/topic/publicize-not-working-for-scheduled-posts-4?replies=6#post-8803427 made auto posting to Google Plus work again … once.
So here is a summary for Jeremy ( my ticket number is #2784644 ), hoping that maybe Jeremy can help me with my problem:
– I have wp-cron disabled in wp-config (DISABLE_WP_CRON true) not ALTERNATE_WP_CRON.
– 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
– Using the add_filter you described at other’s post
add_filter( 'jetpack_sync_listener_should_load', '__return_true' ); add_filter( 'jetpack_sync_sender_should_load', '__return_true' );– It work .. for once only, then I made another scheduled post (scheduled to be posted within 2 minutes) and it won’t get posted at all to my G+.
Is there any other solution I could try?
Still not resolved for me, in fact I just discovered another problem. In jetpack stats module, all the post written after I upgraded to 4.2, are linked using the post id rather than the pretty permalinks.
To make things clear, post that were made before updating to 4.2 are linked like this:
myurl.com/pretty-permalink
and then post that were written after updated to 4.2:
myurl.com/?p=12345
In reality the post is using pretty permalink but in wordpress stats page, despite showing the correct title, it is linked using its post id.
Also I’d like to mention, actually before I updated into 4.2.1 on Friday, I was using 4.1.1 and it works great no problem at all. I tried looking at what’s changed on Github, but there are way too many changes.
Disregard my last post, it is back to not working again in 4.2. I switched back into 4.2.2 and made another test post, but still problem persist. I’ll be waiting for an update then.
Thank you very much for the workaround Francisco, it works great and I’m able to connect as my page again.
Unfortunately the first publicize problem for me is still persist, in fact I just tested again with another test post earlier today aftar updating to Jetpack 4.2.2 but still not working.
Then I decided to revert into 4.2 (the last working version) and made another test post, and it gets posted automatically to social media, so I guess the problem is due to something changed in 4.2.1 and 4.2.2.
I’ve made another support request using the post I made here. The site url in question is also listed there.
Thanks 🙂
Is there a pm function? Actually I sent the information via the contact form in Jetpack website twice. First is to report the publicize issue, the second is the google plus issue but still haven’t received any response at all.