Changeset 2510989

Timestamp:

04/07/2021 04:48:22 PM (5 years ago)

Author:

iamfriendly

Message:

Update to version 0.2.4 from GitHub

Location:

content-visibility

Files:

• tags/0.2.4 (copied) (copied from content-visibility/trunk)
• tags/0.2.4/build/index.asset.php (modified) (1 diff)
• tags/0.2.4/content-visibility.php (modified) (1 diff)
• tags/0.2.4/includes/editor/class-editor.php (modified) (1 diff)
• tags/0.2.4/readme.txt (modified) (4 diffs)
• trunk/build/index.asset.php (modified) (1 diff)
• trunk/content-visibility.php (modified) (1 diff)
• trunk/includes/editor/class-editor.php (modified) (1 diff)
• trunk/readme.txt (modified) (4 diffs)

content-visibility/tags/0.2.4/build/index.asset.php

@@ -1 @@
-<?php return array('dependencies' => array('react', 'wp-blockEditor', 'wp-components', 'wp-compose', 'wp-element', 'wp-hooks', 'wp-i18n', 'wp-plugins', 'wp-polyfill'), 'version' => 'f2c1b1fc56917e5e84b71612446c7752');
+<?php return array('dependencies' => array('react', 'wp-blockEditor', 'wp-components', 'wp-compose', 'wp-element', 'wp-hooks', 'wp-i18n', 'wp-plugins', 'wp-polyfill'), 'version' => '609efb85338aa7a2f8177ec1f4cb9e12');

content-visibility/tags/0.2.4/content-visibility.php

@@ -12 +12 @@
  * Plugin URI:  https://richardtape.com/content-visibility/
  * Description: Content Visibility allows you to decide when, where, and to whom your blocks are visible.
- * Version:     0.2.2
+ * Version:     0.2.4
  * Author:      Rich Tape
  * Author URI:  https://richardtape.com/

content-visibility/tags/0.2.4/includes/editor/class-editor.php

@@ -77 +77 @@
             'post',
             'page',
+            'wp_block',
             $this->get_widget_screen_id(),
         );

content-visibility/tags/0.2.4/readme.txt

@@ -5 +5 @@
 Requires at least: 5.0
 Tested up to: 5.7.0
-Stable tag: 0.2.2
+Stable tag: 0.2.4
 Requires PHP: 7.0
 License: GPLv2 or later
@@ -14 +14 @@
 == Description ==
 
