Integrates WordPress with Browsersync to trigger events like reload when you edit pages.<\/p>\n\n
The plugin also only triggers a reload for now. If you have requests or ideas for other functionality, get in touch.<\/p>\n\n
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!<\/p>\n\n
By default the plugin will trigger a reload on these actions:<\/p>\n\n
trigger_browsersync_irrelevant_meta_keys<\/code>)<\/li>\n- activated_plugin<\/li>\n
- deactivated_plugin<\/li>\n
- delete_widget<\/li>\n<\/ul>\n\n
you can customise this as well as other Browsersync settings using filters:<\/p>\n\n
add_filter('trigger_browsersync_reload_actions', function($filters) {\n \/\/ Remove a default. Bear in mind that one action you take (e.g. saving a page)\n \/\/ may trigger more than one hook.\n unset($filters['save_post']);\n \/\/ Add your own. The key name lets other filters remove it (like the line above)\n $filters['wp_logout'] = 'wp_logout';\n return $filters;\n});\n<\/code><\/pre>\n\nIgnoring Meta Keys<\/h4>\n\n
Not all meta_key updates (triggered by updated_postmeta<\/code>) have any impact on the front-end functioning of your site. You can customise which meta_key<\/code> values are ignored with the trigger_browsersync_irrelevant_meta_keys<\/code> filter:<\/p>\n\nadd_filter('trigger_browsersync_irrelevant_meta_keys', function($filters) {\n \/\/ Remove a default.\n unset($filters['_edit_lock']);\n \/\/ Add your own. The key name lets other filters remove it (like the line above)\n $filters['_edit_lock'] = '_edit_lock';\n return $filters;\n});\n<\/code><\/pre>\n\nConfiguration with Filters<\/h4>\n\n
The default Browsersync settings will be used (http:\/\/localhost:3000<\/code>) 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.<\/p>\n\nadd_filter('trigger_browsersync_protocol', function(){ return 'https'; } );\nadd_filter('trigger_browsersync_host', function(){ return 'dev.server'; } );\nadd_filter('trigger_browsersync_port', function(){ return '4321'; } );\n<\/code><\/pre>\n\nOr you can specify the whole URL which will cause the others to be ignored, but don't include a trailing slash.<\/p>\n\n
add_filter('trigger_browsersync_url', function(){ return 'http:\/\/localhost:3000'; } );\n<\/code><\/pre>\n\nEnvironmental Configuration<\/h4>\n\n
Since you probably only want Browsersync on your development or staging site, the plugin will do nothing once you activate it it in WordPress.<\/p>\n\n
To make it work, you'll want to create a file to activate it. See Installation for instructions.<\/p>\n\n
Logging Activity<\/h4>\n\n
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.<\/p>\n\n