Version 1.9.1

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.

Version 1.9.0

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.

v1.9.0d tag includes fix for missing language file, fixes the ACF notice, and hotfix for font rendering issue in Safari.

Version 1.8.0

Added

• Added the Advanced Custom Field control, the second third-party integration for Block Visibility! 🎉
• Added functionality for multiple Date & Time 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.

Version 1.7.1

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!

Version 1.7.0

Added

• Added the WP Fusion control, the first third-party integration for Block Visibility! 🎉
• Added the Query String 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.

Version 1.6.0

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.

Version 1.5.3

Fixed

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

Version 1.5.2

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.

Version 1.5.1

Added

• Added plugin setting so users can toggle whether plugin-specific notices are displayed in the editor. Some power users may want to disable these notices.

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.
• Fixed minor styling issues in the editor when the user changes the admin color scheme.

Version 1.5.0

Added

• Screen Size controls allow you to show or hide blocks 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.