error after update

  • Resolved hidenori

    (@hidenori)


    8 years, 1 month ago

    I updated this plugin and resulted in the following message:

    Parse error: syntax error, unexpected ‘)’, expecting T_PAAMAYIM_NEKUDOTAYIM in (my site directory) on line 1764

    Please advise me.
    Thank you.

    hidenori

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

  • (my site directory) points to the common.php?

    Line 1764 in common.php is bellow

    if ( ! defined( 'DOING_AJAX' ) || empty( DOING_AJAX ) ) {

    This syntax is not supported in php version 5.4 and earlier.
    For now, I think that the error does not appear if you change the version of php later 5.5.

    I’m getting the same error. It actually shut my site down until I uninstalled the plugin.

    • This reply was modified 8 years, 1 month ago by jmorti.
    Thread Starter hidenori

    (@hidenori)

    I updated PHP from 5.2 to 5.6 and the error message went out.
    Thank you for your quick and correct advice.

    hidenori

    Ditto here. I took two sites down. The error is not consistent as it did install well on two other sites.

    OC2PS

    (@sooskriszta)

    Parse error: syntax error, unexpected ‘)’, expecting T_PAAMAYIM_NEKUDOTAYIM in (my site directory) on line 1764

    Same here.

    same here. using PHP Version : 5.4.45 / 64Bit OS
    had to remove the plugin as I ca not change php versions at the moment

    • This reply was modified 8 years, 1 month ago by udijw.
    Plugin Author nosilver4u

    (@nosilver4u)

    just released fix in 3.0.1

    Still getting this error in 3.0.1

    Plugin could not be activated because it triggered a fatal error.
    Parse error: syntax error, unexpected ‘)’, expecting :: (T_PAAMAYIM_NEKUDOTAYIM) in wp-content/plugins/ewww-image-optimizer/common.php on line 1765

    • This reply was modified 8 years, 1 month ago by udijw.
    Plugin Author nosilver4u

    (@nosilver4u)

    What the heck! The code reverted itself. Going to go see what in the world just happened, and push it as 3.0.2…

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