Title: 61pixels's Replies | WordPress.org --- # 61pixels [ ](https://wordpress.org/support/users/61pixels/) * [Profile](https://wordpress.org/support/users/61pixels/) * [Topics Started](https://wordpress.org/support/users/61pixels/topics/) * [Replies Created](https://wordpress.org/support/users/61pixels/replies/) * [Reviews Written](https://wordpress.org/support/users/61pixels/reviews/) * [Topics Replied To](https://wordpress.org/support/users/61pixels/replied-to/) * [Engagements](https://wordpress.org/support/users/61pixels/engagements/) * [Favorites](https://wordpress.org/support/users/61pixels/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 32 total) 1 [2](https://wordpress.org/support/users/61pixels/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/61pixels/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/61pixels/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Media Focus Point] Weird bug when setting focus point for Featured Image or ACF Image fields](https://wordpress.org/support/topic/weird-bug-when-setting-focus-point-for-featured-image-or-acf-image-fields/) * Thread Starter [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [4 months, 2 weeks ago](https://wordpress.org/support/topic/weird-bug-when-setting-focus-point-for-featured-image-or-acf-image-fields/#post-18770941) * Hi there, any update on when the fix will be implemented? I did some digging and narrowed it down to your close_overlay() function in script.js around line 90. THe problem is you’re looking for .wpcmfp-media-modal-content which doesn’t exist when setting a featured image so it’s defaulting to submitting the post as if you’re on the media attachment screen. Replacing it with this code seems to fix all the issues. * const isAttachmentEditPage = document.body.classList.contains(‘post-type-attachment’); if (isAttachmentEditPage && !document.querySelector(‘.media-modal’)) {const postForm = document.getElementById(‘post’);if (postForm) {postForm.submit();}} * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Media Focus Point] .close.button CSS style interferes with default WP CSS](https://wordpress.org/support/topic/close-button-css-style-interferes-with-default-wp-css/) * Thread Starter [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [11 months ago](https://wordpress.org/support/topic/close-button-css-style-interferes-with-default-wp-css/#post-18509487) * Awesome! Much appreciated. I had fixed it by adding my own class to overwrite it, but moving foward it looks like I won’t have to worry about that. Great plugin by the way, I’ve been testing it out on 2 client sites so far and it seems to work great. My clients are gonna love it. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Extended] 0.9.0.8 update causing various backend issues](https://wordpress.org/support/topic/0-9-0-8-update-causing-various-backend-issues/) * Thread Starter [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [1 year, 6 months ago](https://wordpress.org/support/topic/0-9-0-8-update-causing-various-backend-issues/#post-18120997) * That worked! Fixed both the weird Revisions box error as well as the dynamic previews * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Event Template Selection empty in 6.7.0](https://wordpress.org/support/topic/event-template-selection-empty-in-6-7-0/) * Thread Starter [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [1 year, 7 months ago](https://wordpress.org/support/topic/event-template-selection-empty-in-6-7-0/#post-18042537) - 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 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Extended] Using get_row_index always returns 1 in Dynamic Previews](https://wordpress.org/support/topic/using-get_row_index-always-returns-1-in-dynamic-previews/) * Thread Starter [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [1 year, 8 months ago](https://wordpress.org/support/topic/using-get_row_index-always-returns-1-in-dynamic-previews/#post-17997322) * 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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Extended] Clone field no longer will populate options as of latest ACF release](https://wordpress.org/support/topic/clone-field-no-longer-will-populate-options-as-of-latest-acf-release/) * Thread Starter [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [1 year, 10 months ago](https://wordpress.org/support/topic/clone-field-no-longer-will-populate-options-as-of-latest-acf-release/#post-17852431) * Thanks so much for the prompt reply! Just verified your fix works perfectly ( so far at least!) * Thanks again! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Advanced Custom Fields: Extended] $is_preview() throwing undefined warning on front-end](https://wordpress.org/support/topic/is_preview-throwing-undefined-warning-on-front-end/) * Thread Starter [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [2 years, 6 months ago](https://wordpress.org/support/topic/is_preview-throwing-undefined-warning-on-front-end/#post-17182658) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Flexible Content Preview for Advanced Custom Fields] PHP Warning FCP\Singleton::__wakeup() must have public visibility](https://wordpress.org/support/topic/php-warning-fcpsingleton__wakeup-must-have-public-visibility/) * Thread Starter [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [4 years, 5 months ago](https://wordpress.org/support/topic/php-warning-fcpsingleton__wakeup-must-have-public-visibility/#post-15118377) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] PHP Uncaught Error: Class ‘Yoast\WP\SEO\Conditionals\Slovak_Supp](https://wordpress.org/support/topic/php-uncaught-error-class-yoastwpseoconditionalsslovak_supp/) * Thread Starter [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [4 years, 9 months ago](https://wordpress.org/support/topic/php-uncaught-error-class-yoastwpseoconditionalsslovak_supp/#post-14710959) * Thanks so much for the prompt and detailed response! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Can’t edit any taxonomy term descriptions since WordPress 5.6 update](https://wordpress.org/support/topic/cant-edit-any-taxonomy-term-descriptions-since-wordpress-5-6-update/) * [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [5 years, 4 months ago](https://wordpress.org/support/topic/cant-edit-any-taxonomy-term-descriptions-since-wordpress-5-6-update/#post-13812682) * For anyone wondering, Yoast fixed in this in the newest version. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Can’t edit any taxonomy term descriptions since WordPress 5.6 update](https://wordpress.org/support/topic/cant-edit-any-taxonomy-term-descriptions-since-wordpress-5-6-update/) * [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [5 years, 5 months ago](https://wordpress.org/support/topic/cant-edit-any-taxonomy-term-descriptions-since-wordpress-5-6-update/#post-13780961) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] 4.6.4 and ACF conflict](https://wordpress.org/support/topic/4-6-4-and-acf-conflict/) * [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [8 years, 6 months ago](https://wordpress.org/support/topic/4-6-4-and-acf-conflict/#post-9681274) * 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://wordpress.org/support/topic/conflict-with-acf-advanced-custom-fields-2/](https://wordpress.org/support/topic/conflict-with-acf-advanced-custom-fields-2/) and Tribe is aware of the problem and working on a fix. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Conflict with ACF (Advanced Custom Fields)](https://wordpress.org/support/topic/conflict-with-acf-advanced-custom-fields-2/) * [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [8 years, 6 months ago](https://wordpress.org/support/topic/conflict-with-acf-advanced-custom-fields-2/#post-9679808) * [@barryhughes-1](https://wordpress.org/support/users/barryhughes-1/) Awesome to hear. Look forward to the patch. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Yoast index field conflict](https://wordpress.org/support/topic/yoast-index-field-conflict/) * [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [8 years, 6 months ago](https://wordpress.org/support/topic/yoast-index-field-conflict/#post-9678353) * 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://wordpress.org/support/topic/conflict-with-acf-advanced-custom-fields-2/](https://wordpress.org/support/topic/conflict-with-acf-advanced-custom-fields-2/) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[The Events Calendar] Conflict with ACF (Advanced Custom Fields)](https://wordpress.org/support/topic/conflict-with-acf-advanced-custom-fields-2/) * [61pixels](https://wordpress.org/support/users/61pixels/) * (@61pixels) * [8 years, 6 months ago](https://wordpress.org/support/topic/conflict-with-acf-advanced-custom-fields-2/#post-9678158) * [@demaier](https://wordpress.org/support/users/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](https://wordpress.org/support/users/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](https://wordpress.org/support/users/sampryor/) seemed to work just fine. Viewing 15 replies - 1 through 15 (of 32 total) 1 [2](https://wordpress.org/support/users/61pixels/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/61pixels/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/61pixels/replies/page/2/?output_format=md)