Plugin events now include the WordPress user who performed the action (username and role) instead of showing as Anonymous.<\/p>","1.0.8":"
Dashboard URL is now pre-filled on activation. Updated installation instructions.<\/p>","1.0.7":"
Adds subscription status awareness with admin notices for plan limit and payment issues.<\/p>","1.0.6":"
Plugin renamed to "FizteQ Pulse - Monitoring and error tracking" per WordPress.org trademark review. No functional changes.<\/p>","1.0.5":"
Addresses WordPress.org plugin review feedback and adds subscription status awareness with admin notices for plan limit and payment issues.<\/p>","1.0.4":"
Fixes misleading same-version alerts from translation updates and improves cron failure deduplication.<\/p>","1.0.3":"
Fixes monitor config not persisting across cache flushes and adds heartbeat diagnostics to test connection.<\/p>","1.0.2":"
Test connection now triggers an immediate heartbeat so the setup wizard detects your site instantly.<\/p>","1.0.1":"
Fixes connection issue where domain validation failed on server-to-server API requests.<\/p>","1.0.0":"
Initial release. Install, connect to your WPPulse dashboard, and start monitoring.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3500609,"resolution":"128x128","location":"assets","locale":""},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3500609,"resolution":"256x256","location":"assets","locale":""}},"assets_banners":{"banner-772x250.png":{"filename":"banner-772x250.png","revision":3500609,"resolution":"772x250","location":"assets","locale":""}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.7","1.0.8","1.0.9"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3500609,"resolution":"1","location":"assets","locale":""},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3500609,"resolution":"2","location":"assets","locale":""},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3500609,"resolution":"3","location":"assets","locale":""},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3500609,"resolution":"4","location":"assets","locale":""}},"screenshots":{"1":"Plugin settings<\/strong> \u2014 Simple setup: enter your URL and API key, test the connection, and you're done","2":"Dashboard<\/strong> \u2014 All your sites at a glance with health status indicators and recent alerts","3":"Site detail<\/strong> \u2014 Drill into a single site to see its errors, events, and environment","4":"Issue detail<\/strong> \u2014 Full error information with stack trace, request context, and occurrence timeline"},"jetpack_post_was_ever_published":false},"plugin_section":[],"plugin_tags":[5590,29196,5603,4906,151481],"plugin_category":[54],"plugin_contributors":[259628],"plugin_business_model":[],"class_list":["post-294670","plugin","type-plugin","status-publish","hentry","plugin_tags-agency","plugin_tags-error-tracking","plugin_tags-monitoring","plugin_tags-notifications","plugin_tags-site-health","plugin_category-security-and-spam-protection","plugin_contributors-fizteq","plugin_committers-fizteq"],"banners":{"banner":"https:\/\/ps.w.org\/fizteq-pulse\/assets\/banner-772x250.png?rev=3500609","banner_2x":false,"banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/fizteq-pulse\/assets\/icon-128x128.png?rev=3500609","icon_2x":"https:\/\/ps.w.org\/fizteq-pulse\/assets\/icon-256x256.png?rev=3500609","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/fizteq-pulse\/assets\/screenshot-1.png?rev=3500609","caption":"Plugin settings<\/strong> \u2014 Simple setup: enter your URL and API key, test the connection, and you're done"},{"src":"https:\/\/ps.w.org\/fizteq-pulse\/assets\/screenshot-2.png?rev=3500609","caption":"Dashboard<\/strong> \u2014 All your sites at a glance with health status indicators and recent alerts"},{"src":"https:\/\/ps.w.org\/fizteq-pulse\/assets\/screenshot-3.png?rev=3500609","caption":"Site detail<\/strong> \u2014 Drill into a single site to see its errors, events, and environment"},{"src":"https:\/\/ps.w.org\/fizteq-pulse\/assets\/screenshot-4.png?rev=3500609","caption":"Issue detail<\/strong> \u2014 Full error information with stack trace, request context, and occurrence timeline"}],"raw_content":"\n WPPulse is an error tracking and site health monitoring service built specifically for WordPress agencies and freelancers managing multiple client sites.<\/p>\n\n Install this plugin on each site you manage. It reports errors, plugin changes, security events, and more to your WPPulse dashboard<\/a> \u2014 giving you a single overview of every site's health.<\/p>\n\n The plugin runs silently in the background. If the connection to WPPulse is temporarily unavailable, events are queued locally and sent automatically when the connection is restored.<\/p>\n\n If you manage 10, 50, or 100 client sites, WPPulse gives you one place to see which sites have errors, which have pending updates, and which need attention \u2014 before your clients call you.<\/p>\n\n This plugin requires a WPPulse<\/a> account and sends data to the WPPulse API hosted at Data transmitted to WPPulse:<\/strong><\/p>\n\n Sensitive data filtering:<\/strong> Passwords, tokens, API keys, emails, names, addresses, credit card fields, and 34+ other sensitive field types are automatically replaced with Service links:<\/strong><\/p>\n\n WPPulse is operated by FizteQ Solutions SRL (Romania, EU). All data is processed and stored on servers located in Bucharest, Romania.<\/p>\n\n\n After activation, the plugin needs two things:<\/p>\n\n Once connected, monitors are controlled from the WPPulse dashboard. Use the Sync Config<\/strong> button on the settings page to pull the latest configuration.<\/p>\n\n By default, the plugin uses WP-Cron for scheduling. If your site has low traffic or you prefer more reliable timing, switch to System Cron<\/strong> mode in the settings and add the provided crontab command to your server.<\/p>\n\n\n Yes. The plugin sends monitoring data to your WPPulse dashboard at wp-pulse.app<\/a>. You can sign up for a free account to get started.<\/p><\/dd>\n The plugin sends error details (message, file, stack trace), plugin change events, and environment information (PHP version, WordPress version, active theme). Sensitive fields like passwords, tokens, emails, and credit card numbers are automatically filtered and never transmitted.<\/p><\/dd>\n No. The plugin hooks into WordPress events and only runs when something happens (an error, a plugin change, etc.). It adds no frontend JavaScript, no database tables, and no queries to page loads. API calls use a 10-second timeout so they never block your site.<\/p><\/dd>\n Events are automatically queued locally (up to 50 events) and retried with exponential backoff. Once the connection is restored, all queued events are sent in a single batch. No data is lost.<\/p><\/dd>\n Yes. Monitors are toggled from the WPPulse dashboard. After making changes there, click Sync Config<\/strong> in the plugin settings to pull the latest configuration.<\/p><\/dd>\n Yes. Go to the WPPulse settings page and add field names under Additional Filtered Fields<\/strong> (one per line). These are merged with the 34 built-in filtered fields. You can also use the WPPulse is built by an EU company (FizteQ Solutions SRL, Romania) and hosted entirely within the EU. Sensitive data is filtered before transmission, and the plugin does not use cookies or track visitors. See our privacy policy<\/a> and DPA<\/a> for full details.<\/p><\/dd>\n The plugin detects WP-CLI and command-line contexts. Error monitoring works in CLI mode, but request-specific data (URL, headers, POST body) is not captured since there is no HTTP request.<\/p><\/dd>\n Yes. The plugin reports the multisite status as part of the environment data. Install and configure it on each site in the network where you want monitoring.<\/p><\/dd>\n\n<\/dl>\n\n\nWhat it monitors<\/h4>\n\n
\n
Why WPPulse?<\/h4>\n\n
\n
How it works<\/h4>\n\n
\n
Built for agencies<\/h4>\n\n
External Service<\/h4>\n\n
wp-pulse.app<\/code>. No data is transmitted until you configure the plugin with your API key.<\/strong> The plugin does not contact any external server until you explicitly connect it.<\/p>\n\n\n
[Filtered]<\/code> before transmission. You can add custom fields on the settings page.<\/p>\n\n\n
From the WordPress Plugin Directory<\/h4>\n\n
\n
Manual Installation<\/h4>\n\n
\n
Configuration<\/h4>\n\n
\n
https:\/\/wp-pulse.app<\/code>. No change needed unless directed otherwise.<\/li>\nSystem Cron (optional)<\/h4>\n\n
\n
Do I need a WPPulse account?<\/h3><\/dt>\n
What data does the plugin send?<\/h3><\/dt>\n
Does it slow down my site?<\/h3><\/dt>\n
What happens if the connection to WPPulse is down?<\/h3><\/dt>\n
Can I control which monitors are active?<\/h3><\/dt>\n
Can I add custom fields to the privacy filter?<\/h3><\/dt>\n
wppulse_sensitive_body_keys<\/code> and wppulse_sensitive_header_keys<\/code> filters in code.<\/p><\/dd>\nIs it GDPR-compliant?<\/h3><\/dt>\n
Does it work with WP-CLI?<\/h3><\/dt>\n
Does it work on multisite?<\/h3><\/dt>\n
1.0.9<\/h4>\n\n
\n
1.0.8<\/h4>\n\n
\n
1.0.7<\/h4>\n\n
\n
1.0.6<\/h4>\n\n
\n
1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n