Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author gioni

    (@gioni)

    Hi! I recommend adding the directory of the plugin you’re working on to the Directories to exclude setting field. Obviously, that code is not malicious, but there is no way to verify it.

    Thread Starter Hector Cabrera

    (@hcabrera)

    Got it, thanks for the input Gioni. What worries me though if that if I decide on releasing the plugin to the public someday, people might come saying “hey, there’s malicious code in it!” hahaha I guess I’ll just have to point them to the source code.

    You still should have a look at the JS error, though. While nothing major, it might keep some less inexperienced users from understanding why WP Cerber is marking said code as “potentially malicious”.

    If there’s anything I could help with don’t hesitate to ask.

    Plugin Author gioni

    (@gioni)

    There will be no issues unless someone decides to install the plugin via FTP. If a plugin is installed via the WP dashboard, Cerber knows how to handle this. When a plugin is installed via FTP it has to be uploaded on the scanner results page also.

    I’ll look into the JS error, thanks for the screenshot.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘JS error: Cannot read property ‘details’ of undefined at cerber_xdata_info’ is closed to new replies.