Plugin could not be activated because it triggered a fatal error.

  • Thank you for this good-looking plugin, unfortunately I can’t get it to work.
    When I try to activate it, I get this error message:
    Parse error: syntax error, unexpected T_STRING in /web/WebSites/d/g/r/e/mydomain.de/htdocs/wp-content/plugins/filester/ninja-file-manager.php on line 15
    I don’t post the URL, because the site is still using WP 3.6.1. ??
    It belongs to an NGO, which has lost the account information.
    While they try to recover, I want to backup the files in order to create a backup site and try to update WP.
    Can you resolve this error, please?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Ninja Team

    (@ninjateam)

    Hello @spade

    Thanks for using Filester.

    This issue occurred because you are using WP very old version, we support WP 4x and 5x. Can you update your WP core? It’s recommended for security.

    Best regards,
    Tommy

    Thread Starter Frank Spade

    (@spade)

    Thanks Tommy,
    you better update your plugin information then, because it says ?WordPress Version:
    3.0 or higher?. Otherwise I would not have tried it and wasted my time. :-{

    Plugin Author Ninja Team

    (@ninjateam)

    Oops! Sorry about that.

    I will try to discuss with our development team if can make it work on WordPress 3x in the next update.

    Tommy

    Thread Starter Frank Spade

    (@spade)

    Dear Tommy,
    sounds great thanks.
    I’m looking forward to it. How will I know when it’s ready?
    Keep up the good work.
    Cheers,
    Frank

    Plugin Support Bruce

    (@ninjateamwp)

    Hi @spade ,

    This was already conveyed to our developer team and they are researching on it now to be sure it would not cause any security vulnerabilities, so for now we don’t have an ETA for when we might have it or if we might have it.

    Thank you.

    Kind regards,
    -Bruce-

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error.’ is closed to new replies.