• This plugin is trash! It’s dangerous! It’s crashed my whole project. Neither is it possible to deactivate the debug mode inside of the plugin, nor to delete the whole bullshit via ftp.

    It has to be deleted from www.remarpro.com immediately!!!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator James Huff

    (@macmanx)

    There is absolutely nothing in the plugin that would prevent it from being deleted via FTP.

    What error did you see when you tried to delete it via FTP, and are you able to delete other files under /wp-content/ via FTP?

    As for the issue experienced with the plugin, would you please detail every step you took before the problem and the error you saw with the problem?

    Thanks!

    yes, you can delete it via FTP, BUT the plugins will remain deactivated, and, somehow, this plugin will still be active in the database, preventing any plugin from activation! I had the same problem. I tried so many things, but nothing worked, this plugin kept overwriting any plugin enabling, and the whole problem was visible to everyone, not just myself! Only after I added PHP 7.4 on my server I was able to stop this plugin. please check it, it is a real danger, and I also believe it should be removed from WordPress

    Plugin Author Marius L. J.

    (@clorith)

    Hiya,

    It’s not impossible to think that you may be experiencing synchronization issues if your host has files replicated between servers (for example), because if the file is deleted, it is not possible for the plugin to execute that code (since it wouldn’t be there to be read and ran).

    As for the disabled plugins affecting anyone, this may be another plugin, or your theme, doing something strange to the plugin loading, force-loading an entry (which unfortunately overwrites what the list of active plugins should be). We’ve not seen a lot of those cases after version 0.9, but there may be scenarios we’ve not accounted for, so I encourage you to open a support thread to look into what plugins or themes you have running and maybe we can find a fix for that together.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘DANGEROUS!’ is closed to new replies.