Thousands of errors for PHP 8.x

  • Resolved Matthias Pabst

    (@matthiaspabst)


    8 months ago

    The plugin version 3.0.1 fills up the error log! Please fix this!

    [Fri Mar 22 10:34:39 2024] [php:notice] [pid 22751] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/query/helper.php:160 #8192
[Fri Mar 22 10:34:39 2024] [php:notice] [pid 22751] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: Return type of Ai1ec_Abstract_Query::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/http/request/abstract.php:198 #8192
[Fri Mar 22 10:34:39 2024] [php:notice] [pid 22751] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: Return type of Ai1ec_Abstract_Query::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/http/request/abstract.php:208 #8192
[Fri Mar 22 10:34:39 2024] [php:notice] [pid 22751] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: Return type of Ai1ec_Abstract_Query::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/http/request/abstract.php:215 #8192
[Fri Mar 22 10:34:39 2024] [php:notice] [pid 22751] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: Return type of Ai1ec_Abstract_Query::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/http/request/abstract.php:222 #8192
[Fri Mar 22 10:34:41 2024] [php:notice] [pid 22766] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: preg_split(): Passing null to parameter #3 ($limit) of type int is deprecated @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/query/helper.php:160 #8192
[Fri Mar 22 10:34:41 2024] [php:notice] [pid 22766] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: Return type of Ai1ec_Abstract_Query::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/http/request/abstract.php:198 #8192
[Fri Mar 22 10:34:41 2024] [php:notice] [pid 22766] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: Return type of Ai1ec_Abstract_Query::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/http/request/abstract.php:208 #8192
[Fri Mar 22 10:34:41 2024] [php:notice] [pid 22766] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: Return type of Ai1ec_Abstract_Query::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/http/request/abstract.php:215 #8192
[Fri Mar 22 10:34:41 2024] [php:notice] [pid 22766] [client 123.123.123.123] [host www.domain.de] All-in-One Event Calendar: Return type of Ai1ec_Abstract_Query::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice @ /is/htdocs/path/wp-content/plugins/all-in-one-event-calendar/lib/http/request/abstract.php:222 #8192
Viewing 4 replies - 16 through 19 (of 19 total)

  • This issue has not really been resolved. The ‘new’ version they are directing you to does not work in the same way as the legacy version. We cannot have part of our content in an iFrame hosted by an outside company. Firstly, there are potential GDPR issues and secondly, the display is totally different and no longer seem to have the nice sidebar widgets we rely on.

    I am involved with several different charity websites that have used this plugin. Where we tried to update to the new version we gave up as and can no longer using the plugin. I now need to update the php version to 8 for the rest of the WordPress sites I am involved with. I see there are suggestions for editing the plugin code but unfortunately I no longer feel comfortable doing this. Which means we can no longer use this plugin. What a shame. The legacy version was great.

    Can anyone recommend another calendar plugin that works in a similar way to the legacy timely one?

    dshaykewich

    (@dshaykewich)

    @vinjoy707

    I just wanted to say thank you very much for your detailed instructions above. Our logs were being overwhelmed after an upgrade (aka “old bugs out, new bugs in”) to PHP8.

    After combing through the vendor code (which makes me feel so dirty) to clean up some of the mis-typed calls to things like str_replace and preg_match and adding the AllowDynamicProperties property, our logs are looking much better.

    Thank you again @vinjoy707!

    vinjoy707

    (@vinjoy707)

    @dshaykewich,

    I’m happy that I was able to help and can only sympathize with your plight. The extensive logging of deprecation notices etc. after moving to PHP8 was a frustration for me too. I wouldn’t feel too bad about getting your hands dirty with plugin edits if it means your site operates more smoothly and your host is not overwhelmed with enormous log files.

    The biggest challenge we face is deciding how to move forward. I doubt very much whether the developers at Time.ly have any incentive or motivation to upgrade the legacy plugin to support PHP8. It’s not just their own code, but the other open source projects they have leveraged to build their product (e.g. iCalcreator, Twig). Updating the core code to support PHP8 plus the newest versions of these other tools is likely quite a chore.

    Good luck to you (and all the long-term users out there struggling with this issue).

    dshaykewich

    (@dshaykewich)

    Agreed, @vinjoy707, I don’t see them investing the kind of time required to update their own code and library dependencies to keep providing (and supporting) a free plugin, especially with their paid cloud service available. Some of the code I updated in Twig was from 2009! (I have to admit, I was saying to myself, “you should not be editing this code – all the changes will be lost when they update the plugin”. Then, I said, “give your head a shake – they’re not going to update it!”)

    We’re going to look at a different options for our events listings. Our biggest blocker is that we add artifacts to past events (e.g., video recording of the online event) so that they’re available on our site. Migrating that content to a new plugin/other software will be a job.

    Thanks again! All the best to you!

Viewing 4 replies - 16 through 19 (of 19 total)
  • You must be logged in to reply to this topic.