Skip to content

Releases: Pierre-Lannoy/wp-decalog

Version 3.7.0

24 Feb 11:19
60d328a
Compare
Choose a tag to compare

The developments of PerfOps One suite, of which this plugin is a part, is now sponsored by Hosterra.

Hosterra is a web hosting company I founded in late 2022 whose purpose is to propose web services operating in a European data center that is water and energy efficient and ensures a first step towards GDPR compliance.

This sponsoring is a way to keep PerfOps One plugins suite free, open source and independent.

Added

  • Compatibility with WordPress 6.2.
  • It's now possible to define failsafe loggers right in the wp-config.php file (thanks to Jan Thiel).
  • Jaeger and Zipkin traces loggers now support SpanKind feature (thanks to YR Chen).
  • It's now possible to add a custom service name for tracers using Jaeger thrift over HTTP format.
  • New option to not report non-existent metrics.

Changed

  • Upgraded Monolog library from version 2.8.0 to version 2.9.1.
  • Improved browser logger for events.
  • Fixed tags are now passed as global tags when tracing with Jaeger logger (thanks to YR Chen).
  • Great resources improvement for WordPress installs where there's no monitoring needed (thanks to Jan Thiel).
  • Improved loading by removing unneeded jQuery references in public rendering (thanks to Kishorchand).

Fixed

  • Some weird processes can try to delete null attachments, and it produces PHP warning (thanks to Axel Ducoron).
  • In some edge-cases, detecting IP may produce PHP deprecation warnings (thanks to YR Chen).
  • Some strings should not be translatable (thanks to Laurent Millet).

Version 3.6.3

01 Dec 15:45
995b419
Compare
Choose a tag to compare

Changed

  • [WP-CLI] Now, metrics are not sent by default when using command line (thanks to Jan Thiel).

Fixed

  • DecaLog may produce PHP errors with new versions of WP Activity Log (thanks to Axel Ducoron).

Version 3.6.2

24 Oct 13:32
8f9686c
Compare
Choose a tag to compare

Fixed

  • [WP-CLI] Enabling/disabling listeners is not working properly (thanks to Alex Mozhey).
  • [WP-CLI] Some messages have inconsistent upper/lower casing or success/warning prefix.

Version 3.6.1

11 Oct 12:23
d7d1c56
Compare
Choose a tag to compare

Changed

  • [WP-CLI] A warning is now triggered when an outdated version of WP-CLI is detected.

Fixed

  • [WP-CLI] With outdated versions of WP-CLI, a PHP uncaught exception is thrown (thanks to Jan Thiel).
  • Unable to use Plesk WordPress toolkit when Plesk WP-CLI is not up to date.

Version 3.6.0

06 Oct 06:30
3b1d321
Compare
Choose a tag to compare

Added

  • Compatibility with WordPress 6.1.
  • Compatibility with PHP 8.2.
  • DecaLog can now warn about slow SQL queries - see "options" tab in plugin settings.
  • It's now possible to collect SQL queries in traces (based on a suggestion from evoicefire) - see "options" tab in plugin settings.
  • DecaLog now collects installed/updatable themes metrics (based on a suggestion from deltaecho07).
  • It's now possible to add custom tags to each span in traces for Datadog, Grafana, Jaeger, NewRelic, Tempo and Zipkin loggers (based on a suggestion from YR Chen).
  • DecaLog can now log all events triggered by WooCommerce status tools.
  • [WPCLI] DecaLog can now log all events triggered in interactive wp-cli sessions.

Changed

  • Upgraded Monolog library from version 2.6.0 to version 2.8.0.
  • Improved and optimized launch of listeners.
  • [WPCLI] The command wp log listener list --detail=full now returns launch step too.
  • [WPCLI] The results of wp log commands are now prefixed by the product name.
  • Improved detection, loading and listening of WooCommerce.

Fixed

  • Live console with PHP 8 may be broken (thanks to stuffeh).
  • In some rare conditions, Rotating Files logger may wrongly compute the file path or name.
  • The trace span for logger purges may be attached to a wrong parent.
  • Some listeners may not detect they need to be launched.

Version 3.5.1

12 May 08:43
Compare
Choose a tag to compare

Changed

  • Upgraded Monolog library from version 2.5.0 to version 2.6.0.
  • Experimental: Elasticsearch V7-only support is now upgraded to V7/V8.

Fixed

  • A PHP error may be triggered when adding a new role to a user (thanks to Axel Ducoron).

Version 3.5.0

22 Apr 13:11
Compare
Choose a tag to compare

Added

  • Compatibility with WordPress 6.0.
  • New events when adding or removing a user role.
  • A new filter allows now to exclude specific metrics for specific loggers (based on a suggestion from Jan Thiel).
  • New icons in loggers list to show activated privacy options.

Changed

  • Messages for database version downgrade/upgrade are much more precise.
  • Upgraded Monolog library from version 2.3.4 to version 2.5.0.
  • Site Health page now presents a much more realistic test about object caching.
  • Improved favicon handling for new Google API specifications.
  • Improved compatibility with Members plugin.
  • Improved errors handling when creating incomplete loggers.

