Strange, I’ll take a look this evening! Thanks for reporting.
its not just your plugin, tried others and Jetpack is doing to any one I enable…
thanks for follow-up, curious to hear if anyone else experiencing this or it is perfect storm of my install
I tested with JetPack with no issue. I have debug enabled. How do I reproduce?
Thanks
Hi – thanks for following up
probably impossible to reproduce, and it really “isn’t your fault”
As I explored this issue there are a whole bunch of people that ran into a lot of different problems after the last Jetpack update.
I actually had to delete it and all the data to keep it from conflicting with ANY coming soon plugins, even when disabled it was throwing errors
ultimately after uninstalling, installing jetpack a few times and your plugin and other plugins and just being miserable, I found a thread where jetpack said to install latest jetpack Manually…
that worked, and cleared up problems, I also found a plugin that disables most of the stupid default activated features they force upon you, so now things working smoothly
turns out not really a bug (yes guilty of always thinking that)
from:
Jeremy Herve
Happiness Engineer
That’s indeed to be expected. Jetpack uses your site’s XML-RPC file to communicate with WordPress.com. Unfortunately, coming soon plugins often block access to that file, alongside with all the other pages on your site.
To avoid such issues, I’d suggest using Jetpack’s Development mode as long as your site is not live. You can use a plugin like this one to enable Jetpack’s Development mode on your site:
https://wordpress.org/plugins/surbma-jetpack-development-mode/
Strange, I don’t think the plugin blocks that request. It only runs on the front facing part. Looking into it now.
I just checked and that url is not blocked on my test instance. What’s your url? Does it work if you disable?
hi since I implemented that plugin to limit jetpack modules I’m not having problems anymore, thanks
