WordPress plugin intelligence profile

Trigger Browsersync

Integrates WordPress with Browsersync to trigger events like Reload when you edit pages and settings.

WP PlugIndex snapshot

Current directory snapshot

Tested up to not listed
Current version0.8.6
WordPress coverageTested up to not listed
Minimum stackWP 3.0.1 · PHP —
Directory statusactive
Last directory update23 Jun 20224y ago
Active installations10Adoption metric — not a quality score
WordPress.org rating4.7 / 5 from 3 ratings
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records Trigger Browsersync version 0.8.6 as active, updated 4y ago and without a listed Tested up to version.

Overview

About this plugin

Integrates WordPress with Browsersync to trigger events like reload when you edit pages.

The plugin also only triggers a reload for now. If you have requests or ideas for other functionality, get in touch.

Since you (should) disable this plugin on production sites, the WordPress stats won’t be reliable – if you find the plugin useful I’d really appreciate it if you’d let me know with a quick email or message!

Triggers

By default the plugin will trigger a reload on these actions:

  • save_post – Editing posts/pages/custom posts etc
  • added_option – Changing settings
  • attachment_updated – Editing media fields (caption etc)
  • updated_postmeta – Covers many things, particularly regenerating media thumbnails. Some meta_fields are ignored (see trigger_browsersync_irrelevant_meta_keys )
  • activated_plugin
  • deactivated_plugin
  • delete_widget

you can customise this as well as other Browsersync settings using filters:

add_filter('trigger_browsersync_reload_actions', function($filters) { // Remove a default. g. saving a page) // may trigger more than one hook.

unset($filters['save_post']); // Add your own. The key name lets other filters remove it (like the line above) $filters['wp_logout'] = 'wp_logout'; return $filters; });

Ignoring Meta Keys

Not all meta_key updates (triggered by updated_postmeta ) have any impact on the front-end functioning of your site. You can customise which meta_key values are ignored with the trigger_browsersync_irrelevant_meta_keys filter:

add_filter('trigger_browsersync_irrelevant_meta_keys', function($filters) { // Remove a default. unset($filters['_edit_lock']); // Add your own. The key name lets other filters remove it (like the line above) $filters['_edit_lock'] = '_edit_lock'; return $filters; });

Configuration with Filters

The default Browsersync settings will be used ( http://localhost:3000 ) but you can use filters to change them. The filters are used every time the trigger is activated so you don’t need to set them before instanciating the class.

server'; } ); add_filter('trigger_browsersync_port', function(){ return '4321'; } );

Or you can specify the whole URL which will cause the others to be ignored, but don’t include a trailing slash.

add_filter('trigger_browsersync_url', function(){ return 'http://localhost:3000'; } );

Environmental Configuration

Since you probably only want Browsersync on your development or staging site, the plugin will do nothing once you activate it it in WordPress.

To make it work, you’ll want to create a file to activate it. See Installation for instructions.

Logging Activity

Trigger Browsersync can log events to the WordPress log – this is especially useful for development on the plugin when you want to add or exclude a new event from triggering an action.

php file (see Installation);

add_filter('trigger_browsersync_log_events', '__return_true');

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • automation
  • browsersync
  • dev
  • refresh
Compatibility & maintenance

Compatibility & maintenance

Tested up to not listed

WordPress.org does not currently provide a Tested up to version that WP PlugIndex can compare with WordPress 7.1.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up toNot listed
Minimum requirementsWordPress 3.0.1 · PHP not listed
Update activity23 Jun 20224y ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.