When you say “removed my plugin folder,” do you mean that the /wp-content/plugins/ directory no longer exists on your server? I assume this disrupted all of the plugins on your website if so.
Did you have any other updates going on? Theme? WP Core?
Thread Starter
pcomt
(@pcomt)
Sorry, I stated it incorrectly. The folder was still there, but it was empty. Sorry about the confusion. …plugtins/contact-form-7-dynamic-text-extension folder is the one I am referring to.
All my other plug-ins are working.
Ah, I find that sometimes happens when the site times out during the update process (I have that happen all the time on my clients’ azure environments regardless of how much memory I allot).
If you delete the empty folder, you can install the plugin fresh from the WordPress backend, but it’s possible it times out again if you have had this issue happen before.
You can also install it via upload by downloading the zip file and uploading to the backend or manually via FTP by unzipping the downloaded zip file and moving the files to the /plugins/ folder.
Thread Starter
pcomt
(@pcomt)
I assume I am not the only one that will experience this so you may want to work out the update so it does not fail in the future. Work arounds are fine for some of us, but not all of us will be comfortable doing it manually.
I will probably make the update in the future. I do not really need the new features right now. I will just disable this plug-in auto update for the time being.
Thanks for the feedback.
Please mark this as complete
Unfortunately this is not something that my plugin is responsible for nor is something I could fix to ensure it never happens. Whether or not an update (manual or automatic) fails or succeeds is entirely dependent on your WordPress environment. Factors may include file permissions, your web host, memory limits, available disk space, internet connection, etc.
Plugin developers are only responsible for the code packaged in their plugins, not how well they transfer. That is out of our scope.
For example, I often get these errors with Yoast SEO and Wordfence for a specific client who insists on a certain hosting environment whereas other client sites that use a different host do not have this issue, so I can safely enable auto-update for those.
At any rate, thank you for reaching out to me in these forums to let me know you were having this issue. Cheers!
