Facilitated Routines vs Trigger Browsersync

Facilitated Routines brings together useful routines for sites that publish a lot of content. * Technical SEO automation * Identify and remove broken links with one click * Renames the featured image file to the title slug when publishing or updating. * Bulk renames featured images. * Cleans unused media with protection for site logo and icon. * Finds posts without featured image and lists with edit link. * Finds and removes broken images in content and featured images. * Generates WebP versions when possible. * WordPress adjustments with checkboxes: hide version, disable heartbeat, embeds, shortlink, dashicons on front, XML-RPC, feeds, global styles, emojis and more. * Security tab to write .htaccess in uploads, wp-content and wp-includes and remove default readme * Sitemap generation for posts, pages, custom post types, authors and news with automatic updates * Easy edit robots.txt, ads.txt and llms.txt * Track bots and AI access * Find pages without internal or external links

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. Bear in mind that one action you take (e.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. add_filter('trigger_browsersync_protocol', function(){ return 'https'; } ); add_filter('trigger_browsersync_host', function(){ return 'dev.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. To enable logging add this filter to your enable-trigger-browsersync.php file (see Installation); add_filter('trigger_browsersync_log_events', '__return_true');