Not compatible with PHP and WordPress latest versions

  • Resolved Pappu Ann kristo

    (@prabasjalakai)


    11 months, 2 weeks ago

    WordPress active version: 6.4.2
    PHP active version: 8.1.25
    Got error
    ‘All-in-One Event Calendar: preg_match(): Passing null to parameter #4
    ($flags) of type int is deprecated @/wp-content/plugins/all-in-one-event-calendar/vendor/twig/Lexer.php:209

    PHP message: All-in-One Event Calendar: preg_match(): Passing null
    to parameter #4 ($flags) of type int is deprecated @
    /wp-content/plugins/all-in-one-event-calendar/vendor/twig/Lexer.php:221

    PHP message: All-in-One Event Calendar: Return type of
    Twig_Node::count() should either be compatible with Countable::count():
    int, or the #[\\ReturnTypeWillChange] attribute should be used to
    temporarily suppress the notice @/wp-content/plugins/all-in-one-event-calendar/vendor/twig/Node.php:217

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support yenmer

    (@yenmer)

    Hi @prabasjalakai

    Thanks for reaching out!
    To better assist you please fill out the following form here, and we will review your request.

    Sincerely,
    Yenmer.
    Timely Customer Support.

    Hi @yenmer, I’m having the same issue. Same error messages.

    WordPress v6.4.3
    All-in-One Event Calendar by Time.ly v3.0.1
    PHP 8.1

    I’m having this problem too. It has generated a 28GB error log for today (well, today is only 2/3 over for me so it will get bigger).

    nicollb

    (@nicollb)

    Same issue — my error log is so full of these errors, I can’t even find errors I need to address.

    I see this marked as “Resolved” — but no resolution posted. Anyone know what to do?

    Same issues for us:

    All-in-One Event Calendar: preg_match(): Passing null to parameter #4 ($flags) of type int is deprecated @ /wp-content/plugins/all-in-one-event-calendar/vendor/twig/Lexer.php:235 #8192

    This error is flagged for many different line numbers in the same Lexer.php file

    PHP Version 8.2

    This plugin has generated a 112GB logfile in the last 2 days. Please don’t just mark it resolved, please tell us what the fix is instead!

    • This reply was modified 4 months, 3 weeks ago by kbjunkie.
Viewing 6 replies - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.