Jetpack’s Publicize feature won’t work for plugins/scripts that don’t the default post method by WordPress as it skips some checks set by Jetpack to run those Publicize jobs.
Could you try manually publishing one post on your kernel-sesias.net site and see if that works?
Thank you for the reply! I manually published an article and is actually shared on all 4 platforms. Is there a way to solve the problem? Until two weeks ago this did not happen and everything worked perfectly!
Thank you
Hi there, the only thing I can suggest in this case is to roll back to an older version of your posting plugin – I am assuming that an update would have changed its behavior.
Unfortunately Jetpack will only Publicize posts if the post is published using the default WordPress flow.
Thank you for the reply.
How do I download the previous version (5.0)?
Thank you
You can find a list of our previous versions on this page here:
https://wordpress.org/plugins/jetpack/advanced/
Please select version 5.0 and click download
Hi Lamday,
I installed the old versions (5.0, 4.9, 4.8) but the problem is not resolved. On another platform, I changed the communication protocol from https to http to line 17 in the jetpack.php file and seems to work all over again.
This may be the problem (maybe an incompatibility with WordPress version 4.8) or is it just a case?
Hosting the two platforms is the same.
original:
/*defined( ‘JETPACK__API_BASE’ ) or define( ‘JETPACK__API_BASE’, ‘https://jetpack.wordpress.com/jetpack.’ );*/
edited:
/*defined( ‘JETPACK__API_BASE’ ) or define( ‘JETPACK__API_BASE’, ‘http://jetpack.wordpress.com/jetpack.’ );*/
Thank you
Hi @acicciu
Sorry about the delay in writing back to you!
That’s interesting. Changing that line will force the outgoing requests to HTTP – Which suggests that your host could be blocking outgoing HTTPS requests.
Are you running the same plugins on your other site? ie. Cybersin?
Also, if you you need to change that setting for Jetpack to work, you’re better off using a filter:
define( ‘JETPACK_CLIENT__HTTPS’, ‘NEVER’ );
Add this into your theme’s function.php file or a code snippet plugin, this will ensure that no future updates will overwrite the change you made to the core files.
Cheers.
