• Resolved jreedpasd

    (@jreedpasd)


    Upon the automatic upgrade to 6.11.01, the following error started appearing when going to the WordPress login screen, and random areas on the dashboard once logged it. If you refresh you can continue. but the error occurs again a few minutes later.

    Argument 3 passed to TEC\Events\Calendar_Embeds\Calendar_Embeds::disable_slug_changes() must be of the type array, object given, called in **Path to site on Server**/wp-includes/class-wp-hook.php on line 324

    Things I’ve done already
    – Disabled Events Calendar (Error Goes Away)
    – Updated Events Calendar to 6.11.02 (doesn’t change anything, error remains)
    – disabled all plugins except Events Calendar (Still an issue)
    – disabled all plugins except Events Calendar and changed theme to a default WordPress theme (Still Remains)

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Support Darian

    (@d0153)

    Hi @jreedpasd

    I’m glad you reached out. Let me assist you with this one.

    I tried replicating the issue on my end, but it’s working as expected. If you haven’t done so yet, could you please try activating the Twenty Twenty-One theme along with only The Events Calendar plugin, and see if that makes a difference?

    Also, by any chance, do you have a custom post type created by a plugin? If so, could you let me know which plugin created it? That information could help us determine if there’s a potential conflict or interaction affecting The Events Calendar.

    If it doesn’t help, could you provide the versions of the following:

    • PHP
    • WordPress

    Looking forward to your reply.

    Plugin Support Darian

    (@d0153)

    Hi @jreedpasd

    It looks like we haven’t heard back from you in a while, so I’ll go ahead and close this thread for now. If you need further assistance, feel free to reopen it or start a new thread.

    Thread Starter jreedpasd

    (@jreedpasd)

    Thanks for getting back and sorry for the delay. This issue currently impacting several sites more than just the one we saw in the beginning.

    To answer some of your questions:
    WordPress version: 6.7.2
    PHP Version: 8.2

    Plugins that I believe are creating post types are Formidable and NextGen Gallery. We also have “tickets” enabled within the Events Calendar.

    The issue still remains when I enable the Twenty Twenty One theme with the Events Calendar only.

    Thread Starter jreedpasd

    (@jreedpasd)

    I also forgot to add that are main theme for the web site is Divi

    Plugin Support tristan083

    (@tristan083)

    Hi @jreedpasd ,

    Thank you for your message and the information.

    To help us reproduce the issue, could you provide some detailed steps or screen recordings of what you’re doing that is leading you to the receive the error?

    Hi,

    I am having the same issue on our site esfk.se which runs on:
    WordPress 6.8
    The Events Calendar 6.11.2
    The Events Calendar Shortcode & Block 3.1
    TwentyFifteen with Child Theme
    PHP-version 7.4.33

    The error shows up randomly, so I would expect it is rather some background job that causes it…

    If you need some help to investigate this issue just let me know!

    Cheers,
    Dietmar

    • This reply was modified 1 year, 1 month ago by esfk.

    Hi again,

    I just checked on our staging site, which runs on the Twenty Twenty-Five theme and without the Shortcode & Block addon, and there the error shows up as well 🙁

    Plugin Support tristan083

    (@tristan083)

    Hi @esfk ,

    Thank you for your message and chiming in here.

    It would be great to learn how the error is being triggered as we’ve not been able to reproduce it in our testing environment running only the Twenty Twenty-One theme and only The Events Calendar plugins active.

    Would you be able to share the full stack trace of the error?

    Plugin Author Dimitris Pantazis

    (@dpantazis)

    Hey @jreedpasd @esfk,

    Thank you your reports and we are sorry you faced this issue.

    First let me start by saying this is resolved in the latest version of our plugin.

    Secondly, I’d like to provide a short explanation as to why that was happening and why it wasn’t a wide spread issue.

    Our code, was being too strict. Usually when writing code this is great as its easier to catch mistakes and you don’t have to deal with surprises. In this specific case though, the strict code wasn’t the appropriate solution.

    WP core documentation states that the 3rd argument of the wp_insert_post_data filter *should* be an array. So our code, was strictly expecting an array always. When it wasn’t an array, the fatal issue you encountered would surface.

    Now even though the correct approach would be for all code (plugins/themes/core/etc…) to always follow the documentation, since WP core is not enforcing an array but only suggests it, we made sure our code will also handle non-array values.

    Thank you,
    Dimi

    Plugin Support Darian

    (@d0153)

    Hi there,

    It appears that we haven’t heard back from you in a while, so I’ll go ahead and close this thread for now. If you need any more help, feel free to start a new thread and we’ll be happy to assist you.

    Thanks for the quick support 👍🏼

    Plugin Support Darian

    (@d0153)

    Hi @esfk

    Thanks for your message. If you have some time to review, that would be amazing!

    https://ww.wp.xz.cn/support/plugin/the-events-calendar/reviews/

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

The topic ‘“Disable_slug_changes() must be of the type array” Error’ is closed to new replies.