Plugin could not be activated because it triggered a fatal error

  • Resolved Suggymoto

    (@suggymoto)


    8 years, 3 months ago

    Hi.

    I’m running PHP 5.4 but am still getting error message:

    Plugin could not be activated because it triggered a fatal error
    Parse error: syntax error, unexpected ‘[‘ in /home/cluster-sites/4/d/digitaldogs.co.uk/public_html/digi/wp-content/plugins/plainview-activity-monitor/src/old_sdk/collection.php on line 29

    Any thoughts?

    Thanks

    https://wordpress.org/plugins/plainview-activity-monitor/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author edward_plainview

    (@edward_plainview)

    8 years, 3 months ago

    That’s definitely a php 5.3 error.

    I’d check the PHP version again. Sometimes you have to do something in the htaccess to enable 5.4 for all subdirectories.

    HollyJahangiri

    (@hollyjahangiri)

    8 years, 2 months ago

    Checking with my web host, now. I would assume they’re running 5.4, but never assume anything. There are still people running Windows XP.

    HollyJahangiri

    (@hollyjahangiri)

    8 years ago

    The site’s running 5.4. Any updates? Still get the following error on attempting to activate. :

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

    Parse error: syntax error, unexpected ‘[‘ in /home1/hollyj/public_html/2013/wp-content/plugins/plainview-activity-monitor/src/old_sdk/collection.php on line 29

    Plugin Author edward_plainview

    (@edward_plainview)

    7 years, 12 months ago

    I am dead sure that it’s a php 5.3 error.

    http://docs.php.net/manual/en/language.types.array.php

    “As of PHP 5.4 you can also use the short array syntax, which replaces array() with [].”

    Thread Starter Suggymoto

    (@suggymoto)

    7 years, 12 months ago

    Turned out my .htaccess file was limiting the version of php that my site could support. Changed it and resolved my issue.

    sitesourced

    (@sitesourced)

    7 years, 6 months ago

    This turned out to be a php error for me. It was corrected by switching from php version 7 to a 5 series version.

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

Tags