[Plugin: Jetpack by WordPress.com] Local testing version

  • Resolved jfrankli

    (@jfrankli)


    12 years, 5 months ago

    Is there a way to activate the JetPack plugin on my locally running copy of WordPress on my MacBook? I saw a message that said “site_inaccessible”. Error Details: The Jetpack server was unable to communicate with your site [IXR -32300: transport error: http_request_failed Couldn’t resolve host ‘wptest’]

    Is there a way to make this work in my local development environment? The web site that I run is only locally accessible on my Mac.

    https://www.ads-software.com/extend/plugins/jetpack/

Viewing 15 replies - 1 through 15 (of 35 total)
  • Plugin Contributor Tim Moore

    (@tmoorewp)

    Currently, no, it is not possible. We are considering ways to make this available so folks can test Jetpack with development sites, but I don’t have an ETA on if or when it will be possible.

    I can understand that jetpack needs wp.com for the comments and stats, but there is no reason that the widgets and the gallery isn’t accessible locally

    I have two modules activated that jetpack can replace but I have no way to test this. It’s not an option to do this on a busy site so offline testing is mandatory. Now I can only use it for the stats.

    +1 for local development capability.

    +1 as well. This is a pretty major hindrance to the development cycle.

    +1 yep, what they said…
    I think developers would be more than OK to accept that some features or obviously not available when the website is not public. Needing to dev on a live server is really time consuming…
    Thanks!

    squeakydave

    (@squeakydave)

    +2 from me. Jetpack consolidates quite a bit of useful functionality in one up-datable place. Ideal for my clients. Offline testing is a must.

    phoenixMagoo

    (@phoenixmagoo)

    +1 from me. I really need to be able to get everything going on a development server before moving into production.

    msenate

    (@msenate)

    +1, indeed. Considering making the switch and this is the only thing holding me up.

    319

    (@noyz319)

    So this has been resolved?

    peterwsterling

    (@peterwsterling)

    +1 here too: it’s essential to be able to test out features and configurations before releasing in to the wild…

    Cristian Nistor

    (@cristian-nistor)

    +1

    I vote for this option too

    adding my name to the list – this is essential for me when developing client sites.

    (i’m not sure why this thread is marked as resolved, it’s certainly still an issue as of version 2.0.2)

    edwinvanolst

    (@edwinvanolst)

    +1

    For now, you can trick jetpack into thinking it is connected by modifying plugins/jetpack/jetpack.php (version 2.0.2 on wp 3.4)

    Edit is_active() around line 274:

    function is_active() {
	return true;
	//return (bool) Jetpack_Data::get_access_token( JETPACK_MASTER_USER );
}

    Edit $is_connected and $is_user_connected in admin_page() around line 2213:
    $is_connected = true; //Jetpack::is_active()
    $is_user_connected = true; //$user_token && !is_wp_error($user_token)

    source

    pjv

    (@pjv)

    I also don’t understand why this is marked resolved. edwinvanolst’s hack notwithstanding, there is still no proper way to test jetpack prior to putting it into production.

    I started another thread about the same issue with a little twist here.

Viewing 15 replies - 1 through 15 (of 35 total)
  • The topic ‘[Plugin: Jetpack by WordPress.com] Local testing version’ is closed to new replies.