Download the PHP package xwp/block-visibility-edge-cache without Composer
On this page you can find all versions of the php package xwp/block-visibility-edge-cache. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download xwp/block-visibility-edge-cache
More information about xwp/block-visibility-edge-cache
Files in xwp/block-visibility-edge-cache
Package block-visibility-edge-cache
Short Description Handles edge cache invalidation for blocks with time-based visibility settings.
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package block-visibility-edge-cache
Block Visibility Edge Cache
A WordPress plugin that integrates the Block Visibility plugin with WordPress.com VIP edge caching. It ensures that edge caches are automatically purged at the exact moment a block's visibility is scheduled to change.
How it Works
When using edge caching, page content is cached at the "edge" (servers closer to the user). Traditional "Date/Time" visibility rules in the Block Visibility plugin usually rely on PHP executing during the page load to decide whether to show or hide a block. With edge caching, PHP might not run for every request, leading to stale content being served even after a visibility transition should have occurred.
This plugin solves this by:
- Parsing the blocks in a post when it is saved or published.
- Calculating all future "transition" timestamps (when a block should appear or disappear) based on the Date/Time settings.
- Scheduling background tasks using Action Scheduler to purge the post's edge cache at those specific timestamps.
Requirements
- PHP 8.4+
- WordPress 6.0+
- Block Visibility plugin
- Action Scheduler (bundled with the plugin or available via WooCommerce)
Installation
Via Composer (Recommended)
Manual
- Upload the plugin folder to the
/wp-content/plugins/directory. - Activate the plugin through the 'Plugins' menu in WordPress.
- Ensure the Block Visibility plugin is also active.
Supported Visibility Controls
To maintain compatibility with edge caching, only time-based visibility controls are supported:
- Date Range: Specific start and end dates/times.
- Seasonal: Recurring date ranges every year.
- Day of Week: Showing/hiding blocks on specific days.
- Time of Day: Showing/hiding blocks during specific hours.
Disabled Controls
The following controls are automatically disabled because they depend on dynamic request data (visitor-specific) which is incompatible with static edge caching:
- Browser / Device
- Cookie
- Location
- Role / User
- Screen Size
- URL Path / Query String
- Referral Source
- WooCommerce / EDD / WP Fusion integration
- ACF fields
Developer Hooks
xwp_block_visibility_edge_cache_purged
Triggered after a post's edge cache has been purged. Useful for adding custom purging logic for other cache layers.
Local Development & Testing
Installation
Running Tests
The project includes a comprehensive test suite using PHPUnit via wp-env.
License
GPLv2 or later.
