61pixels

That worked! Fixed both the weird Revisions box error as well as the dynamic previews

• PHP 8.2.10
• WordPress: 6.6.2?
• The Events Calendar: 6.6.4.2 and everything before (works), 6.7(problem, templates don’t show)
• Theme: Custom Theme

Wow. Now THAT is support! That’s better support than I’ve received from premium products in the past. Extremely impressed!

Thank you so much for a solution. It’s much appreciated! I honestly can’t believe I never really noticed it before until now. I think it’s because most use cases where I need to write inline code is when using JS solutions, and I always just disable that in my flexible previews with the is_preview() check to just output static html for the preview instead of loading the JS etc on the backend (could get messy I felt like with lots of blocks).

The drawback you mention I completely understand and thankfully really isn’t an issue for me. It’s not important for the #’s to instantly change when dragging the order. I only use the row_index to target that specific block for CSS/JS changes that are needed inline (seemed easier than using a RNG). So long as they are different, dragging to a new order won’t affect anything even if it doesn’t update instantly.

Thanks again so much!

Thanks so much for the prompt reply! Just verified your fix works perfectly (so far at least!)

Thanks again!

Figured this out. I was still using my old “flexible-loop.php” template part which called the fields the normal way in a big if statement calling the individual template parts.

Once I noticed that, I changed the code to your has_flexible, is_flexible and the errors were gone.

I didn’t realize it, but GoDaddy had PHP autoset to 8.03. I don’t think I’ve used anything 8.0+ yet, downgraded PHP to 7.4 and it appears the warning disappears.

Also for anyone else curious, after some Googling, I found just changing the word private to public on the corresponding line supposedly will fix the issue.

Thanks so much for the prompt and detailed response!

For anyone wondering, Yoast fixed in this in the newest version.

I can confirm that this is an issue on all of my sites as well.

• Using latest version of Yoast SEO 15.4
• no JS errors in console
• started up fresh WP install and added only Yoast

Installing the Enable jQuery Migrate Helper plugin DOES SOLVE the issue. So it’s definitely some deprecated JS in the Yoast plugin that’s causing the issue.

The problem is with their Select2.js library. It shouldn’t be loading when ACF is active, but it does, which causes all of the issues. Basically any ACF field using the select2.js library will have issues, as well as any other plugin like Yoast SEO just to name one.

I’ve provided a temporary solution here https://www.ads-software.com/support/topic/conflict-with-acf-advanced-custom-fields-2/ and Tribe is aware of the problem and working on a fix.

@barryhughes-1 Awesome to hear. Look forward to the patch.

This is the same problem affecting many plugins that use the select2.js library. The fix I posted in the following thread will fix it for you until Tribe fixes the actual problem. Just add the fix in your functions.php

https://www.ads-software.com/support/topic/conflict-with-acf-advanced-custom-fields-2/

@demaier It’s pretty common from what I’ve seen with plugins; loading their js/css on every single page. I honestly just think it’s laziness but there may be other reasons. It definitely can cause loads of issues, as we see here. Ironically Tribe has specific code in their plugin to look for ACF Pro, and if it’s active, not to load the Event Calendar’s version. Something must have happened in this latest update that broke that aspect though since it obviously no longer works.

@southernb No problem, happy it helped. There is probably a much more elegant way of doing it to be honest, but I am assuming they will fix the problem as it definitely is a bug considering they have code in place to prevent this (that just no longer works). I just needed a quick fix until then, and the code above which I got the idea from @sampryor seemed to work just fine.

I’m using ACF throughout my entire site and custom post types, so in my case I just whipped this up which seems to do the trick for me. It only loads the Event Calendar select2 on their admin pages. (not sure why they load it everywhere by default)

function deregister_tribe_select2() {
  $current_screen = get_current_screen();
  if( $current_screen->id !== "tribe_events" && $current_screen->id !== "tribe_venue"  && $current_screen->id !== "tribe_organizer") {
     wp_deregister_script('tribe-select2');
  }
}
add_action('admin_enqueue_scripts', 'deregister_tribe_select2');

Came here to post the same thing. One of the recent updates to Events Calendar broke any select2 fields with ACF. This includes the standard select boxes with stylized UI, page link fields, among others that use the select2 library.

Not sure how to fix the issue, but it’s easily repeatable and definitely related to an update to Events Calendar.