Block Visibility — ブロックエディターの条件付き表示コントロール

説明

WordPress で動的コンテンツを簡単に作成して、コンバージョンを増やし、ユーザーエクスペリエンスを向上させ、ワークフローを改善します。

このノーコードソリューションを使用して、Web サイトで表示されるブロックと、それらを表示できるユーザーを制御します。特定の時間にコンテンツを表示または非表示にするスケジュールを設定します。顧客やメンバーに特別なプロモーションを表示します。ブロックを特定のユーザー権限、画面サイズ、クエリ文字列、WooCommerce 商品、EDD ダウンロード、ACF フィールド、WP Fusion タグなどに制限します。

Block Visibility は WordPress エディター (Gutenberg) 専用に構築されており、あらゆる WordPress ブロックで動作するように設計されています。これには、WordPress によってネイティブに提供されるブロック、サードパーティのブロック、さらにはブロックベースのウィジェットが含まれます。

仕組みを見る

詳細な動画については、YouTube チャンネルをご覧ください。

条件付きブロックを数秒で作成できます !

使い慣れたブロックを使用して、WordPress エディターで直接作業します。学ぶべき外部エディターや新しいインターフェースはありません。数秒で、静的ブロックを条件付きのパーソナライズされたコンテンツに変換できます。

3つの簡単な手順で動作させることができます。

  1. 任意の WordPress ブロックを使用してコンテンツを作成します。
  2. 希望の可視条件を選択します。
  3. 固定ページ / 投稿を保存して、結果に感動してください !

機能満載です

Visibility Controls は、ウェブサイトのフロントエンドでブロックをユーザーに表示するかどうかを決定します。機能は次のとおりです。

  • すべてのユーザーからブロックを非表示にします。
  • 開始日時と終了日時を使用して、コンテンツをいつ表示するかをスケジュールします。
  • 画面サイズに基づいて条件付きでブロックを表示 (デスクトップ、タブレット、モバイルなど) します
  • ログインユーザーにのみブロックを表示します。
  • ログアウトしたユーザーにのみブロックを表示します。
  • 特定の権限 (管理者、購読者、顧客、メンバーなど) を持つユーザーにのみブロックを表示します。
  • 特定のユーザーにのみブロックを表示します。パーソナライゼーションに最適です。
  • URL クエリ文字列に基づいて動的ブロックを表示または非表示にします。販促キャンペーンに最適です!
  • ブロックの場所とその場所の「属性」(投稿タイプ、タクソノミー、アーカイブなど) に基づいてブロックを表示または非表示にします。
  • ウェブサイト訪問者の参照元 (ドメイン / URL) に基づいてブロックを表示します。
  • すべての投稿とユーザーのメタデータ (カスタムフィールド) のサポート。
  • HTML Cookie に基づいてブロックを表示します。
  • WooCommerce: Show or hide blocks based on products, cart contents, customer purchase history, and more.
  • Advanced Custom Fields (ACF) : ACF に基づいてブロックコンテンツの表示を制御します。
  • Easy Digital Downloads: Show or hide blocks based on downloads, cart contents, customer purchase history, and more.
  • WP Fusion : Block Visibility と WP Fusion の力を組み合わせて、条件付きで表示または お気に入りの CRM またはマーケティングオートメーションプラットフォームのデータに基づいてコンテンツを非表示にします。

プラス : 強力な設定を使用すると、ブロックの可視性を自分のニーズやクライアントのニーズに合わせてカスタマイズできます。

  • 可視性プリセットを使用すると、複数のブロックを一度に制御できます。
  • 可視性コントロールをグローバルに無効にします。
  • 可視性コントロールを特定の種類のブロックに制限します。
  • 特定のユーザーのみが表示条件を設定できるように権限を制限します。
  • 画面サイズコントロールを最適化するために、最大4つの異なるブレークポイントを構成できます。
  • コンテキストインジケーターやその他のプラグインユーティリティを無効にします。
  • コンテキストインジケーターの色をカスタマイズして、テーマの互換性を高めます。
  • フルコントロールモードを有効にします 🚀 (FAQ を参照)。
  • アンインストール時にすべてのプラグイン設定を削除します。

これが必要な理由は ?

条件付きブロックには数え切れないほどのアプリケーションがありますが、ここではいくつかの例を紹介します :

  • コンテンツ管理ツールとして使用します。作業中は新しいブロックを非表示にしますが、ページは公開したままにします。
  • ウェブサイト上の期間指定コンテンツを、削除するのではなく一時的に非表示にします。
  • 時間制限のあるプロモーションコンテンツやイベント情報をスケジュールして、自動的に表示します。
  • デスクトップ、タブレット、またはモバイルデバイスで特定のコンテンツを表示または非表示にします。
  • コンテンツを制限して、顧客、メンバー、または購読者にのみ表示されるようにします。
  • ログアウトしているユーザーにメッセージを表示して、ブログの購読を促します。
  • クエリ文字列パラメーターを使用して独自のマーケティングキャンペーンを作成し、パーソナライズされたメッセージを表示します (実際の動作を見る)。
  • 高度な可視性ロジックを使用して、条件付きでサイトエディターに要素を表示します。
  • 動的なコンテンツとパーソナライゼーションにより、訪問者のエンゲージメントとコンバージョンを増やします。

