Title: New update errors
Last modified: August 3, 2017

---

# New update errors

 *  [kubeq130](https://wordpress.org/support/users/kubeq130/)
 * (@kubeq130)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/)
 * Hi,
 * After a new update I get error incontrol panel:
 *     ```
       ...nt/plugins//wp-content/plugins/wp-hide-post/wp-hide-post.php): failed to open stream: No such file or directory in /wp-includes/functions.php on line 4785
   
       Warning: fread() expects parameter 1 to be resource, boolean given in /wp-includes/functions.php on line 4788
   
       Warning: fclose() expects parameter 1 to be resource, boolean given in /wp-includes/functions.php on line 4791
       ```
   
 * I changed my hosting to php 7 and it didn’t help. I cant just turn off this plugin
   because I have a lot of posts hidden. Please help if you can.

Viewing 15 replies - 1 through 15 (of 21 total)

1 [2](https://wordpress.org/support/topic/new-update-errors-2/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/new-update-errors-2/page/2/?output_format=md)

 *  Plugin Author [scriptburn](https://wordpress.org/support/users/rmahfoud/)
 * (@rmahfoud)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9366598)
 * it clearly says that you have missing wp-hide-post.php , it seems somehow updates
   was unable to copy all of the files
 * I would suggest you to download the plugin and upload manually in plugins folder
 *  Thread Starter [kubeq130](https://wordpress.org/support/users/kubeq130/)
 * (@kubeq130)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9366736)
 * I arleady tried to unistall and download wp hide post again – still error
    I 
   uploaded manually in plugins folder and it didn’t work too.
 *  [matthewblev](https://wordpress.org/support/users/matthewblev/)
 * (@matthewblev)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9366866)
 * It broke my website, was getting 500 internal service error. Having tech support
   remove the plugin to fix the site :/
 *  [technomad42](https://wordpress.org/support/users/technomad42/)
 * (@technomad42)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367027)
 * +1 Today’s update completely white-screened my entire multisite installation.
   removing the plugin brought it back. So what didn’t get tested?
 *  Plugin Author [scriptburn](https://wordpress.org/support/users/rmahfoud/)
 * (@rmahfoud)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367182)
 * what php version you guys are using ?
    Plugin has been tested for php version
   >=5.5
 *  [matthewblev](https://wordpress.org/support/users/matthewblev/)
 * (@matthewblev)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367204)
 * Checked, my site is still on 5.3. I see an option to update to 7.1, any reason
   not to do that?
 *  [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367556)
 * The cause of the problem is probably that when you committed this plugin version
   to SVN you made a made a mistake “tagging” this plugin version. Total zipped 
   size of plugin is: 22.9MB. If you look at your plugin folder structure you will
   see that your older plugin versions are nested and included in this plugin version
   > wp-hide-post > wp-hide-post > wp-hide-post.
    -  This reply was modified 8 years, 10 months ago by [AITpro](https://wordpress.org/support/users/aitpro/).
    -  This reply was modified 8 years, 10 months ago by [AITpro](https://wordpress.org/support/users/aitpro/).
 *  [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367592)
 * We did this same mistake once by tagging from the root plugin folder (C: drive)
   instead of the trunk folder (C:\plugin-folder\trunk). I can’t remember exactly
   how we fixed that SVN problem. I believe we deleted the tagged plugin version
   folder in C:\plugin-folder\tags\[deleted the bad plugin version folder], did 
   an SVN Update, then redid the tag again correctly from the trunk folder and did
   another Commit.
    -  This reply was modified 8 years, 10 months ago by [AITpro](https://wordpress.org/support/users/aitpro/).
 *  [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367606)
 * Actually you would need to do a Commit before doing the tag again.
 * Delete the tagged plugin version folder in C:\plugin-folder\tags\[deleted the
   bad plugin version folder], do an SVN Update, do a Commit from the root plugin
   folder, redo the tag again correctly from the trunk folder and then do another
   SVN Update.
    -  This reply was modified 8 years, 10 months ago by [AITpro](https://wordpress.org/support/users/aitpro/).
    -  This reply was modified 8 years, 10 months ago by [AITpro](https://wordpress.org/support/users/aitpro/).
 *  [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367648)
 * You also need to delete the wp-hide-post.2.0.4 tagged version. The same problem
   is going on with that tagged version too. Version 2.0.2 is ok.
 *  Plugin Author [scriptburn](https://wordpress.org/support/users/rmahfoud/)
 * (@rmahfoud)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367727)
 * [@aitpro](https://wordpress.org/support/users/aitpro/) Thankx for pointing that
   out, just cleaned up tags and released new version with few more fix
 *  [doublesharp](https://wordpress.org/support/users/doublesharp/)
 * (@doublesharp)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367762)
 * It still doesn’t seem to be working… I just updated to the latest and am now 
   getting out of memory errors. Removing the plugin fixes the issue. This was installed
   fresh from the WP repository.
 *     ```
       Fatal error: Allowed memory size of 205520896 bytes exhausted (tried to allocate 262144 bytes) in /www/html/wp-includes/l10n.php on line 202
   
       Fatal error: Allowed memory size of 205520896 bytes exhausted (tried to allocate 262144 bytes) in /www/html/wp-includes/load.php on line 677
       ```
   
 * The line number bounces around, but the errors do resolve when I remove `wp-hide-
   post`, so it does seem to be triggered by the plugin. Maybe an infinite loop?
    -  This reply was modified 8 years, 10 months ago by [doublesharp](https://wordpress.org/support/users/doublesharp/).
 *  [Kulverstukas](https://wordpress.org/support/users/kulverstukas/)
 * (@kulverstukas)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367780)
 * Indeed. With a previous version it white-screened my site. With current (2.0.6)
   version the plugin doesn’t even activate – crashed when I press the Activate 
   button.
 *  Plugin Author [scriptburn](https://wordpress.org/support/users/rmahfoud/)
 * (@rmahfoud)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/#post-9367882)
 * hmm weird i have max memory_limit for php process 128 MB and i dont get out of
   memory issue while yours is more then me (200) and you are getting the error
 *  [Miguel](https://wordpress.org/support/users/millote/)
 * (@millote)
 * [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/page/2/#post-9367985)
 * The plugin causes a fatal error. It causes the whole system to fail. I upgrade
   2.06 version and fail. Thank you

Viewing 15 replies - 1 through 15 (of 21 total)

1 [2](https://wordpress.org/support/topic/new-update-errors-2/page/2/?output_format=md)
[→](https://wordpress.org/support/topic/new-update-errors-2/page/2/?output_format=md)

The topic ‘New update errors’ 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/)

## Tags

 * [php-7](https://wordpress.org/support/topic-tag/php-7/)
 * [update error](https://wordpress.org/support/topic-tag/update-error/)

 * 21 replies
 * 9 participants
 * Last reply from: [Jan Dembowski](https://wordpress.org/support/users/jdembowski/)
 * Last activity: [8 years, 10 months ago](https://wordpress.org/support/topic/new-update-errors-2/page/2/#post-9376657)
 * Status: not resolved