• Hi,

    first of all, we are very happy with the plugin (free version).

    There are some issues with PHP 8.0, though. At changing from PHP 7.4 to 8.0 the following warnings get displayed in the frontend:
    1. Warning: Trying to access array offset on value of type null in?…/wp-content/plugins/restaurant-reservations/includes/MailChimp.class.php?on line?75
    2. Warning: Trying to access array offset on value of type null in?…/wp-content/plugins/restaurant-reservations/includes/MailChimp.class.php?on line?76

    In the backend, there are 3 more messages concerning MailChimp:
    Warning: Cannot modify header information – headers already sent by (output started at …/wp-content/plugins/restaurant-reservations/includes/MailChimp.class.php:75) in?…/wp-includes/functions.php?on line?6362
    Warning: Cannot modify header information – headers already sent by (output started at …/wp-content/plugins/restaurant-reservations/includes/MailChimp.class.php:75) in?…/wp-admin/includes/misc.php?on line?1310
    Warning: Cannot modify header information – headers already sent by (output started at …/plugins/restaurant-reservations/includes/MailChimp.class.php:75) in?…/wp-admin/admin-header.php?on line?9

    This said, we do not plan to integrate MailChimp (which is a Premium feature anyway) into our table reservation system in the near future. So, that’s just to let you know.

    However, if you’d have a quick fix for us in order to be able to start using PHP 8.0 that would be greatly appreciated.

    Thanks in advance!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support jaysupport

    (@jaysupport)

    Hi adalov,

    Thanks for letting me know about this. Just to be certain, do these warnings only show if you have debug enabled? Also, do they only show when you are on a specific screen (e.g. the settings page), or when you do a specific action in the plugin (admin or front end)?

    Thread Starter adalov

    (@adalov)

    Hi jaysupport,

    debug is off. The warnings are displayed as described in the frontend (not only the admin screen) upon switching from PHP 7.4 to 8.0. independently of screen or any other specific action concerning the plugin.

    Everything is fine with PHP 7.4.19, but we cannot switch to PHP 8.0 because of this, so a fix would be great.

    By the way, the warnings are also reported by https://plugintests.com/plugins/wporg/restaurant-reservations/latest.
    The problem seems to have occurred first with version 2.1.20 of the plugin: https://plugintests.com/plugins/wporg/restaurant-reservations/2.1.20.

    Thanks for looking into this and letting us know when a fix will be available.

    Plugin Support jaysupport

    (@jaysupport)

    Where did you describe exactly where they were displaying, besides just mentioning front end and back end? I was hoping for more exact steps (which is why I asked for a specific screen or action), to pass along to the development team for testing. Perhaps send a link to a page on your site where it’s happening and a (some) screenshot(s) of affected admin areas.

    It may seem redundant or pointless to you, but we need to know exactly how and where your site is affected, as everyone’s site is different and we’re not seeing those same warnings as you on our end. Additionally, “headers already sent” warnings are fairly common and can happen for any number reasons, especially when doing something like activating a plugin. If you’re getting those same warnings constantly, then that’s why it would be helpful for us to know exactly where and how.

    Thank you!

    Thread Starter adalov

    (@adalov)

    There is only one step that led to the issue, switching PHP versions, as already described. Our concern is mainly the “Trying to access array offset on value of type null …” warnings, not the headers. And yes, upon switching to PHP 8.0 the warnings are displayed constantly in the frontend on the landing page and every subpage as well as in the admin dashboard and, again, independently of any action like activating the plugin. I thought that was clear enough.

    Naturally, the site is not live with those warnings as we switched back to PHP7.4.
    I am sure that the first two warnings must be easily reproducible for the development team with our initial description.

    I hope that this is all you and the team need now for resolving the issue. In the meantime, we just commented out lines 151-152 in the restaurant-reservations.php file so that the mailchimp integration (that we will not use anyways) does not try to load and cause the warnings.

    However, pls still let me know what was done by the dev team from your end to resolve this.

    Thank you!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘PHP 8.0’ is closed to new replies.