• Resolved ereckers

    (@ereckers)


    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.):

    http://www.mydomain.com/xmlrpc.php

    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.

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Richard Archambault

    (@richardmtl)

    Hi!

    if you’re using the dev mode constant, you shouldn’t even be getting a “Connect to WordPress.com” button, so I’m a little uncertain as to what it going on here, to be honest. Where in the wp-config.php file did you put the line? Did you put it before the

    /* That’s all, stop editing! Happy blogging. */

    ?

    If you want, you can post your wp-config.php files on pastebin.com so I can take a look (be sure to remove any passwords or other identifying info first, though!)

    Thread Starter ereckers

    (@ereckers)

    Rich,

    Yes, I’ve got the constant added before the “That’s all…” line. I’m using:

    On a whim I just tried it on an entirely different dev instance and this time I got it to work.

    I think there’s probably an issue with by plugins or theme and I can go ahead and investigate that myself. The DEBUG flag does work on a cleaner installation, so I’ll mark this as resolved.

    Thanks,

    Ed

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Issues Developing with Jetpack Locally’ is closed to new replies.