Fixed

  • Events about roles changes are wrongly reported (thanks to Valérie Galassi).
  • The APCu test in option page may fail (thanks to Renaud Pacouil).
  • PHP 8.1 compatibility changes have introduced side effect on HTML entities encoding (thanks to Jan Thiel).
  • Callstack items are wrongly named (and ordered) in Loki logger.

Version 3.4.1

17 Jan 15:11
Compare
Choose a tag to compare

Fixed

  • The Site Health page may launch deprecated tests.

Version 3.4.0

17 Jan 07:05
Compare
Choose a tag to compare

Added

  • Compatibility with PHP 8.1.
  • New logger to send events to Spatie Ray app.
  • New listener for Redis Object Cache (thanks to Till Krüss for the help).
  • Logo for bbPress in events list and viewer.
  • Logo for MysQL DB in events list and viewer.
  • Logo for MariaDB DB in events list and viewer.
  • Logo for PostgreSQL DB in events list and viewer.
  • Logo for Percona DB in events list and viewer.

Changed

  • Html entities are now substituted for better readability in New Relic NR-Logs.
  • Refactored cache mechanisms to fully support Redis and Memcached.
  • Improved layout for WordPress traces viewer.
  • Better events messages for lost password form submission.
  • Improved APCu storage for loggers.
  • Reduction of the events' level for the wp_die ajax handler because it is not used consistently in the WordPress core (thanks to Jan Thiel for the suggestion).
  • Updated DecaLog SDK from version 2.0.0 to version 2.0.2.
  • Updated PerfOps One library from 2.2.1 to 2.2.2.
  • Improved bubbles display when width is less than 500px (thanks to Pat Ol).
  • Updated headers for drop-in and mu-plugin files.

Fixed

  • The console menu may display an empty screen (thanks to Renaud Pacouil).
  • There’s a PHP error when reaching the checkout page of woocommerce with WP Activity Log activated (thanks to freshuk).
  • Object caching method may be wrongly detected in Site Health status (thanks to freshuk).
  • The "WordPress metrics collation" span is attached to the wrong parent.
  • There may be name collisions with internal APCu cache.

Version 3.3.0

07 Dec 00:05
Compare
Choose a tag to compare

Added

  • Compatibility with WordPress 5.9.
  • New listener for Cavalcade (thanks to Jan Thiel for the suggestion).
  • Internal viewers for events and traces display instance name in details screens.
  • New button in settings to install recommended plugins.
  • There's now decalog_events_list_actions_for_event, decalog_events_list_actions_for_source, decalog_events_list_actions_for_time, decalog_events_list_actions_for_site, decalog_events_list_actions_for_user and decalog_events_list_actions_for_ip filters to add custom actions to events list view (thanks to Julio Potier for the suggestion).
  • There's now decalog_event_view_actions_for_event, decalog_event_view_actions_for_content, decalog_event_view_actions_for_php, decalog_event_view_actions_for_device, decalog_event_view_actions_for_wp, decalog_event_view_actions_for_http, decalog_event_view_actions_for_wpbacktrace and decalog_event_view_actions_for_phpbacktrace filters to add custom actions to single event viewer (thanks to Julio Potier for the suggestion).
  • There's now decalog_traces_list_actions_for_trace, decalog_traces_list_actions_for_duration, decalog_traces_list_actions_for_time, decalog_traces_list_actions_for_site and decalog_traces_list_actions_for_user filters to add custom actions to traces list view (thanks to Julio Potier for the suggestion).
  • There's no decalog_trace_view_actions_for_trace and decalog_trace_view_actions_for_wp filters to add custom actions to single trace viewer (thanks to Julio Potier for the suggestion).
  • In all internal viewers, country flags have the name of the country as alternative text.
  • Adds OPcache compatibility for cluster/nodes environments - including Kubernetes.
  • Adds, for consistency check, PHP versions and modules compatibility for cluster/nodes environments - including Kubernetes.
  • Logo for WP-CLI in events list and viewer.

Changed

  • Improved update process on high-traffic sites to avoid concurrent resources accesses.
  • Better publishing frequency for metrics.
  • Instance name is now propagated for all events and traces loggers (in context), even if it is not required by the corresponding service.
  • Upgraded Monolog library from version 2.2.0 to version 2.3.4.
  • Improved default values for "InfluxDB 2" logger.
  • Improved way to detect instance name.
  • Updated labels and links in plugins page.

Fixed

  • The loggers list displays wrong types for "crash analytics" and "alerting".
  • OPcache events logging is wrong on clustered environments (thanks to Jan Thiel).
  • The warning message about "debugging" class logger is not always displayed when it should be.
  • The default index names for Elasticsearch and Elastic Cloud are inconsistent.
  • The HTTP 204 error code sometimes returned by a Loki instance is wrongly interpreted.
  • Name collisions or PHP errors can occur with plugins using outdated versions of Monolog library (like BackWPup).
  • Clearing events by hook reference may be not logged (thanks to Jan Thiel).
  • Unscheduling events may be not logged.
  • Logging an event with a message containing SQL select may be wrongly truncated in the where clause.
  • In some edge cases, logging plugins updates may not work correctly.
  • WordPress event viewer try to display request referrer even if it doesn't exist.
  • Country translation with i18n module may be wrong.
  • There's typos in CHANGELOG.md.