Fatal error

  • Plugin could not be activated because it triggered a fatal error. As I see no reply to Rick F’s report of the same problem a year ago, I’m uninstalling. Too bad.

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

    (@edward_plainview)

    I do not see a support forum question from you.

    In the forum, did you visit the first, stickied, bright yellow link with the exact same error as you desribe?

    Thread Starter HollyJahangiri

    (@hollyjahangiri)

    Nope.

    I’ll go look. I looked, once – back when I first installed this plug-in. I saw no reason to replace the WP Activity Monitor with it at the time, so seeing nothing, I didn’t pursue it. When I saw the same error – and the comment from a year ago – I didn’t bother with the forum this time.

    Plugin Author edward_plainview

    (@edward_plainview)

    Did you figure out the problem?

    Thread Starter HollyJahangiri

    (@hollyjahangiri)

    It has supposedly been at 5.4 since April 2014.

    Thread Starter HollyJahangiri

    (@hollyjahangiri)

    Here’s the error:

    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)

    That is definitely a v5.3 error.

    Thread Starter HollyJahangiri

    (@hollyjahangiri)

    Well, that’s really weird since the server’s been running 5.4 since 2014. (I’m on Hostgator, if it matters – and I’d requested the upgrade then. I have another plug-in that required it and it runs fine.) Any other ideas?

    Plugin Author edward_plainview

    (@edward_plainview)

    Nope. But if you search around you’ll find that error being associated with php <= 5.3 not being able to parse php 5.4 [] style arrays.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Fatal error’ is closed to new replies.