• Resolved ebiz98

    (@ebiz98)


    Not sure when – but I am getting the following “There has been a critical error on this website.”
    and had to rename the RSVPMaker plugin directory to get the site back —

    Any ideas?
    in the log it shows:

    PHP 8.0.30

    Using: Stable tag: 11.2.7

    [25-Aug-2024 03:52:56 UTC] PHP Parse error: Unclosed ‘{‘ on line 4206 in /home/… /wp-content/plugins/rsvpmaker/rsvpmaker-util.php on line 4706

    • This topic was modified 3 months ago by ebiz98.
    • This topic was modified 3 months ago by ebiz98.
Viewing 12 replies - 1 through 12 (of 12 total)
  • John

    (@webwiz1)

    I got exactly the same problem.

    WordPress v6.2.6
    RSVPMaker v11.2.7
    PHP v7.4.33

    I disabled the plugin for now so the website loads but it’s broken for sure.

    Definitely a problem with the latest code. The script rsvpmaker-util.php has syntax errors and is well and truly broken.

    I reverted to my last good copy of the plugin. The current release download not safe.

    Thread Starter ebiz98

    (@ebiz98)

    I am very surprised that the developer has not responded to this– is this Plugin still being supported?

    No new version is out from a critical error…

    Plugin Author davidfcarr

    (@davidfcarr)

    Sorry for the slow response. Please try version 11.3 and let me know if that resolves the issue.

    Thread Starter ebiz98

    (@ebiz98)

    Sorry – but after updating it did not resolved the issue — The site come back with a critical error.

    Thread Starter ebiz98

    (@ebiz98)

    So I just started from a clean version and I am getting the same critical error after it updates:
    I am really challenged here… not sure what to do !!

    Had to rename the plugin folder to restore functionality –

    Parse error: Unclosed ‘{‘ on line 4206 in … /wp-content/plugins/rsvpmaker/rsvpmaker-util.php on line 4715

    There has been a critical error on this website. Please check your site admin email inbox for instructions.

    When I install previous version,had to go back to version 11.2.5 — I am getting a bunch of warnings so something much have changed in the DB perhaps?: I just do not know..

    • This reply was modified 2 months ago by ebiz98.
    • This reply was modified 2 months ago by ebiz98.
    chrisj97229

    (@chrisj97229)

    In my case, the problem was on line 4229 of rsvpmaker_util.php

    I changed the “<?” on that line to “<?php” and it started working again. YMMV

    Plugin Author davidfcarr

    (@davidfcarr)

    Anyone still struggling with this: Please try installing RSVPMaker 11.4.2 and let me know if that resolves the issue.

    Turns out PHP 8 removed default support for a short tag syntax that I don’t normally use but which occurs in one spot in the rsvpmaker-util.php file.

    The reason it took me so long to find the bug: Both my web host and my local dev environment had a php.ini configuration switch turned on that allows short_tags to work in PHP 8.

    • This reply was modified 1 month, 3 weeks ago by davidfcarr.

    Also getting critical errors after updating. We have always had short_open_tag enabled.

    Enabling debugging and logging shows nothing unfortunately.

    Plugin Author davidfcarr

    (@davidfcarr)

    Rob,

    The short open tag thing shouldn’t be an issue at this point, if you have the current release installed.

    You’re saying you get critical errors when updating the plugin? No other changes? What PHP version?

    Re nothing being logged, you might try temporarily enabling DEBUG_LOG_DISPLAY in your wp-config.php. I’ve occasionally seen errors that will be displayed on screen but not written to the log for whatever reason.

    I’m not seeing these errors on my test and production servers, so I do need a clue of where to look if the plugin is behaving differently on your website. Could be a conflict with another plugin or something different about the hosting setup.

    I’ve just been testing on a local copy, PHP versions 5.6, 7.0, 7.2, 8.0, 8.2.

    Debug logging and display is turned on and php error reporting set to max, but I just get the wordpress critical error notice on the frontend and admin and no specific error and no debug file.

    There are a number of problems in the utils file, like undefined variables, but nothing I can see that would cause a fatal error.

    I’ll update you if I find the issue.

    Ok, it’s down to the method of overriding the output.

    We have an rsvpmaker-custom.php file in the wp-content directory. It had error_reporting(0); at the top.

    In our case, the issue was that the class event_content is redefined.

    In the previous version, rsvpmaker-pluggable.php checks to see if functions are already defined. Those checks have been removed, so redefining them in the custom file breaks a site.

    WordPress filters would be a better method of modifying the output.

Viewing 12 replies - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.