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?
- The topic ‘How to test?’ is closed to new replies.