Issues Developing with Jetpack Locally
-
I’m trying to develop locally with Jetpack v2.8 by defining the jetpack debug line in wp-config.php:
define(‘JETPACK_DEV_DEBUG ‘, true);
I’ve tried it in 2 different configurations and get issues in both:
1. A local dev instance in which I’m pointing a domain to the instance (www.mydomain.com). I’m getting the following error when trying to Connect to WordPress.com
xml_rpc-32601
I checked the following URL and it is available and returns (XML-RPC server accepts POST requests only.):
I’m actually trying this on 2 different local development environments which both appear to be setup correctly. 1 is nginx, and the other apache.
2. I also tried it on dev.mydomain.com which is on a public server. However, I do have apache auth on it (user/pass) and I’m getting the following error when trying to Connect to WordPress.com:
Your website needs to be publicly accessible to use Jetpack: site_requires_authorization Error Details: Jetpack requires your site to be publicly accessible.
The question with this one, is that if I have Jetpack DEBUG mode on should it work with a password in front of the domain?
— those are my 2 issues
The last time I developed with Jetpack locally was when we used to go into core and for a flag to On. This is the first time I’ve tried with with the DEBUG flag in wp-config and I’m wondering if I’m missing anything here.
The topic ‘Issues Developing with Jetpack Locally’ is closed to new replies.