Update to 1.3.2 failed

  • Resolved popmillipede

    (@popmillipede)


    7 years, 9 months ago

    Just tried to update from Media Deduper 1.3.1 to 1.3.2. Now my site is showing the following error on every access.

    Parse error: syntax error, unexpected T_STATIC, expecting ‘)’ in /home/content/41/7202541/html/stage-new/wp-content/plugins/media-deduper/media-deduper.php on line 58

    Fortunately I did this on a staging site, not in production. I will delete the extension to get the site back but I would like to use this plug-in in the future. Am I the only one seeing this or is 1.3.2 completely broken?

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

    (@kenjigarland)

    Hi there! It sounds like the version of PHP your staging site is running on doesn’t support late static bindings, which were introduced back in 2009 with PHP version 5.3. Can you confirm what version of PHP you’re using? If it’s less than 5.3, then that’s what’s causing this problem.

    In general, I’d really recommend upgrading to at least PHP 5.6, or PHP 7 if your host supports it, for security and performance reasons (as well as to get Media Deduper running again). The PHP dev team no longer releases security updates for version 5.5 or lower, so running an older version can leave your site vulnerable.

    Thread Starter popmillipede

    (@popmillipede)

    Thanks for the response. Yes, the PHP version is my problem. I’m using 5.2.17. Not sure why we have such an old version given we just did a major site redesign in 2016. I will look into this with our web devs and start a project to upgrade to a newer version of PHP.

    Plugin Author kenjigarland

    (@kenjigarland)

    Awesome. Thanks for reporting this problem, by the way. In the next release we’ll make sure to clarify that PHP 5.3+ is required, but we’ll also make sure things don’t crash if you’re running 5.2.

    I’m marking this thread as resolved for now, but if you run into any issues after upgrading, please do follow up.

    Cheers!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Update to 1.3.2 failed’ is closed to new replies.