arjendejong

@joostdevalk I see that wordpress-seo\admin\class-primary-term-admin.php:25 still uses the class with the deprecated function (WPSEO_Frontend_Primary_Category). It’s probably not the right way of including the class, but when I change that to Yoast\WP\SEO\Integrations\Primary_Category (the new one), the error disappears.

It seems this deprecation error only happens when you have %category% in permalinks:

View post on imgur.com

All other tags work correctly, because with these tags the post_link_category isn’t being called.

These are the filters $wp_filter['post_link_category'] running on the wp-admin/edit.php page:

View post on imgur.com

As you can see, both are from Yoast and the one that’s causing it, is the second filter.

Alright, I’ll wait for the next update then. Thanks! ??

Hey, I’ve got the wrong ‘Store Locator’ plugin, my bad!

That’s awesome news! Glad it got integrated inside the plugin!

It seems that acf-input.js only loads the content in the DOM once when loading the page. It does not account for content coming in via a call to admin-ajax.php. That’s where my ‘fix’ comes in. It retrieves all fields again, including the ones from admin-ajax.php.

• This reply was modified 5 years, 10 months ago by arjendejong.
• This reply was modified 5 years, 10 months ago by arjendejong.
• This reply was modified 5 years, 10 months ago by arjendejong.

I’ve fixed this by adding the following at the end of the success function of the $.post function in js/admin.js:1055

if ('acf' in window) {
    acf.getFields(document);
}

This assumes that you have ACF loaded. Would it be possible to integrate this into your plugin? Or do you know a way to put this piece of code in my theme?

Hey,

I found something interesting. When disabling select2 from all plugins, on the widgets.php page I immediately get an error from acf-input.js saying select2 is not a function (which is clear because we disabled it) but that error does not appear when I open the widget in Mega Menu in nav-menus.php. https://imgur.com/WDLezwy However, when I click on the reload button in Chrome, the error appears in the console before vanishing because the page got reloaded. When I enable select2 again, on clicking reload, I can see the select transforming into a select2. When I immediately click the reload button again, stopping the browser from reloading the page, I can do everything with that field like I’m supposed to. It seems that something is preventing ACF from transforming the select into a select2 field. The script can only execute when reloading the page. Do you have any insight on this? Can you tell me if this behaviour also happens at your end?

Hey,

There’s only one select2 script being loaded (from WooCommerce) (select2 v4). ACF Pro loads the single select2 style. The console gives no errors, only: “admin.js?ver=2.5.3.2:16 Launched for Menu ID 10376” when clicking the blue button.

Here’s how I created the widget (functions.php). And here’s the JSON for the ACF field. Have ACF (pro) and WooCommerce installed. Thanks for helping me!