Block Visibility を選択する理由は ?

1. 使いやすい
Block Visibility は、WordPress で条件付きブロックを作成する最も簡単な方法です。すべてコードなしで、数回クリックするだけです !

2. パワーとシンプルさのバランス
Block Visibility は、顧客向けに洗練された時間ベースのプロモーションキャンペーンを構築している場合でも、モバイルでいくつかのブロックを非表示にする必要がある場合でも役立ちます。一部の機能は必要ありませんか ? プラグイン設定でオフに切り替えることができます。

3. 役立つサポートと継続的な開発
Block Visibility は、より広範な Block Visibility コミュニティからの貢献により、Nick Diego によって設計、開発、およびサポートされています。追加のブロックロジックのアイデアがありますか ? プラグインサポートフォーラムでお知らせください。

公平なレビューのために、プラグインは WordPress Tavern で紹介されました。

他の人と交流する

Block Visibility は あらゆる ブロックで動作するように設計されており、これらのトップブロックライブラリとプラグインでテストされています。

互換性 + 直接的な連携

互換性

  • Jetpack
  • CoBlocks
  • Redux Framework
  • Ultimate Add-ons for Gutenberg
  • Kadence Blocks
  • GenerateBlocks
  • Otter Blocks
  • Atomic Blocks
  • Gutentor
  • Stackable
  • Getwid
  • EditorsKit
  • Genesis Blocks

問題を見つけましたか? プラグインサポートフォーラムでお知らせください。早急に調査いたします。より大きな WordPress ブロックエコシステムとの優れた互換性が最優先事項です。

接続を維持

以下のリンクを使用して、Block Visibility に関する最新情報を入手してください。プラグインも GitHub で透過的に開発されているので、スターを付けてフォローしてください ! 😉

スクリーンショット

  • Web サイトのブロックをすばやく簡単に表示や非表示にすることができます。
  • 開始日と終了日の設定を使用してブロックをスケジュールします。曜日と時刻の再帰も利用できます。プラグインは完全なブロックスケジューリングを提供し、ここに示すように WooCommerce を含むすべての Gutenberg ブロックで動作します。
  • モバイルデバイス、タブレット、デスクトップなどによってブロックを表示または非表示にします。
  • ユーザー権限の制限により、各 Gutenberg ブロックを表示できるユーザーを制御します。パーソナライゼーションに最適です。
  • クエリ文字列パラメーターを使用して独自のマーケティングキャンペーンを作成し、パーソナライズされたメッセージを表示します。
  • 現在の連携には、 Advanced Custom Fields 、 Easy Digital Downloads 、 WooCommerce 、および WP Fusion が含まれます。
  • ユーザー権限やフルコントロールモードなど、特定の機能を有効/無効にする一般的なプラグイン設定です。
  • サイトで使用する条件付き表示コントロールを選択します。
  • Block Manager を使用して、特定の種類のブロックの条件付き表示を無効または有効にします。

インストール

  1. You have a couple of options:
    • Go to Plugins → Add New and search for “Block Visibility.” Once found, click “Install.”
    • WordPress.org から Block Visibility をダウンロードし、フォルダーが圧縮されていることを確認します。 次に、プラグイン経由でアップロード → 新規追加 → アップロード。
  2. WordPress の「プラグイン」メニューからプラグインを有効にします。
  3. 「プラグイン」ページから、プラグインの「設定」ページに直接進みます。
  4. すべてのブロックに条件付き可視性コントロールの適用を始めましょう !

FAQ

Block Visibility を使用する必要があるのは誰ですか ?

Block Visibility は強力かつシンプルなプラグインで、マーケティング代理店、ブロガー、e コマース Web サイト、および中小企業の所有者に、Web サイトで条件付きでブロックを表示または非表示にする機能を提供します。Gutenberg ブロックを非表示にする必要性はさまざまです。メンバーなどの特定のユーザーにコンテンツを制限する必要がある場合や、ブロックスケジュールを使用して特定の時間にプロモーションキャンペーンを開始する必要がある場合などにも対応し、用途は無限大です。

WordPress Web サイトで動的なコンテンツコントロールが必要な場合は、Block Visibility が必要です。

条件付き可視性コントロールは、どのブロックでも本当に機能しますか ? (フルコントロールモードとは
?)

はい! ただし、すべての種類のブロックがデフォルトで有効になっているわけではありません。コントロールは、ブロック挿入機能によって固定ページ / 投稿に直接追加できるブロックにのみ提供されます。したがって、子ブロックなどの一部の特殊なブロックは、既定では含まれません。例として、より大きなカラムブロックの一部である個々のカラムブロックがあります。

