Title: Block Visibility — Conditional Visibility Control for the Block Editor
Author: Nick Diego
Published: <strong>11 de agosto de 2020</strong>
Last modified: 18 de enero de 2026

---

Buscar plugins

![](https://ps.w.org/block-visibility/assets/banner-772x250.png?rev=3122657)

![](https://ps.w.org/block-visibility/assets/icon-256x256.png?rev=3122657)

# Block Visibility — Conditional Visibility Control for the Block Editor

 Por [Nick Diego](https://profiles.wordpress.org/ndiego/)

[Descargar](https://downloads.wordpress.org/plugin/block-visibility.3.7.1.zip)

[Vista previa](https://es.wordpress.org/plugins/block-visibility/?preview=1)

 * [Detalles](https://es.wordpress.org/plugins/block-visibility/#description)
 * [Valoraciones](https://es.wordpress.org/plugins/block-visibility/#reviews)
 *  [Instalación](https://es.wordpress.org/plugins/block-visibility/#installation)
 * [Desarrollo](https://es.wordpress.org/plugins/block-visibility/#developers)

 [Soporte](https://wordpress.org/support/plugin/block-visibility/)

## Descripción

Crea fácilmente contenido dinámico en WordPress que aumentará las conversiones, 
mejorará la experiencia del usuario y mejorará tu flujo de trabajo.

Con esta solución **sin código**, controla qué bloques son visibles en tu sitio 
web y quién puede verlos. Programa contenido para mostrar u ocultar en un momento
específico. Muestra promociones exclusivas a tus clientes o miembros. Restringe 
bloques a perfiles de usuario específicos, tamaños de pantalla, cadenas de consulta,
productos de WooCommerce, descargas de EDD, campos de ACF, etiquetas de WP Fusion
y más.

Block Visibility está construido exclusivamente para el editor de WordPress (Gutenberg)
y está diseñado para funcionar con **cualquier** bloque de WordPress. Esto incluye
bloques proporcionados de forma nativa por WordPress, bloques de terceros e incluso
widgets basados en bloques.

### ¡Crea bloques condicionales en segundos!

Trabaja directamente en el editor de WordPress con bloques que ya conoces. No es
necesario aprender a usar un editor externo ni una interfaz nueva. En cuestión de
segundos, puedes transformar bloques estáticos en contenido condicional y personalizado.

Sólo se necesitan **3 sencillos pasos**:

 1. Crea tu contenido usando **cualquier** bloque de WordPress.
 2. Selecciona las condiciones de visibilidad deseadas.
 3. ¡Guarda la página/entrada y maravíllate con los resultados!

### Lleno de características

Los **controles de visibilidad** determinan si un bloque debe ser visible para los
usuarios en la interfaz de usuario de tu sitio web. Las características incluyen:

 * **Ocultar** los bloqueos para todos los usuarios.
 * **Programa** cuándo debe ser visible el contenido utilizando una fecha/hora de
   inicio y finalización.
 * Mostrar bloques de forma condicional según el **tamaño de la pantalla** (escritorio,
   tableta, móvil y más)
 * Mostrar bloques solo a usuarios **conectados**.
 * Mostrar bloques solo a usuarios que hayan **salido**.
 * Mostrar bloques solo a usuarios con **perfiles específicos** (administrador, 
   suscriptor, cliente, miembro, etc.)
 * Mostrar bloques solo a **usuarios específicos**. Ideal para personalizar.
 * Muestra u oculta bloques dinámicos basados ​​en **cadenas de consulta de URL**.¡
   Ideal para campañas de marketing!
 * Mostrar u ocultar bloques según su **ubicación** y los «atributos» de su ubicación(
   tipo de entrada, taxonomía, archivo, etc.)
 * Mostrar bloques basados ​​en la **fuente de referencia** de un visitante del 
   sitio web (dominio/URL).
 * Es compatible para todos los **metadatos** de entradas y usuarios (campos personalizados).
 * Mostrar bloques basados ​​en **cookies** HTML.
 * **WooCommerce:** muestra u oculta bloques según productos, contenido del carrito,
   historial de compras del cliente y más.
 * **Advanced Custom Fields (ACF):** controla la visibilidad del contenido del bloque
   según los campos [ACF](https://wordpress.org/plugins/advanced-custom-fields/).
 * **Easy Digital Downloads:** muestra u oculta bloques según descargas, contenido
   del carrito, historial de compras del cliente y más.
 * **WP Fusion:** combina la visibilidad de bloques con el poder de [WP Fusion](https://wordpress.org/plugins/wp-fusion-lite/)
   para mostrar u ocultar contenido de forma condicional en función de los datos
   de tu CRM o plataforma de automatización de marketing favorita.

**Además:** los ajustes potentes te permiten personalizar la visibilidad del bloque
según tus necesidades o las de tus clientes.

 * Los preajustes de visibilidad te permiten controlar varios bloques a la vez.
 * Desactivar globalmente cualquier control de visibilidad.
 * Restrinje los controles de visibilidad a tipos de bloques específicos.
 * Establecer permisos para que sólo ciertos usuarios tengan acceso a las condiciones
   de visibilidad.
 * Configura hasta 4 puntos de interrupción diferentes para optimizar los controles
   de tamaño de pantalla.
 * Desactiva los indicadores contextuales y otras utilidades del plugin.
 * Personaliza el color del indicador contextual para mejorar la compatibilidad 
   del tema.
 * Activar el modo de control total 🚀 (consulta las FAQs).
 * Eliminar todos los ajustes del plugin al desinstalarlo.

### ¿Por qué necesito esto?

Si bien existen innumerables aplicaciones para los bloques condicionales, aquí hay
algunos ejemplos para comenzar:

 * Úsalo como herramienta de gestión de contenido. Oculta los bloques nuevos mientras
   trabajas en ellos, pero manten la página publicada.
 * Oculte temporalmente el contenido de temporada en tu sitio web en lugar de tener
   que eliminarlo.
 * Programa contenido promocional urgente o información de eventos para que se muestren
   automáticamente.
 * Mostrar u ocultar contenido específico en escritorio, tabletas o dispositivos
   móviles.
 * Restringe el contenido para que solo sea visible para tus clientes, miembros 
   o suscriptores.
 * Muestra mensajes a los usuarios que han salido, alentándolos a suscribirse a 
   tu blog.
 * Crea campañas de marketing únicas utilizando parámetros de cadena de consulta
   para mostrar mensajes personalizados ([Miralo en acción](https://www.blockvisibilitywp.com?bv_query=example))
 * Mostrar elementos condicionalmente en el editor del sitio usando lógica de visibilidad
   avanzada.
 * Aumenta la participación y las conversiones de los visitantes con contenido dinámico
   y personalización.

### ¿Por qué elegir Block Visibility?

**1. Fácil de usar**
 Block Visibility es la forma más sencilla de crear bloques
condicionales en WordPress. ¡Todo sin código y con solo unos clics!

**2. Un Equilibrio entre potencia y simplicidad**
 Block Visibility es para ti, 
ya sea que estés construyendo una sofisticada campaña promocional basada en el tiempo
para tus clientes o necesites ocultar algunos bloques en dispositivos móviles. ¿
No necesitas cierta funcionalidad? Cambialo en los ajustes del plugin.

**3. Soporte y desarrollo continuo**
 Block Visibility está diseñado, desarrollado
y respaldado por Nick Diego con contribuciones de la comunidad de Block Visibility.¿
Tienes una idea para lógica de bloque adicional? Háznoslo saber en el foro de soporte
del plugin.

 * [Base de conocimientos (documentación)](https://www.blockvisibilitywp.com/knowledge-base/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
 * [Foro de soporte](https://wordpress.org/support/plugin/block-visibility/)

Para una **valoración imparcial**, el plugin fue destacado en [WordPress Tavern](https://wptavern.com/show-and-hide-content-via-the-block-visibility-wordpress-plugin).

### Plays nice with others

Block Visibility está diseñado para funcionar con **cualquier** bloque y se prueba
con estas principales bibliotecas de bloques y plugins.

**Compatibilidad + integración directa**

 * [WooCommerce](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-woocommerce-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
 * [Advanced Custom Fields](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-advanced-custom-fields-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
 * [Easy Digital Downloads](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-how-to-use-the-easy-digital-downloads-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
 * [WP Fusion](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-wp-fusion-control/)

### Mantente conectado

Manténte actualizado sobre Block Visibility utilizando los enlaces a continuación.
El plugin también se está desarrollando de forma transparente en GitHub, así que¡
dale unas estrellas y síguenos! 😉

 * [Sitio web complementario](https://www.blockvisibilitywp.com/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
 * [Base de conocimientos](https://www.blockvisibilitywp.com/knowledge-base/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
 * [Canal de YouTube](https://www.youtube.com/channel/UCDsTrm-1766AmNqwdzwJ4KQ)
 * [Seguir en Twitter](https://twitter.com/BlockVisibility)
 * [Ver en GitHub](https://github.com/ndiego/block-visibility)

## Capturas

 * [[
 * Oculta o muestra bloques de forma rápida y sencilla en tu sitio web.
 * [[
 * Programa bloques utilizando ajustes de fecha y hora de inicio y finalización.
   También está disponible la recursión por día de la semana y hora del día. El 
   plugin proporciona una programación de bloques completa y funciona con todos 
   los bloques de Gutenberg, incluido WooCommerce, como se ve aquí.
 * [[
 * Mostrar u ocultar bloques en dispositivos móviles, tabletas, escritorio y más.
 * [[
 * Controla quién puede ver cada bloque de Gutenberg con restricciones de perfiles
   de usuario. Ideal para la personalización.
 * [[
 * Crea campañas de marketing únicas utilizando parámetros de cadena de consulta
   para mostrar mensajes personalizados.
 * [[
 * Las integraciones actuales incluyen Advanced Custom Fields, Easy Digital Downloads,
   WooCommerce y WP Fusion.
 * [[
 * Ajustes generales del plugin para activar o desactivar ciertas funciones, incluidos
   los permisos de usuario y el modo de control total.
 * [[
 * Elije qué controles de visibilidad condicional deseas utilizar en tu sitio.
 * [[
 * Desactiva o activa la visibilidad condicional en ciertos tipos de bloques con
   el administrador de bloques.

## Instalación

 1. Tienes un par de opciones:
 2.  * Go to Plugins → Add New and search for «Block Visibility.» Once found, click«
       Install.»
     * Descarg Block Visibility de WordPress.org y asegúrate de que la carpeta esté
       comprimida. Luego, subela mediante Plugins, Añadir nuevo ; Subir.
 3. Activa el plugin a través del menú «Plugins» en WordPress.
 4. Desde la página «plugins», dirígete directamente a la página «Ajustes» del plugin.
 5. ¡Comienza a aplicar controles de visibilidad condicional a todos los bloques!

## FAQ

### ¿Quién debería utilizar Block Visibility?

Block Visibilitys es un plugin poderoso pero simple que otorga a agencias de marketing,
bloggers, sitios web de comercio electrónico y propietarios de pequeñas empresas
la capacidad de mostrar u ocultar bloques en sus sitios web de manera condicional.
La necesidad de ocultar bloques de Gutenberg varía. Ya sea que necesites restringir
contenido a usuarios específicos como miembros o lanzar una campaña promocional 
en un momento particular con la programación de bloques, las aplicaciones son infinitas.

Si necesitas control de contenido dinámico en tu sitio web de WordPress, necesitas
Block Visibility.

### ¿Los controles de visibilidad condicional realmente funcionan con cualquier bloque? (¿Qué es el modo de control total?)

¡Sí! Sin embargo, no todos los tipos de bloques están activados por defecto. Los
controles solo se proporcionan a los bloques que se pueden añadir directamente a
una página/entrada mediante el inserto de bloques. Por lo tanto, algunos bloques
especializados, como los bloques hijos, no están incluidos por defecto. Un ejemplo
es el bloque de columna individual que es parte del bloque de columnas más grande.

Dicho esto, puedes activar el modo de control total en los ajustes del plugin. Estos
ajustes elimina todas las restricciones y añaden controles de visibilidad condicional
a cada bloque. Probablemente no necesitarás el modo de control total en la mayoría
de los casos, ¡pero está ahí si lo necesitas!

Además, aunque este plugin está diseñado para ser compatible con todos los bloques,
el ecosistema de WordPress está en constante expansión. Si encuentras un conflicto
con un bloque específico, háznoslo saber en el foro de soporte del plugin y lo investigaremos.
Estamos comprometidos a llevar controles de visibilidad de bloques a **todos** los
bloques de Gutenberg.

### ¿Se puede utilizar Block Visibility con cualquier tema de WordPress?

Sí, este plugin no es específico de un tema. Solo necesitas ejecutar la última versión
de WordPress y usar un tema que admita el editor de bloques. Este plugin no proporciona
ninguna funcionalidad al editor clásico.

### ¿Se añadiran más controles de visibilidad condicional en el futuro?

Sí, y si tienes una idea específica de lo que te gustaría ver, envía una solicitud
de característica en el foro de soporte de plugins en WordPress.org.

### ¿Este plugin funciona en el editor del sitio (edición completa del sitio)?

A partir de la versión 1.4.0, la Block Visibility es compatible en el editor del
sitio, que está disponible al utilizar un tema de bloques. Estamos comprometidos
a garantizar una compatibilidad del 100% con todas las funciones de edición completa
del sitio. Por favor, haznos saber en el foro de soporte del plugin si encuentra
errores o problemas de compatibilidad.

### ¿Block Visibility funciona con Elementor y otros maquetadores de páginas?

No. Block Visibility está diseñado específicamente para el editor de bloques de 
WordPress y por lo tanto, no funciona en páginas que controla el editor de Elementor
u otro maquetador de páginas. Siempre que edites contenido nativo de WordPress, 
Block Visibility funcionará.

### ¿Se controla la visibilidad del bloque mediante CSS?

La visibilidad se controla principalmente en el servidor, por lo que si un bloque
debe estar oculto según los controles de bloque establecidos, ni siquiera se mostrará.
Esta funcionalidad asegura que el plugin no cargue recursos adicionales en la portada
de tu sitio, optimizando así el rendimiento.

La **única excepción** a esto son los controles de bloque de tamaño de pantalla.
La visibilidad por tamaño de pantalla requiere el uso de CSS. Este CSS se carga 
en la parte frontal de su sitio si, y solo si, estos controles están activados. 
Puedes optar por desactivar este CSS y añadir los estilos necesarios tu mismo. Visita
la [Base de Conocimientos](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-screen-size-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
del plugin para obtener más información.

## Reseñas

![](https://secure.gravatar.com/avatar/b2630f1635f046600af04302e27abeafd14f91d0e121e157288d6189c02214cf?
s=60&d=retro&r=g)

### 󠀁[Flexible and easy to use](https://wordpress.org/support/topic/flexible-and-easy-to-use-51/)󠁿

 [efrap](https://profiles.wordpress.org/efrap/) 30 de marzo de 2026

Well made, easy to use, many options. Thank you!

![](https://secure.gravatar.com/avatar/e90ca75ac28e588c29d52563b2f6d310d306e0ff268368d8eb4ee5510a76b9cb?
s=60&d=retro&r=g)

### 󠀁[Great plugin](https://wordpress.org/support/topic/great-plugin-41367/)󠁿

 [songreen](https://profiles.wordpress.org/rafaelvp/) 18 de marzo de 2026

Great plugin! I use it alongside the Bogo multilingual plugin. It’s a clever way
to manage multilingual sites in FSE by displaying different navigation menus based
on the URL path. While dedicated premium multilingual plugins might offer more automated
features, this combination is a robust, lightweight, and perfect solution for small
websites on a budget.

![](https://secure.gravatar.com/avatar/ce94481de51a6948161a78017cddfd4df432e3127d50baac66e5db98e91ea0dd?
s=60&d=retro&r=g)

### 󠀁[Super useful!](https://wordpress.org/support/topic/super-useful-232/)󠁿

 [Mickaël Larguier](https://profiles.wordpress.org/mickaellrg/) 4 de marzo de 2026

I use this plugin on several sites I’ve built with Gutenberg and it adds really 
useful features. It offers a lot of flexibility without adding an intrusive interface.
Thanks for building this plugin!

![](https://secure.gravatar.com/avatar/1e1a25680e475fecfe864e95a191337dd090c9359233c00e2c78676055c370af?
s=60&d=retro&r=g)

### 󠀁[One of the best plugins](https://wordpress.org/support/topic/one-of-the-best-plugins-113/)󠁿

 [grayayer](https://profiles.wordpress.org/grayayer/) 30 de enero de 2026

Nick has truly gone above and beyond with this plugin. Block Visibility is something
that should be in core, but even beyond the basics, he’s provided the community 
with a truly enterprise/premium tool. The documentation is extensive and easy to
access. Unlike many other systems of hiding content (like the responsive visibility
settings in Kadence Blocks), all Block Visibility controls conditionally render 
content at the server level improving SEO and page speed. It’s important to note
that the Screen Size control is the only control that hides blocks using CSS.

![](https://secure.gravatar.com/avatar/d8e623dada24bea3d746370ff64a59995a8484e6228b0ffd4c5d49d708ac6957?
s=60&d=retro&r=g)

### 󠀁[Great plugin](https://wordpress.org/support/topic/great-plugin-41236/)󠁿

 [bkrg](https://profiles.wordpress.org/bkrg/) 27 de enero de 2026

I couldn’t hide certain blocks inside other blocks from plugins.Block Visibility
allowed me to do it very easily and quickly.Great!

![](https://secure.gravatar.com/avatar/ed84654fc75d2fa602e375e9a1c62cccab977cd0ae5d688bc56d5075d620902d?
s=60&d=retro&r=g)

### 󠀁[Very difficult to Understand How to Use](https://wordpress.org/support/topic/very-difficult-to-understand-how-to-use/)󠁿

 [jamescarson25](https://profiles.wordpress.org/jamescarson25/) 22 de enero de 2026
1 respuesta

You will not be using this right out of the box, as it is very difficult to use

 [ Leer todas las 106 reseñas ](https://wordpress.org/support/plugin/block-visibility/reviews/)

## Colaboradores y desarrolladores

«Block Visibility — Conditional Visibility Control for the Block Editor» es un software
de código abierto. Las siguientes personas han colaborado con este plugin.

Colaboradores

 *   [ Nick Diego ](https://profiles.wordpress.org/ndiego/)
 *   [ Outermost ](https://profiles.wordpress.org/outermostdesign/)

«Block Visibility — Conditional Visibility Control for the Block Editor» está traducido
en 12 idiomas. Gracias a [los traductores](https://translate.wordpress.org/projects/wp-plugins/block-visibility/contributors)
por sus contribuciones.

[Traduce «Block Visibility — Conditional Visibility Control for the Block Editor» a tu idioma.](https://translate.wordpress.org/projects/wp-plugins/block-visibility)

### ¿Interesado en el desarrollo?

[Revisa el código](https://plugins.trac.wordpress.org/browser/block-visibility/),
echa un vistazo al [repositorio SVN](https://plugins.svn.wordpress.org/block-visibility/)
o suscríbete al [registro de desarrollo](https://plugins.trac.wordpress.org/log/block-visibility/)
por [RSS](https://plugins.trac.wordpress.org/log/block-visibility/?limit=100&mode=stop_on_copy&format=rss).

## Registro de cambios

#### 3.7.1 – 2024-12-08

**Fixed**

 * [WooCommerce] Fixed bug where the «Time Since Order» rule was no calculating 
   the correct number of days.

#### 3.7.0 – 2024-11-08

**Changed**

 * Actualizado «probado hasta» WordPress 6.7.
 * Se actualizó «requiere al menos» WordPress 6.5.
 * Quitar ventanas tipográficas de las descripciones.

#### 3.6.1 – 2024-09-06

**Fixed**

 * [ACF] Se corrigió un error donde los campos ACF no se mostraban después de la
   actualización v3.6.0.

#### 3.6.0 – 2024-09-05

**Added**

 * [Location] Added ability to show/hide blocks in archive templates based on taxonomy
   attributes (Hierarchy, Relative Hierarchy, and Supports).
 * [Location] Added ability to show/hide blocks if the current post has an excerpt.

**Changed**

 * Front-end classes are now implemented using the HTML API.
 * Updated the `render_block` callback function to only fetch plugin settings if
   a block has visibility conditions set.
 * Updated deprecated Button component variant and size properties.
 * Updated popover placement and offsets.
 * Updated general component styling to match Core.
 * Updated React Select component to match Select controls in Core.
 * Refactored the main plugin class.
 * Refactored the setting tabs.
 * Refactored the link utility and updated all plugin links.
 * Removed control filters deprecated in v2.5.1.
 * Removed all usage of `get_file_data()`.

**Fixed**

 * Fixed backward compatibility error due to the unified extensibility APIs in WordPress
   6.6.
 * Fixed Widget Editor notice in WordPress 6.6+.
 * Fixed spacing in the Day of Week control.
 * Fixed Firefox content overflow issue with the React Select component.

#### 3.5.0 – 2024-07-20

**Changed**

 * Updated «Tested up to» to WordPress 6.6.
 * Updated «Requires at least» to WordPress 6.4.
 * Updated the `PluginMoreMenuItem` slot usage to support unified slots in 6.6 and
   ensure backward compatibility.

**Fixed**

 * [Date & Time] Fixed style bug in the day-of-week controls.
 * Fixed the `useCommand` import now that 6.4 is the minimum version.

#### 3.4.0 – 2024-04-01

**Added**

 * [Date & Time] Added the ability to set seasonal (year-agnostic) schedules.

**Changed**

 * Updated Playground blueprint with improved demo content.
 * Updated «Tested up to» to WordPress 6.5.
 * Updated «Requires at least» to WordPress 6.3.
 * To use conditional opacity, you now must also have conditional indicators active.
 * Set rewrites to false for the `visibility_preset` post type.
 * Updated the deprecated `__experimentalGetSettings` function with the stable `
   __getSettings` version.
 * [WooCommerce] When retrieving orders, both processing and completed orders are
   now included.

**Fixed**

 * Fixed enqueue styles console errors by enqueuing the conditional indicator stylesheet
   using `enqueue_block_assets`.

#### 3.3.0 – 2024-01-18

**Added**

 * [ACF] Added the ability to conditionally display blocks based on fields in options
   pages.
 * Added support for help descriptions and labels in rule fields.

**Changed**

 * [Screen Size] Breakpoint defaults are now displayed as placeholders in the plugin
   settings.
 * Improve the placement of the controls dropdown in the Visibility panel to match
   Core.

**Removed**

 * [ACF] Removed deprecated rule handling that was introduced in v1.8.0 (2021)

**Fixed**

 * [ACF] Fixed the broken rule set UI when cleared.
 * [Screen Size] Fixed fatal error caused by deleting a breakpoint and saving an
   empty value.

#### 3.2.0 – 2024-01-03

**Added**

 * [Location] Added ability to show/hide a block if the current user is the author
   of the current post or page.

**Changed**

 * Bumped the «Tested up to» version to WordPress 6.4.

#### 3.1.2 – 2023-10-14

**Fixed**

 * Fixed issue where the Visibility panel would display when data fetching was still
   in process, causing other errors.
 * Fixed issue where the Visibility panel would not display if the User Permissions
   setting was enabled and the user was an Admin.
 * Fixed incorrect error handling when data cannot be fetched.

#### 3.1.1 – 2023-09-21

**Fixed**

 * Fixed missing folders when the plugin was synced to WordPress.org.

#### 3.1.0 – 2023-09-21

**Added**

 * [WooCommerce] Added the [WooCommerce](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-woocommerce-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control. ([#83](https://github.com/ndiego/block-visibility/pull/83))
 * [Easy Digital Downloads] Added the [Easy Digital Downloads](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-how-to-use-the-easy-digital-downloads-control/-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control. ([#87](https://github.com/ndiego/block-visibility/pull/87))
 * Added a Command Palette command for «Manage Visibility Presets». Requires WordPress
   6.3+ or the latest version of Gutenberg. ([#84](https://github.com/ndiego/block-visibility/pull/84))
 * Added a Block Visibility Pro deprecation notice when Pro is installed and active.

**Changed**

 * Increased the minimum WordPress version to 6.2 and the minimum version of PHP
   to 7.0.
 * Moved all Block Visibility Pro features to the base plugin.
 * Refactored away from `getEntityRecord` ([#77](https://github.com/ndiego/block-visibility/pull/77)).
 * [Metadata] Improved support for metadata in array or object format. ([#86](https://github.com/ndiego/block-visibility/pull/86))

**Fixed**

 * Fixed typo on `hide_on_restricted_users` variable ([#64](https://github.com/ndiego/block-visibility/pull/64)).

#### 3.0.4 – 2023-07-14

**Fixed**

 * [Location] Fixed bug that prevented the Relative Hierarchy rule from working.
   The value field was set to multi-select when it should be a single selection.

#### 3.0.3 – 2023-06-04

**Changed**

 * Updated the `blockVisibility.contextualIndicatorClasses` filter to include more
   variables, which allows for more customization.

**Fixed**

 * [Query String] Fixed bug when using 0 as the value of a query parameter would
   cause unexpected results.

#### 3.0.2 – 2023-04-16

**Removed**

 * Removed visibility control defaults so the Visibility panel starts empty. This
   simplifies the interface and reduces confusion around Visibility Presets for 
   users that have no need for this functionality.

**Fixed**

 * Fixed bug that caused error when Visibility Presets were enabled on a block but
   no actual presets existed.
 * Fixed missing text domain in string.

#### 3.0.1 – 2023-03-25

**Fixed**

 * Fixed bug that caused translations to stop working in the Editor after the 3.0.0
   release.

#### 3.0.0 – 2023-03-23

**Added**

 * Added the [Browser & Device](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-browser-device-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control.
 * Added the [Cookie](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-cookie-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control.
 * Added the [Location](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-location-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control.
 * Added the [Metadata](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-metadata-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control.
 * Added the [Referral Source](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-referral-source-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control.
 * Added the [URL Path](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-url-path-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control.
 * Added the [Visibility Preset](https://blockvisibilitywp.com/knowledge-base/guide-to-visibility-presets/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control.
 * Added Day of Week and Time of Day functionality to the [Date & Time](https://blockvisibilitywp.com/knowledge-base/how-to-use-the-date-time-control/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control.
 * Added control set utility support.
 * Added local visibility control support.
 * Added the `ControlSetControls-` and `ControlSetControlsIntegrations-` slots for
   adding visibility control editor UI elements.
 * Added the `PluginSettings` slot for adding additional plugin settings.
 * Added the `VisibilityControls`, `VisibilityControlsGeneral`, and `VisibilityControlsIntegrations`
   slots for adding additional visibility control settings.
 * Added the `blockVisibility.globallyRestrictedBlockTypes` and `blockVisibility.
   widgetAreaRestrictedBlockTypes` filters to restrict visibility controls on specific
   block types.

**Changed**

 * Plugin scripts are now enqueued with `enqueue_block_editor_assets`, and previous
   workarounds have been removed.
 * Deprecated the `ControlSetControlsBottom-` slot, use `ControlSetControlsIntegrations-`
   instead.
 * Deprecated the `VisibilityControlsIntegrationsBottom` slot, use `VisibilityControlsIntegrations`
   instead.

**Removed**

 * Removed Pro upgrade link on the plugins admin page.
 * Removed Pro upsells from settings pages.
 * Removed block-level contextual indicator filters.
 * Removed the `blockVisibility.addControlSetModals` and `blockVisibility.addControlSetOptions`
   filters.
 * Removed the `ControlSetControlsTop-` and `ControlSetControlsMiddle-` slots.
 * Removed the `PluginSettingsEditorTop` and `PluginSettingsEditorTop` slots.
 * Removed the `PluginSettingsTop`, `PluginSettingsMiddle`, and `PluginSettingsBottom`
   slots.
 * Removed the `VisibilityControlsTop`, `VisibilityControlsMiddle`, and `VisibilityControlsBottom`
   slots.
 * Removed the `VisibilityControlsIntegrationsTop` and `VisibilityControlsIntegrationsBottom`
   slots.
 * Removed the `RuleSetOptionsTop`, `RuleSetOptionsMiddle`, `RuleSetOptionsBottom`,
   and `RuleSetMoreSettingsTools` slots.
 * [Date & Time] Removed the `block_visibility_frontend_test_date_time_schedule`
   filter.
 * [Date & Time] Removed the `VisibilityControlsDateTimeTop` and `VisibilityControlsDateTimeBottom`
   slots.
 * [Date & Time] Removed the `DateTimeScheduleToolbar-` and `DateTimeScheduleControlsTop-`,
   and `DateTimeScheduleControlsBottom-` slots.
 * [Date & Time] Removed the `ScheduleOptionsTools`, `ScheduleOptionsMiddle`, and`
   ScheduleOptionsBottom` slots.
 * [Screen Size] Removed the `ScreenSizeControls` slot.
 * [User Role] Removed the `VisibilityByRoleControls` slot.

#### 2.6.0 – 2023-02-13

**Added**

 * [ACF] Added support for «greater than», «greater than or equal», «less than»,
   and «less than or equal» operators for numeric and date/time fields.
 * [ACF] Added field type help message.

**Changed**

 * [ACF] Improved support for numeric and date/time fields.
 * [ACF] Improved support for «choice» fields.
 * Improved help message support in rule set fields.

**Removed**

 * [ACF] Removed frontend tests that were deprecated in v1.9.0.

**Fixed**

 * [ACF] Fix information popover position.
 * Fixed translations not working on the plugin settings page. Thanks @webaxones
   for discovering this issue and also for translating the plugin into French!
 * Fixed incorrect JSDoc tags throughout the plugin.

#### 2.5.4 – 2023-02-05

**Changed**

 * Improve Kadence Blocks support by only displaying the Visibility panel on the
   Advanced tab. (Requires Kadence Block 3.0+)
 * Explicitly set the InspectorControls group to «settings» for new tabbed interface
   in WordPress 6.2.

**Fixed**

 * Fixed bug in contextual indicators that would incorrectly add visibility classes
   to blocks.

#### 2.5.3 – 2023-01-24

**Fixed**

 * Fixed bug in contextual indicators that would override custom block classes added
   by third-party plugins. ([#61](https://github.com/ndiego/block-visibility/issues/61))

#### 2.5.2 – 2023-01-03

**Fixed**

 * Fixed bug in data fetching method used to return simplified variables in plugin
   settings.

#### 2.5.1 – 2023-01-03

**Changed**

 * Consolidated controls filters into a single filter.
 * Renamed and consolidated contextual indicator filters.

**Fixed**

 * Fixed conditional opacity CSS for text-only blocks. ([#54](https://github.com/ndiego/block-visibility/issues/54))
 * Fixed data fetching method to only return simplified variables in plugin settings.
 * Fixed incorrect translation strings.
 * Fixed styling on control reset button to match Core tools panels.

#### 2.5.0 – 2022-12-05

**Upgrade Notice**

Block Visibility now requires WordPress 6.0+ with version 2.5.0 and users of the
Pro add-on will need to upgrade to Pro 1.6.0 to take advantage of these latest enhancements.
There have also been updates to the way visibility defaults work. Check out the 
[release article](https://blockvisibilitywp.com/block-visibility-2-5-0-and-pro-1-6-0-release-notes/)
for more information.

**Added**

 * [Screen Size] Added filter for specifying blocks that are incompatible with the
   control.
 * Added loading indicator in Editor visibility panel while settings and variables
   are being fetched.
 * Added support for uncategorized block types in the Block Manager.
 * Added back the ability to enable or disable help notices and popovers in the 
   Editor.
 * Added subtle upsell messaging in the plugin settings dashboard.
 * Added Pro compatibility warning notice for versions 1.5.3 and lower.

**Changed**

 * **Block Visibility now requires WordPress 6.0 or greater.**
 * [User Role] Fetch users directly rather than rely on the Block Visibility variables
   endpoint.
 * Redesigned the Editor UI to match the WordPress 6.1 design system.
 * Redesigned the Block Manager.
 * Consolidated all external plugin links into single directory.
 * Optimized all custom SVG icons including those used in contextual indicators.
   Indicator stylesheet is now 50% smaller.

**Removed**

 * Removed visibility panel and toolbar controls on Custom HTML blocks in the block-
   based Widget Area due to incompatibility. Visibility controls are still available
   for the Custom HTML block in the post/page Editor as well as the Site Editor.
 * Removed unnecessary custom icons.
 * Removed support url from variables endpoint.

**Fixed**

 * [Advanced Custom Fields] Fixed bug where numeric ACF fields were not being evaluated
   correctly. ([#50](https://github.com/ndiego/block-visibility/issues/50))
 * [Screen Size] Fixed bug where using the Screen Size control and the `meow-gallery/
   gallery` block. Added better error handling to avoid a similar issue in other
   third-party blocks.
 * Fixed bug where resetting settings on a specific tab would reset all plugin settings.

#### 2.4.6 – 2022-11-02

**Fixed**

 * Fixed bug where contextual indicator styles caused issues with Cover blocks when
   a custom indicator color was chosen in WordPress 6.1.
 * Fixed bug where contextual indicator styles caused issues with hover states in
   the Site Editor when a custom indicator color was chosen in WordPress 6.1.

#### 2.4.5 – 2022-11-02

**Fixed**

 * Fixed bug where text blocks became nearly impossible to edit when visibility 
   controls were applied in WordPress 6.1.
 * Fixed bug where block contextual opacity was applied incorrectly to Cover blocks
   with overlay enabled.

#### 2.4.4 – 2022-10-08

**Changed**

 * Simplify REST API requests on the plugin settings page to increase performance
   and attempt to fix edge case fetch errors.

#### 2.4.3 – 2022-08-02

**Fixed**

 * Fixed incorrect filter attribute in WP Fusion visibility test.

#### 2.4.2 – 2022-05-09

**Fixed**

 * Fixed bug in classic themes that caused Screen Size inline styles to not load
   as expected.

#### 2.4.1 – 2022-05-09

**Changed**

 * The Screen Size CSS classes are now added via PHP allowing the control to be 
   used in dynamic blocks.

**Fixed**

 * Fixed bug where Screen Size inline styles would be printed multiple times.

#### 2.4.0 – 2022-04-10

**Added**

 * Added contextual block opacity settings.
 * Added information icons to all visibility controls with links to Knowledge Base.
 * Added cookie contextual indicator for Cookie control in Block Visibility Pro.

**Changed**

 * Removed tip/information modals from Editor. Information icons now direct users
   to the corresponding Knowledge Base pages.

**Fixed**

 * Fix indicator color styling in settings.

#### 2.3.1 – 2022-02-28

**Fixed**

 * Fixed issue with block-based widgets where widget markup would still be rendered
   even if the block content was not. ([#26])(https://github.com/ndiego/block-visibility/
   issues/26))
 * Fixed React Select input styling.
 * Fixed styles that were bleeding into the Editor.
 * Fixed linting errors.

#### 2.3.0 – 2021-12-14

**Added**

 * Added advanced User Role controls (User Rule Sets).
 * Allow Block Visibility Pro settings to disable local visibility controls.

**Changed**

 * Moved the default visibility control settings from the «General Settings» tab
   to the «Visibility Controls» tab.
 * The additional contextual indicator settings are now disabled when indicators
   are disabled.
 * Rule sets now support a custom rule label.
 * Temporarily remove the «Editor Notices» Block Editor setting since it’s no longer
   relevant. This setting will be evaluated and potentially reintroduced in v2.4.
 * Updated plugin compatibility to WordPress 5.9.

**Fixed**

 * Fixed issue where Visibility Presets would appear in available control defaults
   with Block Visibility Pro is enabled.
 * Fixed minor styling issues found in WordPress 5.9 testing.

#### 2.2.0 – 2021-10-29

**Added**

 * Added the ability to duplicate schedules and rule sets.
 * Added support for Visibility Presets in Block Visibility Pro.

**Changed**

 * Visibility controls and tools (reset controls, help, etc.) have been separated
   into two different dropdown menus to reduce menu length.
 * Managing visibility controls can now be done using the «eye» icon whereas tools
   are managed using the vertical dots icon.
 * Minor changes to labeling have been done throughout the plugin to improve clarity.

**Removed**

 * Removed all legacy visibility controls deprecated in version 1.6.0.
 * Removed control reset confirmation modal for a smoother user experience.
 * Removed redundant help/reminder text to simplify the user interface.

#### 2.1.2 – 2021-10-06

**Changed**

 * Updated incompatibility notice for the Screen Size control to include HTML blocks
   and directed users to a workaround.

**Fixed**

 * Fixed bug in the Date & Time control where timezones with +30 minute offsets 
   were not handled properly. Thanks @ashleyzwp for discovering this issue and opening
   a support ticket!
 * Fixed bug in Query String control that caused a test failure when multiple strings
   using the same query parameter were used. Thanks Lucian for discovering this 
   issue and opening a support ticket!
 * Fixed conflict with Sensei (and potentially other third-party plugins) caused
   by the render_block filter returning `null` when a block is hidden. An empty 
   string is now returned instead. Thanks Ted for discovering this issue and opening
   a support ticket!
 * Fixed bug caused by admin scripts being enqueued during DOING_AJAX. Thanks Ted
   for discovering this issue and opening a support ticket!

#### 2.1.1 – 2021-09-14

**Added**

 * Added contextual indicator support for the Metadata control in Block Visibility
   Pro.

**Changed**

 * Continued extensibility improvements of the control set toolbar menu.
 * Updated plugin logo on settings page.

**Fixed**

 * Fixed incorrect languages .pot file.
 * Fixed bug in rule set configuration.

#### 2.1.0 – 2021-09-09

**Added**

 * Added the ability to reset plugin settings and restore defaults from within the
   admin.
 * The Advanced Custom Fields control can now display blocks based on user fields.

**Changed**

 * Moved the create_date_time function to its own utility file. This allows for 
   its use across the plugin and Block Visibility Pro.
 * Refactored rule and rule set functionality to provide for greater extensibility.
 * Improve extensibility of the control set toolbar menu for future Pro add-on functionality.

**Removed**

 * Removed erroneous integration-checks.php file.

**Fixed**

 * Fixed bug where not all users would be fetched in the User Role control. Thanks
   @lenehanj for discovering this issue and opening a support ticket!
 * Fixed styling on multi-select components.
 * Fixed z-index on contextual indicators that was causing some unwanted overlapping.

#### 2.0.0 – 2021-07-27

**Added**

 * Added the ability to restrict visibility by specific users as part of the User
   Role control.
 * Added the ability to customize the color of the contextual indicators.
 * Added a «block not compatible» messaging to the Legacy Widget block in WordPress
   5.8, since the block does not support custom attributes.
 * Added Block Visibility Pro ad to settings pages to inform users about the Pro
   add-on.
 * Added a direct link to the plugin Knowledge Base in the plugin settings masthead.

**Changed**

 * Changed how the WP Fusion control logic works to be more intuitive. Now all tag
   conditions need to be _true_ for the block to be visible. In v1.9.1 and lower,
   the conditions operated independently. Thanks @marlonsabala for bringing this
   to our attention!
 * Changed the contextual indicator styling (again) to improve the UI/UX. Color 
   now defaults to the set `--wp-admin-theme-color` and indicators have been moved
   to the ::after pseudo element for improved block compatibility.
 * Changed the control toolbar styling to match the upcoming dimensions panel UI
   in Gutenberg.

**Removed**

 * Removed custom icon font for contextual indicators. Reverting back to SVG icons
   now that we have a more optimize approach.
 * Removed the «Getting Started» tab in the plugin settings and directed all help
   links to the Block Visibility website and WordPress.org support forum.
 * Removed the review and support popup on the plugin settings pages.

**Fixed**

 * Fixed error introduced in WordPress 5.8 on the block-based Widgets screen by 
   removing the wp-edit-post dependency from the plugin.
 * Fixed spelling errors in plugin settings. Thanks @paaljoachim!
 * Fixed display logic in the Date & Time control when a single schedule was disabled,
   but others were enabled.
 * Fixed display logic in the ACF control when a single rule set was disabled, but
   others were enabled.

#### 1.9.1 – 2021-06-18

**Added**

 * Added preliminary support for Block Visibility (and Pro) on the new block-based
   Widgets screen, the new Widget pane in the customizer, and the experimental Navigation
   screens added by Gutenberg.

**Fixed**

 * Fixed bug where a Block Editor critical error would sporadically occur for certain
   admin users when switching from Fullscreen in the Block Editor. Thanks @gsarig
   for discovering this issue and opening a support ticket!
 * Fixed PHP error that would occasionally occur when a previously set ACF field
   was deleted from the user’s website.
 * Fixed bug where contextual indicator style sheet was loading on incorrect admin
   pages.

#### 1.9.0 – 2021-06-07

**Added**

 * Added support for Block Visibility Pro.
 * Added rule set functionality to the ACF control. This allows you to create OR
   conditions within the ACF control.
 * Added «rule set» and «rule» architecture.
 * Added notice regarding compatibility issues with the Screen Size control and 
   the Shortcode Block, plus links to a workaround in the Knowledge Base.
 * Added additional Slots for integrating new visibility controls.

**Changed**

 * Replaced many Popover components in the block editor with Modal components for
   improved UI.
 * Replaced most other Button/Popover components with DropdownMenu components for
   improved UI.
 * The «Remove» schedule button is now an trashcan icon in the Schedule toolbar 
   to be consistent with Block Visibility Pro.
 * Plugin settings tabs are now directly navigable based on URL query parameter.
 * Controls are now alphabetically ordered in the control selectors.
 * Screen size control CSS is now conditionally loaded only when there are actually
   blocks using these settings.
 * Contextual indicators are now powered by a custom icon font to improve performance
   and decrease file size.
 * Minor UI enhancements throughout.

**Removed**

 * Removed the dummy frontend.css file which was used for the screen size control
   and required an extra file to be loaded. An alternative implementation is now
   used.

**Fixed**

 * Fixed error were editing the visibility of a duplicated block would also edit
   the original block. Thanks @mmcginnis for discovering this issue and opening 
   a support ticket!
 * Fixed unnecessary re-renders and loss of focus for slotted components by relocating
   withFilter HOCs outside of all render functions.
 * Fixed error in the Date & Time frontend test.
 * Fixed labels on the Query String control that were previously not translatable.
 * Fixed incorrect links to the plugin [Knowledge Base](https://www.blockvisibilitywp.com/knowledge-base/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme).

#### 1.8.0 – 2021-04-13

**Added**

 * Added the [Advanced Custom Field](https://www.blockvisibilitywp.com/knowledge-base/visibility-controls/advanced-custom-fields/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control, the second third-party integration for Block Visibility! 🎉
 * Added functionality for multiple [Date & Time](https://www.blockvisibilitywp.com/knowledge-base/visibility-controls/date-time/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   schedules. 🎉
 * Added the ability «invert» the Date & Time control per-block. By default, this
   control allows you to **show** the selected block if at least one schedule applies.
   You can now optionally **hide** the block if at least one schedule applies!
 * Added the ability to set default visibility controls.
 * Added the ability to easily reset the visibility controls on each block.

**Changed**

 * Updated control set controls toggle icon to be more consistent with WP core.
 * Updated popover styling to be more consistent with WP core.

**Removed**

 * Removed the `enable_scheduling` setting. Users can now easily toggle visibility
   controls at the block level so this setting is not longer needed. The entire 
   Date & Time control can still be enabled/disabled in the Visibility Control settings.
 * Removed conditional indicator support for the `startDateTime` and `endDateTime`
   properties that were deprecated in version 1.4.1. Frontend visibility tests for
   these properties are still operational, but will likely be removed in version
   2.0.

**Fixed**

 * Fixed WP Fusion filters to improve the integration.

#### 1.7.1 – 2021-03-29

**Fixed**

 * Fixed error in the plugin variables REST API route that caused the settings page
   not to load if WP Debug was enabled. Thanks @gsarig for discovering this issue
   and opening a support ticket!

#### 1.7.0 – 2021-03-29

**Added**

 * Added the [WP Fusion](https://www.blockvisibilitywp.com/knowledge-base/visibility-controls/wp-fusion/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control, the first third-party integration for Block Visibility! 🎉
 * Added the [Query String](https://www.blockvisibilitywp.com/knowledge-base/visibility-controls/query-string/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
   control, significantly increasing the marketing capabilities of Block Visibility!
   🎉
 * Added `react-select` as a project dependency for all multi-select fields.

**Changed**

 * Updated control set UI when multiple controls are enabled to emphasize that all
   control conditions need to be satisfied for the block to be visible.
 * The «Restricted User Roles» setting now uses `react-select` for a cleaner user
   interface.
 * Updated contextual indicator icons. A generic indicator is now displayed when
   more than 2 controls are enabled.

**Fixed**

 * Fixed issue where blocks that should have been hidden by enabled visibility controls
   were appearing in REST API requests. This allowed sophisticated users to «see»
   content that was not intended for them via a public endpoint, i.e. `wp-json/wp/
   v2/...`. This is now fixed. Thanks @tkraftner for reporting this.
 * Fixed issue where the REST API url was not being fetched correctly in the plugin
   settings for WP installations that had prefixed, or «relocated», the REST API.
   Thanks Mike for reporting this issue.
 * Fix minor error due to missing attribute schema.

#### 1.6.0 – 2021-03-21

**Added**

 * New UI allows users to toggle on and off the available visibility controls at
   the block level, making for a cleaner interface.
 * New «control sets» attribute structure which improves the scalability of the 
   plugin and allows nearly unlimited new features/functionality in the future.

**Changed**

 * Updated all visibility frontend tests to respect new «control sets» attribute
   structure while maintaining backwards compatibility.
 * Updated all editor conditional indicators to respect new «control sets» attribute
   structure while maintaining backwards compatibility.

**Removed**

 * Removed the obtrusive «Customize controls» admin notice in the editor in favor
   of a dismissible one-time «Quick tips» popup for new users.
 * Removed verbose attribute specification in the main plugin class for compatibility
   with blocks rendered server-side. This is no longer needed.
 * `hide-control-section.js` and corresponding function are no longer needed.

#### 1.5.3 – 2021-03-10

**Fixed**

 * Fixed PHP error triggered by missing hideBlock attribute setting. Thanks @muppix
   for discovering this issue and opening a support ticket!

#### 1.5.2 – 2021-03-06

**Added**

 * Added a support and review nudge on the plugin settings page in hopefully the
   least annoying way possible. 😉
 * New screenshots and readme updates.

**Fixed**

 * Fixed bug were visibility settings were still displaying for blocks disabled 
   by the Block Manager.
 * Fixed conditional indicators not displaying for extra large and extra small screen
   size controls.

#### 1.5.1 – 2021-02-28

**Fixed**

 * Fixed error where plugin settings were not being fetched from the REST api as
   expected. This issue impacted websites that had WordPress installed in a subdirectory.
   Thanks @elenasaygo for discovering this issue and opening a support ticket!
 * Fixed logic in the `get_current_user_role()` so no errors are thrown when WordPress
   installed in a subdirectory.

#### 1.5.0 – 2021-02-22

**Added**

 * **Screen Size** controls allow you to show or hide block based on the width of
   the screen (Desktop, Tablet, Mobile and more).
 * Added universal function for retrieving plugin settings.

**Changed**

 * Minor adjustments to settings layout and styles.
 * All documentation links have been updated to reflect website changes.

**Removed**

 * Removed legacy visibility controls in REST API settings class.

**Fixed**

 * Fixed error where scheduling controls were still active on the frontend when 
   disabled in the plugin settings.

#### 1.4.3 – 2021-02-06

**Fixed**

 * Error that occurred when plugin assets were enqueued on incorrect admin pages.
   Improved logic now dequeues assets on any admin page without the Block Editor.
   Thanks @gsarig for catching this!

#### 1.4.2 – 2021-01-19

**Fixed**

 * Error that occurred when the plugin was deleted.
 * Contextual indicator border not displaying on placeholder blocks (e.g. the Shortcode
   Block)

#### 1.4.1 – 2021-01-18

**Added**

 * The ability to disabled scheduling at the block level without having to remove
   the start and end date/times.
 * The `blockVisibility` «supports» variable to all blocks types that have visibility
   enabled. This provide a more consistent method for detecting whether a block 
   should have visibility controls or not.

**Changed**

 * The contextual indicator icons have been updated and are now more legible.
 * Refactored the scheduling controls.
 * Updated the Visibility by Role labels to be more consistent with standard WordPress
   labeling and nomenclature.

**Deprecated**

 * The `startDateTime` and `endDateTime` properties of the `blockVisibility` attribute
   have been deprecated. All new blocks will use the new `scheduling` property.

**Removed**

 * Visibility block attribute defaults in an effort to declutter block markup when
   only a few settings are enabled.

**Fixed**

 * Some third-party blocks were not receiving visibility controls when they should
   have, notably Jetpack blocks, due to the way their block JS is enqueued.

#### 1.4.0 – 2021-01-01

**Upgrade Warning**

For the long-term maintainability of the Block Visibility plugin, changes to the
underlying file structure were needed in version 1.4.0. Therefore, when you upgrade
from version 1.3.0 or lower, the plugin will deactivate and you will receive an 
error message. But don’t worry, simply re-activate Block Visibility and you are 
good to go.

This is an unfortunate issue that will occur only once. We apologize for any inconvenience
that this causes, but trust that this change better positions the plugin for many
exciting enhancements in the future!

**Added**

 * Preliminary compatibility with Full Site Editing features
 * Hooks and slots to support the upcoming Pro add-on

**Changed**

 * Block Visibility now requires WordPress 5.5+ to take advantage of new core functionality
 * The base plugin file is now simply `block-visibility.php` and the setup class
   has been moved
 * Redesigned the Block Visibility settings page
 * Refactored the methods for fetching plugin setting and variable data on the Block
   Visibility settings page

**Removed**

 * Component styling that is not longer needed since the version requirement for
   the plugin is now WordPress 5.5+

#### 1.3.0 – 2020-12-05

**Added**

 * User permissions now give website administrators control over who can use visibility
   settings
 * Custom REST API routes for retrieving plugin data

**Changed**

 * By default, visibility controls are now available to all users that have access
   to the Block Editor
 * Refactored the methods for fetching plugin setting and variable data in the Block
   Editor
 * Restructured much of the plugin with a more consistent file/folder layout

**Fixed**

 * Contextual indicator icon was incorrect when using all visibility controls and
   the block was disabled

#### 1.2.0 – 2020-11-15

**Added**

 * Added the ability to «hide on selected roles» in the Restrict by User Roles visibility
   control Thanks to @edwardsh for the feature request!

#### 1.1.0 – 2020-11-05

**Added**

 * Date and time controls for block scheduling
 * Contextual indicators for visibility setting to the Block Editor
 * A toolbar option for quickly hiding blocks
 * Additional plugin settings to dynamically control all the new features

#### 1.0.1 – 2020-08-11

**Fixed**

 * Addressed the PHP warning message that may appear on new installations

#### 1.0.0 – 2020-08-03

 * Initial Release

## Plugin de la comunidad

Este plugin está desarrollado y recibe soporte de una comunidad. [Contribuye a este plugin](https://github.com/ndiego/block-visibility)

## Meta

 *  Versión **3.7.1**
 *  Última actualización **hace 3 meses**
 *  Instalaciones activas **40.000+**
 *  Versión de WordPress ** 6.5 o superior **
 *  Probado hasta **6.9.4**
 *  Versión de PHP ** 7.4 o superior **
 *  Idiomas
 * [Danish](https://da.wordpress.org/plugins/block-visibility/), [Dutch](https://nl.wordpress.org/plugins/block-visibility/),
   [Dutch (Belgium)](https://nl-be.wordpress.org/plugins/block-visibility/), [English (US)](https://wordpress.org/plugins/block-visibility/),
   [French (France)](https://fr.wordpress.org/plugins/block-visibility/), [German](https://de.wordpress.org/plugins/block-visibility/),
   [Japanese](https://ja.wordpress.org/plugins/block-visibility/), [Korean](https://ko.wordpress.org/plugins/block-visibility/),
   [Kurdish (Sorani)](https://ku.wordpress.org/plugins/block-visibility/), [Persian](https://fa.wordpress.org/plugins/block-visibility/),
   [Spanish (Chile)](https://cl.wordpress.org/plugins/block-visibility/), [Spanish (Spain)](https://es.wordpress.org/plugins/block-visibility/)
   y [Vietnamese](https://vi.wordpress.org/plugins/block-visibility/).
 *  [Traducir a tu idioma](https://translate.wordpress.org/projects/wp-plugins/block-visibility)
 * Etiquetas:
 * [conditional blocks](https://es.wordpress.org/plugins/tags/conditional-blocks/)
   [conditional content](https://es.wordpress.org/plugins/tags/conditional-content/)
   [dynamic content](https://es.wordpress.org/plugins/tags/dynamic-content/)[restrict blocks](https://es.wordpress.org/plugins/tags/restrict-blocks/)
   [visibility](https://es.wordpress.org/plugins/tags/visibility/)
 *  [Vista avanzada](https://es.wordpress.org/plugins/block-visibility/advanced/)

## Valoraciones

 4.9 de 5 estrellas.

 *  [  102 valoraciones de 5 estrellas     ](https://wordpress.org/support/plugin/block-visibility/reviews/?filter=5)
 *  [  1 valoración de 4 estrellas     ](https://wordpress.org/support/plugin/block-visibility/reviews/?filter=4)
 *  [  0 valoraciones de 3 estrellas     ](https://wordpress.org/support/plugin/block-visibility/reviews/?filter=3)
 *  [  0 valoraciones de 2 estrellas     ](https://wordpress.org/support/plugin/block-visibility/reviews/?filter=2)
 *  [  3 valoraciones de 1 estrellas     ](https://wordpress.org/support/plugin/block-visibility/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/block-visibility/reviews/#new-post)

[Ver todas las valoraciones](https://wordpress.org/support/plugin/block-visibility/reviews/)

## Colaboradores

 *   [ Nick Diego ](https://profiles.wordpress.org/ndiego/)
 *   [ Outermost ](https://profiles.wordpress.org/outermostdesign/)

## Soporte

Problemas resueltos en los últimos dos meses:

     0 de 5

 [Ver el foro de soporte](https://wordpress.org/support/plugin/block-visibility/)