Working with WordPress and finding the perfect balance between creating an engaging homepage and providing flexible editing options for clients can be challenging. <\/p>\n\n\n\n
Recently, I came across a situation where I wanted to use custom WordPress Blocks (using ACF) and traditional Advanced Custom Fields (ACF) inputs on the homepage of a new website. However, combining the two seemed impossible.<\/p>\n\n\n\n
Therefore, I had to find a solution where I could create the entire page using blocks, but in doing so I also wanted some of this blocks to be only accessible when editting the homepage. <\/p>\n\n\n\n
After experimenting with various options, the following function achieved the desired result of enabling me to creating custom ACF blocks that would be enabled only on specific pages.<\/p>\n\n\n\n
\nfunction custom_load_blocks(){\n\n\tglobal $pagenow;\t\n\n $blocks_to_register = array(\n 'home-banner',\n\t\t 'home-intro',\n 'custom-gallery'\n );\n\n $blacklist_block_types = array();\n\n \/\/ Check if this is the intended custom post type\n if(is_admin() && in_array($pagenow,array('post-new.php','post.php'))){\n\n if (isset($_GET['post'])) {\n $post_id = (int)$_GET['post'];\n } elseif (isset($_POST['post_ID'])) {\n $post_id = (int)$_POST['post_ID'];\n }\n\n \/\/ If the post_id is set and it matches the front page, set the blacklist_block_types\n if($post_id !== (int)get_option('page_on_front')){\n\t\t\tif(get_post_type($post_id) != 'acf-field-group'){\n\t\t\t\t$blacklist_block_types = array(\n\t\t\t\t\t'home-banner',\n\t\t\t\t\t'home-intro'\n\t\t\t\t);\n\t\t\t}\n }\n\n }\n\n $blocks_to_register = array_diff($blocks_to_register, $blacklist_block_types);\n\n foreach ($blocks_to_register as $btr) {\n register_block_type(__DIR__ . '\/blocks\/' . $btr . '\/block.json');\n }\n\n}\nadd_action('init', 'custom_load_blocks');<\/code><\/pre><\/div>\n\n\n\nHow does this work?<\/h2>\n\n\n\n
Here’s a rundown of the code in the above function:<\/p>\n\n\n\n
function custom_load_blocks(){\n\n\tglobal $pagenow;<\/code><\/pre><\/div>\n\n\n\nThe custom_load_blocks()<\/code> function is defined with global $pagenow;<\/code> set as a global variable. This variable helps to determine the current page of the admin area where the custom blocks should be displayed.<\/p>\n\n\n\n$blocks_to_register = array(\n 'home-banner',\n 'home-intro',\n 'custom-gallery'\n);<\/code><\/pre><\/div>\n\n\n\nAn array of custom blocks to register is created. The blocks in this example are ‘home-banner’, ‘home-intro’, and ‘custom-gallery’. Additional blocks can be added to the array as needed.<\/p>\n\n\n\n
$blacklist_block_types = array();<\/code><\/pre><\/div>\n\n\n\nAn empty array is created to hold any block types that should not be displayed.<\/p>\n\n\n\n
if(is_admin() && in_array($pagenow,array('post-new.php','post.php'))){<\/code><\/pre><\/div>\n\n\n\nThis line checks if the user is an admin and if they are on the ‘post-new.php’ or ‘post.php’ pages. This ensures that the custom blocks are only registered when a post is being created or edited.<\/p>\n\n\n\n
if (isset($_GET['post'])) {\n $post_id = (int)$_GET['post'];\n} elseif (isset($_POST['post_ID'])) {\n $post_id = (int)$_POST['post_ID'];\n}<\/code><\/pre><\/div>\n\n\n\nThis section determines the post ID being edited. The $_GET['post']<\/code> and $_POST['post_ID']<\/code> parameters are used to extract the post ID being edited.<\/p>\n\n\n\nif($post_id !== (int)get_option('page_on_front')){<\/code><\/pre><\/div>\n\n\n\nThis line checks if the post being edited is not the front page of the website. If it is not the front page, then the custom blocks should not be displayed.<\/p>\n\n\n\n
if(get_post_type($post_id) != 'acf-field-group'){<\/code><\/pre><\/div>\n\n\n\nThis line checks if the post type being edited is not an ACF field group. ACF field groups are used to define custom fields for pages, posts, and other content types. If the post being edited is an ACF field group, then the custom blocks should all be displayed.<\/p>\n\n\n\n
$blacklist_block_types = array(\n 'home-banner',\n 'home-intro'\n);<\/code><\/pre><\/div>\n\n\n\nAn array of block types is created to blacklist the custom blocks that should not be displayed. In this example, ‘home-banner’ and ‘home-intro’ are blocked. This is because they are only intended to be used on the front page of the website.<\/p>\n\n\n\n
$blocks_to_register = array_diff($blocks_to_register, $blacklist_block_types);<\/code><\/pre><\/div>\n\n\n\nThe $blacklist_block_types<\/code> array is removed from the $blocks_to_register<\/code> array. This ensures that only the allowed custom blocks are registered.<\/p>\n\n\n\nforeach ($blocks_to_register as $btr) {\n register_block_type(__DIR__ . '\/blocks\/' . $btr . '\/block.json');\n}<\/code><\/pre><\/div>\n\n\n\nThe `register_block_type()<\/code>` function is called for each custom block that is allowed to be registered. The `__DIR__<\/code>` constant is used to specify the path to the custom block. This line registers the custom block with the ACF plugin, making it accessible to the editor.<\/p>\n\n\n\nadd_action('init', 'custom_load_blocks');<\/code><\/pre><\/div>\n\n\n\nThe custom_load_blocks()<\/code> function is added as an action to the init<\/code> hook. This ensures that the function is called during the initialization of the WordPress core.<\/p>\n\n\n\nThe custom function makes it easy to register custom blocks in WordPress using the ACF plugin. By specifying the pages where the blocks should be displayed, editors can easily access and use the blocks without concern that certain blocks may not be suitable within the page being editted.<\/p>\n","protected":false},"excerpt":{"rendered":"
Working with WordPress and finding the perfect balance between creating an engaging homepage and providing flexible editing options for clients can be challenging. Recently, I came across a situation where I wanted to use custom WordPress Blocks (using ACF) and traditional Advanced Custom Fields (ACF) inputs on the homepage of a new website. However, combining […]<\/p>\n","protected":false},"author":2,"featured_media":12036,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2],"class_list":["post-12035","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web-and-ux"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/posts\/12035","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/comments?post=12035"}],"version-history":[{"count":0,"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/posts\/12035\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/media\/12036"}],"wp:attachment":[{"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/media?parent=12035"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bronco.co.uk\/our-ideas\/wp-json\/wp\/v2\/categories?post=12035"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}