Version 4.3.2 throws Parse error

  • Resolved allan1978

    (@allan1978)


    2 years, 4 months ago

    Hi,

    When updating to the latest version of WP Maps i’m getting the following error:

    Parse error: syntax error, unexpected ‘)’ in /wp-content/plugins/wp-google-map-plugin/wp-google-map-plugin.php on line 311

    Looking at line 311, it shows an array with a trailing comma, I know that is correct syntax but can’t see why else it’d be throwing an error.

    Site is using PHP 7.2 and after some Googling it turns out that the trailing comma was only allowed from version 7.3

    https://laravel-news.com/php-trailing-commas-functions

    Thanks,
    Allan

    • This topic was modified 2 years, 4 months ago by allan1978.
    • This topic was modified 2 years, 4 months ago by allan1978.
Viewing 9 replies - 1 through 9 (of 9 total)

  • Hello Allan,

    We’re checking the code on PHP 7.2 and getting you back.

    meanwhile, can you please try to remove comma and check it?

    Thanks

    Hello,

    Please let us know if you were able to fix the issue.

    You can remove the comma character after below statement :

    array( $this,’wpgmp_processor’ ){remove comma character from here}

    Above statement is on line number 310.

    Please let us know how it turned out for you. In case you are still viewing an issue we are here to check and fix the issue quickly for you.

    Thank You

    Thread Starter allan1978

    (@allan1978)

    Hi,

    I removed the comma from the sites that were affected and they now work as expected now.

    Cheers,
    Allan

    Hello Allan,

    Thanks for your input! I’m waiting for some more feedback as this is a new release and will update the plugin. Up to now, around 11000 sites updated but we got only one error notification.

    So it seems that most of the users are using PHP 7.3+ version.

    Would you like to mark this ticket as resolved?

    Thanks

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Would you like to mark this ticket as resolved?

    @flippercode This is important. Stop calling support topics “tickets”.

    Wrongly calling support topics “tickets” sets a very wrong expectation of the opensource collaborators who seek support here. Tickets imply “customers” and you have no customers on this site. You never have and treating opensource collaborators as “customers” is wrong.

    Please pay attention to that, it is an important detail.

    @jdembowski – I got it! and will take care in the future! I have worked a lot on technical support on WordPress Plugins so I have this habit.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    Thanks! I appreciate that reply!

    Thread Starter allan1978

    (@allan1978)

    @flippercode I’ve a few clients sites with legacy hosting that can’t be upgraded past 7.2

    and yes, you can mark this support topic as closed ??

    Surely, I’ll update the plugin! Thanks!

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Version 4.3.2 throws Parse error’ is closed to new replies.