Automatic Update Created New Plugin Folder
-
I need to understand exactly how auto updates work for plugins. I have all my plugins set to auto update, but a recent update of one plugin caused a fatal error on the site, so I FTP’d in and appended the plugin folder name with -p to deactivate the plugin so I could log into the backend. I forgot to toggle off auto update, so that was still on. I put in a ticket with the plugin dev and overnight a second (new) folder of the plugin, only a newer version that was released over that same night, coincidentally, was created on the server. I looked at the backend and there were two instances of the plugin on the plugins page. Both deactivated, both set to auto update, one was the next to last version and one was the latest version released over night.
My question is: Is this normative behavior that a deactivated, rename plugin set to auto update would install a whole other plugin folder with the latest version in it?
- You must be logged in to reply to this topic.