• Resolved baalam

    (@baalam)


    I get this on my dashboard. Had to deactivate the plug in.

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

    Parse error: syntax error, unexpected ‘[‘ in /var/www/website/wp-content/plugins/timeline-express/lib/classes/usage-tracking/wp-plugin-usage-tracker.php on line 87

    Will mark as non-functional util fixed.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Code Parrots

    (@codeparrots)

    Hi there,

    Thank you for your comments. There are oher open threads that have raised the same issue, which we have addressed in those threads:
    https://wordpress.org/support/topic/fatal-error-2501/

    In short, we no longer support legacy versions of PHP. PHP 5.6 is at its end of life, and will only receive security updates moving forward. Any versions prior to that have been deprecated and running those versions exposes you to some security vulnerabilities.

    With that being said, you should be running at least PHP 5.6. If you are running earlier versions, you are going to have some issues. We highly recommend that you upgrade to a later version.

    Even on the requirements for the WordPress.org page they list PHP 7.0 as the recommended version, and go on to say you can use legacy versions but will be exposed to security vulnerabilities.

    We can work on a patch to fix this issue moving forward, but we still recommend you upgrade to PHP 5.6 or later to work around the notice and protect your site from attacks.

    Thanks!

    Plugin Contributor Code Parrots

    (@codeparrots)

    Hi @baalam,

    While it’s not recommended that you be using any versions of PHP older than 5.6 due to security issues, we have just pushed out a version 1.4.1 patch that now works around this issue and does not include the tracking file when a user is using a deprecated version of PHP.

    Please feel free to update, and let us know if you are still having issues.

    Thanks again!

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Latest update triggers error’ is closed to new replies.