Merge pull request #5445 from eduard13/patch-layout-block-ifconfig

Improving the layout common customization with block ifconfig argument

Author: dobooth

guides/v2.2/frontend-dev-guide/layouts/xml-instructions.md

@@ -70,6 +70,7 @@ We recommend always adding a `name` to blocks. Otherwise, it is given a random n
 | `template` | A template that represents the functionality of the block to which this attribute is assigned. | template file name | no |
 | `as` | An alias name that serves as identifier in the scope of the parent element. | 0-9, A-Z, a-z, underscore (_), period (.), dash (-). Case-sensitive. | no |
 | `cacheable` | Defines whether a block element is cacheable. This can be used for development purposes and to make needed elements of the page dynamic. | `true` or `false` | no |
+| `ifconfig` | Makes the block's visibility dependent on a system configuration field. | XPath to the system configuration field. E.g. `contact/contact/enabled` | no |
 
 To pass parameters use the [`<argument></argument>`](#argument) instruction.
 

guides/v2.2/frontend-dev-guide/layouts/xml-manage.md

@@ -16,6 +16,7 @@ This article describes the following typical [layout](https://glossary.magento.c
 - [Create a container](#create_cont)
 - [Reference a container](#ref_container)
 - [Reference a CMS block](#ref_cms_block)
+- [Making the block visibility dynamic](#ref_config_block)
 - [Create a block](#xml-manage-block)
 - [Set the template used by a block](#set_template)
 - [Modify block arguments](#layout_markup_modify-block)
@@ -236,6 +237,16 @@ As a result, the CMS block is added to the bottom of the page.
 
 ![CMS Block]({{ site.baseurl }}/common/images/cms-block-reference.png)
 
+## Making the block visibility dynamic {#ref_config_block}
+
+Any block can be configured to show or not based on a [Magento/Config/Model/Config/Source/Yesno] system configuration field, using the `ifconfig` argument. For the value, use the XPath to the needed field.
+
+```xml
+<block class="Namespace\Module\Block\Type" name="block.example" ifconfig="my/yesno/field">
+    ...
+</block>
+```
+
 ## Set the template used by a block {#set_template}
 
 There are two ways to set the template for a block:
@@ -594,3 +605,4 @@ class Product
 [`<move>` instruction]: {{page.baseurl}}/frontend-dev-guide/layouts/xml-instructions.html#fedg_layout_xml-instruc_ex_mv
 [`before` and `after` attributes of `<block>`]: {{page.baseurl}}/frontend-dev-guide/layouts/xml-instructions.html#fedg_xml-instrux_before-after
 [Magento/Cms/Block/Block]: {{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Cms/Block/Block.php
+[Magento/Config/Model/Config/Source/Yesno]: {{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Config/Model/Config/Source/Yesno.php

guides/v2.3/frontend-dev-guide/layouts/xml-instructions.md

@@ -67,6 +67,7 @@ We recommend always adding a `name` to blocks. Otherwise, it is given a random n
 | `template` | A template that represents the functionality of the block to which this attribute is assigned. | template file name | no |
 | `as` | An alias name that serves as identifier in the scope of the parent element. | 0-9, A-Z, a-z, underscore (_), period (.), dash (-). Case-sensitive. | no |
 | `cacheable` | Defines whether a block element is cacheable. This can be used for development purposes and to make needed elements of the page dynamic. | `true` or `false` | no |
+| `ifconfig` | Makes the block's visibility dependent on a system configuration field. | XPath to the system configuration field. E.g. `contact/contact/enabled` | no |
 
 To pass parameters use the [`<argument></argument>`](#argument) instruction.
 

guides/v2.3/frontend-dev-guide/layouts/xml-manage.md

@@ -16,6 +16,7 @@ This article describes the following typical [layout](https://glossary.magento.c
 - [Create a container](#create_cont)
 - [Reference a container](#ref_container)
 - [Reference a CMS block](#ref_cms_block)
+- [Making the block visibility dynamic](#ref_config_block)
 - [Create a block](#xml-manage-block)
 - [Set the template used by a block](#set_template)
 - [Modify block arguments](#layout_markup_modify-block)
@@ -236,6 +237,16 @@ As a result, the CMS block added to the bottom of the page.
 
 ![CMS Block]({{ site.baseurl }}/common/images/cms-block-reference.png)
 
+## Making the block visibility dynamic {#ref_config_block}
+
+Any block can be configured to show or not based on a [Magento/Config/Model/Config/Source/Yesno] system configuration field, using the `ifconfig` argument. For the value, use the XPath to the needed field.
+
+```xml
+<block class="Namespace\Module\Block\Type" name="block.example" ifconfig="my/yesno/field">
+    ...
+</block>
+```
+
 ## Set the template used by a block {#set_template}
 
 There are two ways to set the template for a block:
@@ -597,3 +608,4 @@ You can remove navigation links from the 'My Account' dashboard on the storefron
 [`<move>` instruction]: {{page.baseurl}}/frontend-dev-guide/layouts/xml-instructions.html#fedg_layout_xml-instruc_ex_mv
 [`before` and `after` attributes of `<block>`]: {{page.baseurl}}/frontend-dev-guide/layouts/xml-instructions.html#fedg_xml-instrux_before-after
 [Magento/Cms/Block/Block]: {{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Cms/Block/Block.php
+[Magento/Config/Model/Config/Source/Yesno]: {{ site.mage2bloburl }}/{{ page.guide_version }}/app/code/Magento/Config/Model/Config/Source/Yesno.php