Support » Plugin: WooCommerce » Plugin deleted during update

  • Resolved Chad Warner


    I’ve had repeated issues updating WooCommerce on 3 sites for the last few weeks (WooCommerce 4.4.1, 4.5.1, and maybe others). Updating via WP Admin fails, and the plugin gets deleted. The Updates screen shows:

    Warning: fopen(/www/wp-content/plugins/woocommerce/woocommerce.php): failed to open stream: No such file or directory in /wordpress/wp-includes/functions.php on line 6023 Warning: fread() expects parameter 1 to be resource, boolean given in /wordpress/wp-includes/functions.php on line 6026 Warning: fclose() expects parameter 1 to be resource, boolean given in /wordpress/wp-includes/functions.php on line 6029

    The plugin screen shows:

    The plugin woocommerce/woocommerce.php has been deactivated due to an error: Plugin file does not exist.

    The plugin can’t be reinstalled via WP Admin. I can delete via SFTP then upload the latest version via SFTP. However, when I later try to update to a newer version (e.g., 4.4.1 to 4.5.1) in WP Admin, the problem recurs.

    • This topic was modified 4 months, 1 week ago by Chad Warner.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Also having this issue.

    Plugin Author Siew


    Hi there,

    I just tested updating on my site from 4.5 to 4.5.1 without issues.

    Can you try to disable all plugins before updating WooCommerce?

    I hope this points you in the right direction.

    Thanks for the suggestion. I tested 3 sites (using staging sites), updating WooCommerce with and without deactivating all plugins first. For 2 sites with WooCommerce 4.4.1, the update to 4.5.1 failed, with and without deactivating plugins first. In all cases, WooCommerce was deleted and I got the errors described in my original post.

    For 1 site with WooCommerce 4.3.1, the update to 4.5.1 worked properly, with and without deactivating plugins first.

    So disabling plugins didn’t make a difference. What else can I try?

    I asked Flywheel (web host), and they said,

    I was able to link this issue to a bug that we have outstanding at this time. There is not a workaround for this at this time but moving forward, I would recommend manually updating the plugin via SFTP until this is fixed. You can certainly jump into chat and have them look up ticket [removed] to get the status on the bug but it might be at least a couple of weeks before we have an update on this.

    Plugin Author Siew


    Hi there,

    Since this is due to a bug with the host, and we haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.