Fatal error (syntax error, error of type E_PARSE)

  • Resolved hanneslsm

    (@hanneslsm)


    7 months ago

    Hi, I’m getting an e-mail with the following content, indicating that the plugin causes a fatal error.
    I have upgraded the PHP Version of the server to 8.3 already and asked my host to restart the services, just to be sure. Not sure why the email is referring to PHP 7.3.33 

    Howdy! WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. In this case, WordPress caught an error with one of your plugins, Burst Statistics - Privacy-Friendly Analytics for WordPress. First, visit your website and check for any visible issues. Next, visit the page where the error was caught and check for any visible issues. Please contact your host for assistance with investigating this issue further. If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further. https://…
    To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires. When seeking help with this issue, you may be asked for some of the following information: WordPress version 6.8.3 Active theme: ProLooks-3 (version 1.2.2) Current plugin: Burst Statistics - Privacy-Friendly Analytics for WordPress (version 2.2.9.3) PHP version 7.3.33 Error Details ============An error of type E_PARSE was caused in line 19 of the file …httpdocs/de/wp-content/plugins/burst-statistics/includes/class-burst.php. Error message: syntax error, unexpected '?', expecting function (T_FUNCTION) or const (T_CONST)

    Some more info about the server from Site Health:

    Server
    The options shown below relate to your server setup. If changes are required, you may need your web host’s assistance.

    Server architecture	Linux 5.10.0-33-amd64 x86_64
    Web server	Apache
    PHP version	8.3.27 (Supports 64bit values)
    PHP SAPI	fpm-fcgi
    PHP max input variables	1000
    PHP time limit	30
    PHP memory limit	128M
    PHP memory limit (only for admin screens)	256M
    Max input time	60
    Upload max filesize	64M
    PHP post max size	64M
    cURL version	7.74.0 OpenSSL/1.1.1w
    Is SUHOSIN installed?	No
    Is the Imagick library available?	Yes
    Are pretty permalinks supported?	Yes
    .htaccess rules	Custom rules have been added to your .htaccess file.
    robots.txt	Your site is using the dynamic robots.txt file which is generated by WordPress.
    Current time	2025-10-31T16:48:35+00:00
    Current UTC time	Friday, 31-Oct-25 16:48:35 UTC
    Current Server time	2025-10-31T16:48:34+00:00

    Thank you,
    Hannes

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

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

    (@rogierlankhorst)

    7 months ago

    Hi @hanneslsm,

    This actually is a php compatibility issue, and can only occur with versions below php 7.4.

    Do you still have this error if you visit the website? If the site is on 8.3 it should be resolved now.

    Burst supports php 7.4 and higher, as of next version php 8.0 and up.

    Thread Starter hanneslsm

    (@hanneslsm)

    7 months ago

    Hi @rogierlankhorst Thanks for the quick reply.

    I don’t get the error when I visit the site and also do not see any errors when enabling the debug mode via wp_config.php. Only the e-mails notifies me daily about the issue.

    It’s weird because from my understanding (and according to site health and Plesk in my hoster) I have updated PHP to 8.3
    Is their anything you can point me to to check that could cause the error?

    Thanks
    Hannes

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    7 months ago

    Do you maybe have a separate /de subdomain with php 7.3, and the main domain on PHP 8?

    Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    7 months ago

    As this is a hosting issue, where the problem lies in the PHP version, there’s nothing much we can do on our side. But if you have more info we can assist with let me know!

    Thread Starter hanneslsm

    (@hanneslsm)

    6 months, 3 weeks ago

    Solved. The issue was that the PHP Version was not updated on the wildcard Subdomain.

    Thanks for the support! 🙂

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

The topic ‘Fatal error (syntax error, error of type E_PARSE)’ is closed to new replies.