Stream plugin review and common issues

Check: (1) in Stream → Settings, verify logging is enabled for the action types you expect (e.g., Posts, Settings, Plugins); (2) the free tier has a 72-hour retention window by default — older entries may have been purged; (3) perform a logged action (edit a post, save a setting) and immediately check the Stream log; (4) if WordPress.com connection is required for any feature, verify the connection is established; (5) some server configurations block the database writes Stream uses — check the PHP error log for any Stream-related errors.

Stream’s core logging functions locally in WordPress without requiring the WordPress.com connection. The WordPress.com connection is required for extended retention, Pro features, and some notification integrations. If the setup flow is blocking you: (1) proceed through setup and skip the WordPress.com connection step if available; (2) after setup, Stream should log locally even without a connected WordPress.com account; (3) the 72-hour retention limitation applies without the connection; (4) if a fully self-hosted alternative is preferred, WP Activity Log or Simple History provide equivalent logging without any external service connection.

Stream Slack integration may require the Pro tier through WordPress.com. For free configuration: (1) verify the Slack integration is available in the Stream → Settings → Connectors; (2) create a Slack Incoming Webhook URL in Slack → App → Webhooks; (3) enter the Webhook URL in Stream’s notification settings; (4) configure which event types trigger Slack notifications; (5) test with a monitored admin action to verify the notification arrives in the configured Slack channel.

In the Stream log viewer (Stream → Activity Log), use the filter controls at the top of the log. Filter by User: select the specific username from the user dropdown. Additional filters: Context (which WordPress area — Posts, Settings, Users), Action (Created, Updated, Deleted), and Date Range. Combining User + Date Range shows all actions by a specific user in a time period — useful for auditing a specific editing session or investigating a content change.

Stream’s free version does not include a built-in export feature for the log. Options: (1) use WP-CLI to query and export log entries: wp stream query –author=1 –date_after=”2025-01-01″ –format=csv > log-export.csv; (2) the Stream REST API can be used to programmatically export log data into a spreadsheet or compliance tool; (3) Stream Pro may include export functionality through WordPress.com; (4) for regular compliance exports, schedule a WP-CLI cron job to export logs periodically to a secure location.

WP Activity Log is more comprehensive for audit logging: it covers more third-party plugins, has more configurable notification options without external service dependencies, and its free version has more depth. Stream is better if you prefer its cleaner UI, have existing WordPress.com infrastructure, or need Slack integration with minimal setup. For compliance-focused environments that need comprehensive logging, WP Activity Log’s feature depth and self-hosted architecture are typically preferred. Stream is a solid choice for organizations already in the WordPress.com ecosystem.

Yes — Stream includes a WooCommerce connector that logs WooCommerce-specific events: order status changes (pending → processing → completed), order editing, product changes, coupon modifications, WooCommerce settings changes, and customer account changes. The WooCommerce events appear in the Stream log with WooCommerce-specific context, making it easy to filter for WooCommerce-specific audit entries.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.