torking

Agreed. We manually changed the permissions on our plug in folders to 775 as part of a test to try and change the permissions on your plug in folder (since 755 doesn’t allow write access for group permissions, which we thought might be the issue). The fact that the only folder in our entire WP directory which has permission denied errors and where can’t change the permissions is your folder is what is causing the alarm bells. And there are definitely several other support articles about problems deleting this plug in. I know you say there is no code in your plug in about deletions, but this simply shouldn’t be happening as we should be able to manage permissions on all our folders. We can’t even understand how the permission on your plug in folder got set to 755 in the first instance.

As I noted above, we will have one of our devs look at this folder in detail later this week and I will revert with what we find.

Hi.

Yes, folder permissions for the folder for your plug-in are different. They are 755, whereas all other folders in the plug-in directory are 775. As mentioned in the original post, we cannot change those permissions on the folder for your plug in – keep getting a permission denied error.

Attempting to delete any single file in your plug-in folder leads to the same permission denied error. Somehow, your plug in (and only that plug in) has changed its permissions, which makes me very nervous.

There is nothing unusual in our error logs either.

I will have one of my devs have a closer look at this folder via SSH later in the week. There is definitely something weird going on here though (and will also investigate the WP options table, although that shouldn’t be required to just delete a plug in).