Title: Problem with ACF Blocktypes Last modified: May 20, 2021 --- # Problem with ACF Blocktypes * Resolved [henrikki](https://wordpress.org/support/users/henrikki/) * (@henrikki) * [5 years ago](https://wordpress.org/support/topic/problem-with-acf-blocktypes/) * Plugin works well but not with ACF blocks. They appear in plugin-blockmanager as “not supported”. In post you can add the visibility controls using the three dots but as the post is saved the confuguration for the block is lost. Is there are problem with the plugin or have we got to do someting about the blogs? Viewing 7 replies - 1 through 7 (of 7 total) * Plugin Author [Nick Diego](https://wordpress.org/support/users/ndiego/) * (@ndiego) * [5 years ago](https://wordpress.org/support/topic/problem-with-acf-blocktypes/#post-14461848) * Hi [@henrikki](https://wordpress.org/support/users/henrikki/), thanks for reaching out. I apologize for the issues you are having. * To confirm, you are having issues just with blocks created with ACF blocks? Is that correct? * If so, I will dive in and see what I can find out. * Thanks! * Nick * Thread Starter [henrikki](https://wordpress.org/support/users/henrikki/) * (@henrikki) * [5 years ago](https://wordpress.org/support/topic/problem-with-acf-blocktypes/#post-14462336) * Yes correct. That would be great if you can help. We have set up the blocks via the normal wordpress backend. Maybe we have to register them in functions the“ old fashion” way? That would not a nice way but ok of course as we encounter problems of other plugins too. * If needed: Access to our dev machine is possible * Plugin Author [Nick Diego](https://wordpress.org/support/users/ndiego/) * (@ndiego) * [5 years ago](https://wordpress.org/support/topic/problem-with-acf-blocktypes/#post-14464280) * [@henrikki](https://wordpress.org/support/users/henrikki/) I have requested a developer version of ACF Pro to investigate the issue that you are having. My guess is that the ACF blocks are not respecting/saving the block attributes provided by Block Visibility. I will followup once I know more. * Best, Nick * Thread Starter [henrikki](https://wordpress.org/support/users/henrikki/) * (@henrikki) * [5 years ago](https://wordpress.org/support/topic/problem-with-acf-blocktypes/#post-14464413) * so kind of you! * Plugin Author [Nick Diego](https://wordpress.org/support/users/ndiego/) * (@ndiego) * [5 years ago](https://wordpress.org/support/topic/problem-with-acf-blocktypes/#post-14466960) * Good morning [@henrikki](https://wordpress.org/support/users/henrikki/), * I was able to get a copy of ACF Pro and investigate the situation a bit more. * First off, you are correct that any ACF Blocks that you create do not show in the Block Manager in the settings page for the plugin. I will look into getting this fixed in a future version. ACF registers blocks a bit differently than normal and my block manager is just not picking them up in the interface. * However, I followed the [tutorial on ACF Blocks](https://www.advancedcustomfields.com/resources/blocks/) on their website to create a Testimonial Block. I was then able to add all the Block Visibility controls to the Testimonial block and everything worked as expected. * This leads me to believe that Block Visibility does work with ACF Blocks and there might be an issue with the custom blocks that you have built? Not trying to pass blame at all, but I am not able to find any issues on my end. Can you try creating the Testimonial block in their tutorial example and see if you are still running into issues? * Also let me know which visibility controls you are using and I can test those specifically on my end if that is helpful. * Best, Nick * Plugin Author [Nick Diego](https://wordpress.org/support/users/ndiego/) * (@ndiego) * [5 years ago](https://wordpress.org/support/topic/problem-with-acf-blocktypes/#post-14473654) * Good evening, * I have done more testing over the weekend and the plugin appears to be working as expected with all the ACF blocks I have created. Now granted, my ACF blocks have been pretty simple, but there are no conflicts that I can see or anticipate. Therefore, I am going to close out this ticket. * If you are continuing to have issues, please email me a copy of your custom ACF block code and I can take a more detailed look. The best email is (info at blockvisibilitywp dot com). * Best, Nick * [Jason LeMahieu (MadtownLems)](https://wordpress.org/support/users/madtownlems/) * (@madtownlems) * [4 years, 11 months ago](https://wordpress.org/support/topic/problem-with-acf-blocktypes/#post-14651920) * Just adding a note that my experience is the same as Nick’s: * Our ACF blocks don’t show up in the Settings Page’s Block Manager, but the Visibility Controls show up, save as expected, and function as expected. * [@henrikki](https://wordpress.org/support/users/henrikki/): Here’s a super basic proof of concept ACF Block you can download and try. If this block’s visibility controls don’t work for you, it sounds like you might have some other conflict * [https://gist.github.com/MadtownLems/63029916161d8289d8608a74540dbf17](https://gist.github.com/MadtownLems/63029916161d8289d8608a74540dbf17) Viewing 7 replies - 1 through 7 (of 7 total) The topic ‘Problem with ACF Blocktypes’ is closed to new replies. * ![](https://ps.w.org/block-visibility/assets/icon-256x256.png?rev=3122657) * [Block Visibility — Conditional Visibility Control for the Block Editor](https://wordpress.org/plugins/block-visibility/) * [Frequently Asked Questions](https://wordpress.org/plugins/block-visibility/#faq) * [Support Threads](https://wordpress.org/support/plugin/block-visibility/) * [Active Topics](https://wordpress.org/support/plugin/block-visibility/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/block-visibility/unresolved/) * [Reviews](https://wordpress.org/support/plugin/block-visibility/reviews/) * 7 replies * 3 participants * Last reply from: [Jason LeMahieu (MadtownLems)](https://wordpress.org/support/users/madtownlems/) * Last activity: [4 years, 11 months ago](https://wordpress.org/support/topic/problem-with-acf-blocktypes/#post-14651920) * Status: resolved