つまり、プラグイン設定でフルコントロール モードを有効にできます。この設定により、すべての制限が削除され、条件付きの可視性コントロールがすべてのブロックに追加されます。ほとんどの場合、フルコントロールモードは必要ないでしょう !

さらに、このプラグインはすべてのブロックと互換性があるように設計されていますが、WordPress エコシステムは拡大を続けています。特定のブロックとの競合が見つかった場合は、プラグインサポートフォーラムでお知らせください。調査いたします。私たちは、すべての Gutenberg ブロックに可視ブロックコントロールを導入することに取り組んでいます。

Block Visibility はどの WordPress テーマでも使用できますか ?

はい、このプラグインはテーマ固有ではありません。WordPress の最新バージョンを実行し、ブロックエディターをサポートするテーマを使用するだけです。このプラグインは、Classic Editor に機能を提供しません。

今後、条件付きの可視性コントロールがさらに追加される予定はありますか ?

はい。具体的に見てみたいものがあれば、WordPress.org のプラグインサポートフォーラムに機能リクエストを送信してください。

このプラグインはサイトエディター (フルサイト編集) で動作しますか ?

バージョン1.4.0の時点で、ブロックテーマの使用時に利用できるサイトエディターでブロックの可視性がサポートされます。すべてのフルサイト編集機能との100% の互換性を保証することをお約束します。バグや互換性の問題を見つけた場合は、プラグインサポートフォーラムでお知らせください。

Block Visibility は Elementor やその他のページビルダーで機能しますか ?

No. Block Visibility is designed specifically for the WordPress block Editor and, therefore, does not work on pages that the Elementor editor or another page builder controls. So long as you edit native WordPress “block” content, Block Visibility will work.

Block Visibility は CSS を使用して制御されますか ?

可視性は主にサーバー上で制御されるため、設定されたブロックコントロールに基づいてブロックを非表示にする必要がある場合、ブロックはレンダリングされません。この機能により、プラグインはサイトのフロントエンドに追加のリソースをロードしないため、パフォーマンスが最適化されます。

これに対する1つの例外は、画面サイズブロックコントロールです。 画面サイズごとの表示には、CSS を使用する必要があります。この CSS は、これらのコントロールが有効になっている場合にのみ、サイトのフロント エンドに読み込まれます。この CSS を無効にして、必要なスタイルを自分で追加することを選択できます。プラグインのナレッジベースにアクセスして、詳細をご覧ください。

評価

2024年3月28日
Big thank you to the genius who built this. You just made my day. Keep on rocking!
2024年3月19日
Does exactly what it says, simple and "native like" UI. Totally recommended since it helps you with lot of block layout struggle while using FSE and you don't want to have tons of templates for every single case.
2024年3月6日
We use the plugin for displaying different blocks for an event website. This way, we don't have to edit every page (and potentially miss stuff) when the stage of the website (before registration, during registration, post event) changes. It would be nice to be able to compare against the values of short codes in addition to custom fields. (One can update the values of short codes in one place rather than updating the values of custom fields for each page.)
2024年2月19日 1 reply
no support no answers Ok support ask me, thanks
2024年2月13日
There are still some kinks to work out, but this plugin is one of the most useful things I've encountered for Wordpress in ages. The flexibility to show and hide blocks based on all sorts of logic tests is truly astounding. Well done!
76件のレビューをすべて表示

貢献者と開発者

Block Visibility — ブロックエディターの条件付き表示コントロール はオープンソースソフトウェアです。以下の人々がこのプラグインに貢献しています。

貢献者

“Block Visibility — ブロックエディターの条件付き表示コントロール” は6ロケールに翻訳されています。 翻訳者のみなさん、翻訳へのご協力ありがとうございます。

“Block Visibility — ブロックエディターの条件付き表示コントロール” をあなたの言語に翻訳しましょう。

開発に興味がありますか ?

コードを閲覧するか、SVN リポジトリをチェックするか、開発ログRSS で購読してみてください。

変更履歴

3.4.0 – 2024-04-01

Added

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

Changed

  • Update Playground blueprint with improved demo content.
  • Update “Tested up to” to WordPress 6.5.
  • Update “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.
  • Update the deprecated __experimentalGetSettings function with the stable __getSettings version.
  • [WooCommerce] When retrieving orders, both processing and completed orders are now included.

Fixed

  • Fix 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 control. (#83)
  • [Easy Digital Downloads] Added the Easy Digital Downloads control. (#87)
  • Added a Command Palette command for “Manage Visibility Presets”. Requires WordPress 6.3+ or the latest version of Gutenberg. (#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).
  • [Metadata] Improved support for metadata in array or object format. (#86)

Fixed

  • Fixed typo on hide_on_restricted_users variable (#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 control.
  • Added the Cookie control.
  • Added the Location control.
  • Added the Metadata control.
  • Added the Referral Source control.
  • Added the URL Path control.
  • Added the Visibility Preset control.
  • Added Day of Week and Time of Day functionality to the Date & Time 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)

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)
  • 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 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)
  • [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.

1.8.0 – 2021-04-13

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.

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 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.

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