WordPress.org

Ready to get started?Download WordPress

Forums

Jetpack by WordPress.com
How to test? (5 posts)

  1. pjv
    Member
    Posted 1 year ago #

    comment: in my humble opinion, you guys are rolling out new features way too fast with all the show-stopper issues that have remained un-addressed in this support forum since the 1.8.x version of Jetpack.

    question: i'm admin of a busy, professional wp site. i can't afford to take the production site off-line so i have a test version of the site that runs in a virtual machine upon which i test every change before pushing into production. the test machine must of course have a different URL from the production machine and this seems to make it impossible to really test Jetpack upgrades since many of the Jetpack features, and apparently some of the associated db keys at wordpress.com depend on the connected wp site's specific URL.

    We recently went through a very stressful several days where we had lost all of the stats and all of the subscribers to our blog due to the test version of the site connecting via the same wordpress.com login as the production site and the db at wordpress.com deciding that meant that the URL key for all of the data associated with our site should be changed to the URL of the test site. Suddenly all the stats and subscribers on our production site disappeared.

    I can find no documentation or explanation of exactly how Jetpack connects and communicates with wordpress.com accounts and so have no idea how to be able to test Jetpack before upgrading. Consequently, we are still running version 1.7 of Jetpack.

    How can I test Jetpack without losing all the data associated with our production site?

    http://wordpress.org/extend/plugins/jetpack/

  2. pjv
    Member
    Posted 1 year ago #

    I see that there is another thread about this same issue here which has been marked as resolved, though it does not appear to actually be resolved.

    Jetpack has huge, systemic effects on how a site works. People who are running busy commercial sites cannot afford to just throw a plugin like that into their production environment without first making sure that it won't disrupt the site's functionality.

    The inability to test Jetpack is a total showstopper.

  3. question: i'm admin of a busy, professional wp site. i can't afford to take the production site off-line so i have a test version of the site that runs in a virtual machine upon which i test every change before pushing into production.

    Sensible.

    that meant that the URL key for all of the data associated with our site should be changed to the URL of the test site.

    Yes, that part makes sense. I mean, how would WordPress.COM know you wanted to test with live data on their system?

    IANAAD (I Am Not An Automattic Developer) but if you want to test Jetpack's functionality then just associate a new site with a different data.

    If you want to do unit testing with live production data via WordPress.COM's data set then yes as you know, you're probably out of luck as there's not a way to tell WordPress.COM "Just kidding, don't update the data with this site".

  4. pjv
    Member
    Posted 1 year ago #

    Thanks,

    I would be very happy with either:

    1. some documentation that tells me how wordpress.COM associates jetpack site data with a particular site URL and how that interacts with the login credentials used to connect to wordpress.COM from the jetpack plugin so that I could have some idea what to expect when i do things like set up a test site by copying my production database to a virtual machine.

    2. some way to tell Jetpack and wordpress.COM "Just kidding", or maybe more to the point: this is a test site, please treat it as such and then do the "right thing" in terms of how it stores and associates data in the wordpress.COM database.

  5. Trevor Green
    Member
    Posted 1 year ago #

    I just ran into this issue.

    Even if you do test with a live site. Which I could do with a live staging but I test with local/staging/production. I still am required to make the blog public and index-able in order to connect it to wordpress.com.

    That is pretty weak.

    I can work around some of it but it's still annoying.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic