Comments on: ACF PRO 6.7 Beta 1 https://www.advancedcustomfields.com/blog/acf-pro-6-7-beta-1/ Wed, 03 Dec 2025 17:27:34 +0000 hourly 1 https://wordpress.org/?v=6.8.3 By: Adrian https://www.advancedcustomfields.com/blog/acf-pro-6-7-beta-1/#comment-419286 Fri, 21 Nov 2025 11:34:18 +0000 https://www.advancedcustomfields.com/?post_type=blog&p=683964#comment-2281253 In reply to Juan de Paco.

Would be nice if you would care the same about WPML itself, which is bloated with this kind of notices and deprecation logs…

]]> By: Delicious Brains https://www.advancedcustomfields.com/blog/acf-pro-6-7-beta-1/#comment-419282 Thu, 20 Nov 2025 10:49:02 +0000 https://www.advancedcustomfields.com/?post_type=blog&p=683964#comment-2278520 </p> ]]> In reply to Juan de Paco.

Hi Juan, thanks and thanks for testing! Yes we are aware and will have those notices fixed in the next version 🙌

]]> By: Juan de Paco https://www.advancedcustomfields.com/blog/acf-pro-6-7-beta-1/#comment-419275 Tue, 18 Nov 2025 14:51:33 +0000 https://www.advancedcustomfields.com/?post_type=blog&p=683964#comment-2274672 Hi there, and congrats for this beta release!

This is Juan, from the WPML compatibility team. We have ben testing the beta package against WPML using our automated suite, and we consistently noticed some entries in our logs. Maybe those can ring a bell on your side:

PHP Notice:  Undefined variable: content in /wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php on line 1140
PHP Notice:  Undefined variable: is_preview in /wp-content/plugins/advanced-custom-fields-pro/pro/blocks.php on line 1140

This seems to come from the new filter acf/blocks/top_toolbar_fields getting some variables that were not defined yet.

Hope it helps. Cheers!

]]>