• Resolved Rev. Lloyd Newman

    (@hermcupadmin)


    Error Details
    =============
    An error of type E_PARSE was caused in line 118 of the file /home/hermitsc/public_html/wp-content/plugins/woocommerce-google-adwords-conversion-tracking-tag/includes/class-ask-for-rating.php. Error message: syntax error, unexpected ‘)’

    WordPress version 5.6
    Current theme: Di eCommerce (version 1.1.3)
    Current plugin: WooCommerce Google Ads Conversion Tracking (version 1.7.1)
    PHP version 7.2.34

    I’ve presently change the folder name of the plug-in to maintain site operations.

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author alekv

    (@alekv)

    @hermcupadmin

    Looking into it right now. Will give you an update soon.

    Plugin Author alekv

    (@alekv)

    @hermcupadmin

    I’m not exactly sure what the problem is, since the syntax looks correct.

    Could you send me an email to [email protected] so that we can exchange more information?

    Plugin Author alekv

    (@alekv)

    I just released a new version that should fix the problem.

    There was one comma in the wrong place. Not sure why this wasn’t picked up by our test on my dev machine.

    Let me know if it works for you.

    Thread Starter Rev. Lloyd Newman

    (@hermcupadmin)

    I downloaded the zip, FTP’d, activated, there was a brief error like -plug-in is not installed-(I think this was because the original folder was still edited with _BAD_foldername), I returned to plug-in page, the plug-in WAS active. I then re-activated a2-w3-total-cache. There were no errors.

    Original data for WooCommerce Google Ads Conversion Tracking was maintained. There were no additional errors.

    Status: Revised update appears to work without critical error. . I won’t be able to confirm full functionality without an order and we do not have a “test” site or “sandbox” to test the Google Ad tracking.

    Thank you very much for you expediency. I’m impressed!

    Plugin Author alekv

    (@alekv)

    @hermcupadmin

    Thanks for the feedback !

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