Title: Accidental deploy?
Last modified: September 1, 2016

---

# Accidental deploy?

 *  Resolved [Jared Atchison](https://wordpress.org/support/users/jaredatch/)
 * (@jaredatch)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/accidental-deploy/)
 * I have no idea what’s going on though – but it looks like a new version was accidentally
   sent out?
 * It broke all archives on our site. Additionally, when the plugin is activated
   we now get some test custom post types added to our menu.
 * Author needs to do a roll back release immediately because all the sites set 
   to auto-update plugins are breaking.
 * [https://wordpress.org/plugins/wp-hide-post/](https://wordpress.org/plugins/wp-hide-post/)

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

 *  Plugin Author [scriptburn](https://wordpress.org/support/users/rmahfoud/)
 * (@rmahfoud)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/accidental-deploy/#post-7660082)
 * Plugin has been restored to previous version.
    If your are getting some error
   you can manually remove the plugin with ftp by going to wp-content/plugins folder
   and removing wp-hide-post folder.
 * After that you go to install plugin section and search for hide post plugin and
   install the stable version again
 *  [Robert_ITman](https://wordpress.org/support/users/robert_itman/)
 * (@robert_itman)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/accidental-deploy/#post-7660098)
 * Noticed that WP Hide Post stopped working today on my websites – and what is 
   worse is that it actually hid all my custom post types and wooCommerce products…
   yikes! If you get the message “No products were found matching your selection”–
   this might be your solution
 * I noticed I had a more recent version of WP Hide Post (2.0.3) than what is available
   on your WP plugins page (Version: 1.2.2) – how did that happen? (I’m sure it 
   happened because I have auto updating plugin activated). Anyways I uninstalled
   the newer version and installed what you have available on your WP plugins page(
   Version: 1.2.2) and it solved my issue.
 *  Thread Starter [Jared Atchison](https://wordpress.org/support/users/jaredatch/)
 * (@jaredatch)
 * [9 years, 10 months ago](https://wordpress.org/support/topic/accidental-deploy/#post-7660121)
 * That was the critical error that was made here…
 * There are 50k active installs, so who knows how many of those sites were set 
   to auto update plugins or happened to update during the short window that the“
   bad release” was available – I’m sure it was in the hundreds.
 * What should have ben done is followed up with a 2.1.0 release (even if it was
   the same as 1.2.2). That would have effectively automatically fixed everything
   through updating.
 * Instead, it was rolled back to 1.2.2. This means that for the potentially hundreds
   of users who have the a broken site, the only way they can fix it is to delete
   the plugin completely from their server, then manually reinstall it … and that’s
   assuming they even figure out that the plugin is the source of their site breaking.

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

The topic ‘Accidental deploy?’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wp-hide-post.svg)
 * [WP Hide Post](https://wordpress.org/plugins/wp-hide-post/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-hide-post/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-hide-post/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-hide-post/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-hide-post/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-hide-post/reviews/)

 * 3 replies
 * 3 participants
 * Last reply from: [Jared Atchison](https://wordpress.org/support/users/jaredatch/)
 * Last activity: [9 years, 9 months ago](https://wordpress.org/support/topic/accidental-deploy/#post-7660121)
 * Status: resolved