-Content Visibility provides a set of controls to say whether each discrete piece of content (or 'block' in WordPress parlance) should be shown to users who are signed in to your site or not. Additional add-ons provide controls for [**role-based**](https://github.com/richardtape/content-visibility-user-role) visibility and [**time-based**](https://wordpress.org/plugins/content-visibility-date-and-time/) visibility.
+Your Content. Your Rules. Decide who sees what and when. No setup or complex settings. Write content, decide who should see it, and press publish.
+
+Content Visibility provides a set of controls to say whether each discrete piece of content (or 'block' in WordPress parlance) should be shown to users who are signed in to your site or not. Additional add-ons provide controls for [**role-based**](https://github.com/richardtape/content-visibility-user-role) visibility, [**time-based**](https://wordpress.org/plugins/content-visibility-date-and-time/) visibility, and [**location-based**](https://wordpress.org/plugins/content-visibility-geolocation/) visibility. You can also show or hide blocks to folks using [RSS](https://wordpress.org/plugins/content-visibility-rss-feed/) Readers.
 
 ## Individual Block Controls
 
-Every individual block on all posts and pages on your site can have their own controls. Mix and match the visibility of blocks on a single page. Need some blocks to show to everyone and a few to only be available to your site's subscribers? No problem. Only want a message to appear on Christmas Day? You got it. Only want those who are signed in to your site to see certain pieces of content? Easy peasy.
+Every individual block on all posts and pages (and custom post types) on your site can have their own controls. Mix and match the visibility of blocks on a single page. Need some blocks to show to everyone and a few to only be available to your site's subscribers? No problem. Only want a message to appear on Christmas Day? You got it. Only want those who are signed in to your site to see certain pieces of content? Easy peasy.
 
 ## At a glance
@@ -41 +43 @@
  - [ ] REST API exploration. Should be fine for non-authenticated requests, but need to dive deeper for auth'd requests
  - [ ] Non-trivial dates. Think things like "Every Wednesday between 3pm and 4pm" or "First two weeks in November"
- - [ ] Geolocation: Show this block only to users whose connection is in France
+ - [x] [Geolocation](https://wordpress.org/plugins/content-visibility-geolocation/): Show this block only to users whose connection is in France.
  - [ ] Specific Users: Only show a block when a specific user is signed in
  - [ ] Specific 3rd-party plugin integrations. Show a block when someone has purchased something from your WooCommerce store. Or when someone has submitted a specific Gravity Form.
@@ -64 +66 @@
 
 == Changelog ==
+
+= 0.2.4 =
+* WordPress 5.7.0 compatibility.
+* Nothing really to see here. Fixed an issue with the build script which prevented 0.2.3 from being available in the plugins repo.
+
+= 0.2.3 =
+* Content Visibility controls now show on the reusable blocks edit screen in addition to when you insert a reusable block.
 
 = 0.2.2 =

content-visibility/trunk/build/index.asset.php

@@ -1 @@
-<?php return array('dependencies' => array('react', 'wp-blockEditor', 'wp-components', 'wp-compose', 'wp-element', 'wp-hooks', 'wp-i18n', 'wp-plugins', 'wp-polyfill'), 'version' => 'f2c1b1fc56917e5e84b71612446c7752');
+<?php return array('dependencies' => array('react', 'wp-blockEditor', 'wp-components', 'wp-compose', 'wp-element', 'wp-hooks', 'wp-i18n', 'wp-plugins', 'wp-polyfill'), 'version' => '609efb85338aa7a2f8177ec1f4cb9e12');

content-visibility/trunk/content-visibility.php

@@ -12 +12 @@
  * Plugin URI:  https://richardtape.com/content-visibility/
  * Description: Content Visibility allows you to decide when, where, and to whom your blocks are visible.
- * Version:     0.2.2
+ * Version:     0.2.4
  * Author:      Rich Tape
  * Author URI:  https://richardtape.com/

content-visibility/trunk/includes/editor/class-editor.php

@@ -77 +77 @@
             'post',
             'page',
+            'wp_block',
             $this->get_widget_screen_id(),
         );

content-visibility/trunk/readme.txt

@@ -5 +5 @@
 Requires at least: 5.0
 Tested up to: 5.7.0
-Stable tag: 0.2.2
+Stable tag: 0.2.4
 Requires PHP: 7.0
 License: GPLv2 or later
@@ -14 +14 @@
 == Description ==
 
-Content Visibility provides a set of controls to say whether each discrete piece of content (or 'block' in WordPress parlance) should be shown to users who are signed in to your site or not. Additional add-ons provide controls for [**role-based**](https://github.com/richardtape/content-visibility-user-role) visibility and [**time-based**](https://wordpress.org/plugins/content-visibility-date-and-time/) visibility.
+Your Content. Your Rules. Decide who sees what and when. No setup or complex settings. Write content, decide who should see it, and press publish.
+
+Content Visibility provides a set of controls to say whether each discrete piece of content (or 'block' in WordPress parlance) should be shown to users who are signed in to your site or not. Additional add-ons provide controls for [**role-based**](https://github.com/richardtape/content-visibility-user-role) visibility, [**time-based**](https://wordpress.org/plugins/content-visibility-date-and-time/) visibility, and [**location-based**](https://wordpress.org/plugins/content-visibility-geolocation/) visibility. You can also show or hide blocks to folks using [RSS](https://wordpress.org/plugins/content-visibility-rss-feed/) Readers.
 
 ## Individual Block Controls
 
-Every individual block on all posts and pages on your site can have their own controls. Mix and match the visibility of blocks on a single page. Need some blocks to show to everyone and a few to only be available to your site's subscribers? No problem. Only want a message to appear on Christmas Day? You got it. Only want those who are signed in to your site to see certain pieces of content? Easy peasy.
+Every individual block on all posts and pages (and custom post types) on your site can have their own controls. Mix and match the visibility of blocks on a single page. Need some blocks to show to everyone and a few to only be available to your site's subscribers? No problem. Only want a message to appear on Christmas Day? You got it. Only want those who are signed in to your site to see certain pieces of content? Easy peasy.
 
 ## At a glance
@@ -41 +43 @@
  - [ ] REST API exploration. Should be fine for non-authenticated requests, but need to dive deeper for auth'd requests
  - [ ] Non-trivial dates. Think things like "Every Wednesday between 3pm and 4pm" or "First two weeks in November"
- - [ ] Geolocation: Show this block only to users whose connection is in France
+ - [x] [Geolocation](https://wordpress.org/plugins/content-visibility-geolocation/): Show this block only to users whose connection is in France.
  - [ ] Specific Users: Only show a block when a specific user is signed in
  - [ ] Specific 3rd-party plugin integrations. Show a block when someone has purchased something from your WooCommerce store. Or when someone has submitted a specific Gravity Form.
@@ -64 +66 @@
 
 == Changelog ==
+
+= 0.2.4 =
+* WordPress 5.7.0 compatibility.
+* Nothing really to see here. Fixed an issue with the build script which prevented 0.2.3 from being available in the plugins repo.
+
+= 0.2.3 =
+* Content Visibility controls now show on the reusable blocks edit screen in addition to when you insert a reusable block.
 
 = 0.2.2 =