forked from ndiego/block-visibility
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathreadme.txt
813 lines (524 loc) · 41.2 KB
/
readme.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
=== Block Visibility — Conditional Visibility Control for the Block Editor ===
Author URI: https://www.nickdiego.com/?bv_query=readme
Contributors: ndiego, outermostdesign
Tags: visibility, dynamic content, conditional content, conditional blocks, restrict blocks
Requires at least: 6.0
Tested up to: 6.2
Requires PHP: 5.6
Stable tag: 3.0.3
License: GPL-2.0
License URI: http://www.gnu.org/licenses/gpl-2.0.html
Show or hide any WordPress block with ease. Schedule when blocks should be visible. Restrict blocks to specific screen sizes, user roles, post types, and more.
== Description ==
Effortlessly create dynamic content in WordPress that will increase conversions, enhance the user experience, and improve your workflow.
With this **no-code** solution, control which blocks are visible on your website and who can see them. Schedule content to show or hide at a specific time. Display exclusive promotions to your customers or members. Restrict blocks to specific user roles, screen sizes, query strings, ACF fields, WP Fusion tags, and more.
Block Visibility is built exclusively for the WordPress Editor (Gutenberg) and is designed to work with **any** WordPress block. This includes blocks natively provided by WordPress, third-party blocks, and even block-based widgets.
=== See How It Works ===
https://youtu.be/CW1L4vBpXjw
For more informational videos, visit our [YouTube channel](https://www.youtube.com/channel/UCDsTrm-1766AmNqwdzwJ4KQ).
=== Create Conditional Blocks in Seconds! ===
Work directly in the WordPress Editor with blocks you're already familiar with. There is no external editor or new interface to learn. In seconds, you can transform static blocks into conditional and personalized content.
It takes just **3 simple steps**:
1. Create your content using **any** WordPress block.
2. Select the desired visibility conditions.
3. Save the page/post and marvel at the results!
=== Packed With Features ===
**Visibility Controls** determine whether a block should be visible to users on the front end of your website. Features include:
* **Hide** blocks from all users.
* **Schedule** when content should be visible using a start and end date/time.
* Conditionally display blocks based on **screen size** (Desktop, Tablet, Mobile, and more)
* Only show blocks to **logged-in** users.
* Only show blocks to **logged-out** users.
* Only show blocks to users with **specific roles** (Administrator, Subscriber, Customer, Member, etc.)
* Only show blocks to **specific users**. Great for personalization.
* Show or hide dynamic blocks based on **URL query strings**. Great for marketing campaigns!
* Show or hide blocks based on their **location** and "attributes" of their location (post type, taxonomy, archive, etc.)
* Display blocks based on a website visitor's **referral source** (domain/URL).
* Support for all post and user **metadata** (custom fields).
* Display blocks based on HTML **cookies**.
* **Advanced Custom Fields (ACF):** Control the visibility of block content based on [ACF](https://wordpress.org/plugins/advanced-custom-fields/) fields.
* **WP Fusion:** Combine Block Visibility with the power of [WP Fusion](https://wordpress.org/plugins/wp-fusion-lite/) to conditionally show or hide content based on data from your favorite CRM or marketing automation platform.
**PLUS: Powerful Settings** allow you to customize Block Visibility to your needs or those of your clients.
* Visibility Presets allow you to control multiple blocks at once.
* Globally disable any visibility control.
* Restrict visibility controls to specific block types.
* Set permissions so only certain users have access to visibility conditions.
* Configure up to 4 different breakpoints to optimize the screen size controls.
* Disable contextual indicators and other plugin utilities.
* Customize the contextual indicator color to enhance theme compatibility.
* Enable Full Control Mode 🚀 (See the FAQs).
* Remove all plugin settings on uninstall.
=== Why Do I Need This? ===
While there are countless applications for conditional blocks, here are a few examples to get you started:
* Use as a content management tool. Hide new blocks while working on them, but keep the page published.
* Temporarily hide seasonal content on your website rather than having to delete it.
* Schedule time-sensitive promotional content or event information to display automatically.
* Show or hide specific content on desktops, tablets, or mobile devices.
* Restrict content so it's only visible to your customers, members, or subscribers.
* Display messaging to logged-out users, encouraging them to subscribe to your blog.
* Create unique marketing campaigns using query string parameters to display personalized messaging ([See it in action](https://www.blockvisibilitywp.com?bv_query=example))
* Conditionally display elements in the Site Editor using advanced visibility logic.
* Increase visitor engagement and conversions with dynamic content and personalization.
=== Why Choose Block Visibility? ===
**1. Easy to Use**
Block Visibility is the easiest way to create conditional blocks in WordPress. All with no code and just a few clicks!
**2. A Balance of Power and Simplicity**
Block Visibility is for you whether you're building a sophisticated time-based promotional campaign for your customers or need to hide a few blocks on mobile. Don't need certain functionality? Toggle it off in the plugin settings.
**3. Helpful Support and Continuous Development**
Block Visibility is designed, developed, and supported by Nick Diego with contributions from the broader Block Visibility community. Have an idea for additional block logic? Let us know in the plugin support forum.
- [Knowledge Base (Documentation)](https://www.blockvisibilitywp.com/knowledge-base/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
- [Support Forum](https://wordpress.org/support/plugin/block-visibility/)
For an **unbiased review**, the plugin was featured on [WordPress Tavern](https://wptavern.com/show-and-hide-content-via-the-block-visibility-wordpress-plugin).
=== Plays nice with others ===
Block Visibility is designed to work with **any** block and is tested with these top block libraries and plugins.
**Compatibility + Direct Integration**
* Advanced Custom Fields
* WP Fusion
* WooCommerce _(Integration coming soon)_
* Easy Digital Downloads _(Integration coming soon)_
**Compatibility**
* Jetpack
* CoBlocks
* Redux Framework
* Ultimate Add-ons for Gutenberg
* Kadence Blocks
* GenerateBlocks
* Otter Blocks
* Atomic Blocks
* Gutentor
* Stackable
* Getwid
* EditorsKit
* Genesis Blocks
Find an issue? Let us know in the plugin support forum, and we will investigate ASAP. Excellent compatibility with the greater WordPress block ecosystem is a top priority.
=== Stay Connected ===
Stay up-to-date on Block Visibility using the links below. The plugin is also being developed transparently on GitHub, so give it a star and follow along! 😉
* [Plugin Website](https://www.blockvisibilitywp.com/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
* [Knowledge Base](https://www.blockvisibilitywp.com/knowledge-base/?bv_query=readme&utm_source=block_visibility&utm_medium=plugin&utm_campaign=readme)
* [YouTube Channel](https://www.youtube.com/channel/UCDsTrm-1766AmNqwdzwJ4KQ)
* [Follow on Twitter](https://twitter.com/BlockVisibility)
* [View on GitHub](https://github.com/ndiego/block-visibility)
== Screenshots ==
1. Quickly and easily hide show or hide blocks on your website.
2. Schedule blocks using start and end date/time settings. Day-of-week and time-of-day recursion are also available. The plugin provides complete block scheduling and works with all Gutenberg blocks, including WooCommerce, as seen here.
3. Show or hide blocks on mobile devices, tablets, desktops, and more.
4. Control who can see each Gutenberg block with user role restrictions. Great for personalization.
5. Create unique marketing campaigns using query string parameters to display personalized messaging.
6. Current integrations include Advanced Custom Fields, Easy Digital Downloads, WooCommerce, and WP Fusion.
7. General plugin settings to enable/disable certain functionality, including user permissions and Full Control Mode.
8. Choose which conditional visibility controls you want to use on your site.
9. Disable or enable conditional visibility on certain block types with the Block Manager.
== Installation ==
1. You have a couple of options:
* Go to Plugins → Add New and search for "Block Visibility." Once found, click "Install."
* Download Block Visibility from WordPress.org and make sure the folder is zipped. Then upload via Plugins → Add New → Upload.
2. Activate the plugin through the 'Plugins' menu in WordPress.
3. From the 'Plugins' page, head directly to the plugin 'Settings' page.
4. Start applying conditional visibility controls to all blocks!
== Frequently Asked Questions ==
= Who should use Block Visibility? =
Block Visibility is a powerful yet simple plugin that gives marketing agencies, bloggers, eCommerce websites, and small business owners the power to conditionally show or hide blocks on their websites. The need to hide Gutenberg blocks varies. Whether you need to restrict content to specific users like members or launch a promotional campaign at a particular time with block scheduling, the applications are endless.
If you need dynamic content control on your WordPress website, you need Block Visibility.
= Do conditional visibility controls really work with any block? (What is Full Control Mode?) =
Yes! However, not all block types are enabled by default. Controls are only provided to blocks that can be added directly to a page/post by the block inserter. Therefore, some specialized blocks, such as child blocks, are not included by default. An example is the individual Column block that is part of the larger Columns block.
That said, you can enable Full Control Mode in the plugin settings. This setting removes all restrictions and adds conditional visibility controls to every block. You probably will not need Full Control Mode in most cases, but it is there if you do!
Furthermore, while this plugin is designed to be compatible with all blocks, the WordPress ecosystem is ever-expanding. If you find a conflict with a specific block, please let us know in the plugin support forum, and we will investigate. We are committed to bringing visibility block controls to **every** Gutenberg block.
= Can Block Visibility be used with any WordPress theme? =
Yup, this plugin is not theme-specific. You just need to run the latest WordPress version and use a theme that supports the block Editor. This plugin provides zero functionality to the Classic Editor.
= Will more conditional visibility controls be added in the future? =
Yes, and if you have a specific idea of what you would like to see, please submit a feature request in the plugin support forum on WordPress.org.
= Does this plugin work in the Site Editor (Full Site Editing)? =
As of version 1.4.0, Block Visibility is supported in the Site Editor, which is available when using a block theme. We are committed to ensuring 100% compatibility with all Full Site Editing features. Please let us know in the plugin support forum if you find bugs or compatibility issues.
= Does Block Visibility work with Elementor and other page builders? =
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.
= Is block visibility controlled using CSS? =
Visibility is controlled primarily on the server, so if a block should be hidden based on the set block controls, it will not even be rendered. This functionality ensures the plugin does not load any additional resources on the front end of your site, thereby optimizing performance.
The **one exception** to this is the Screen Size block controls. Visibility by screen size requires the use of CSS. This CSS is loaded to the front end of your site if, and only if, these controls are enabled. You can opt to disable this CSS and add the necessary styles yourself. Visit the plugin [Knowledge Base](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) to learn more.
== Changelog ===
= 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
== Upgrade Notice ==
= 1.4.0 =
Version 1.4.0 includes a necessary file structure change that will deactivate the plugin when upgrading and throw an error message. But don't worry, simply re-activate Block Visibility and you are good to go. We apologize for this inconvenience and it will not happen again.