WP Activity Log 4.2: Support for all date & time formats & other major updates

Featured image *WSAL Update Available*

Today, we’re thrilled to announce the first release of WP Activity Log for 2021, update 4.2.

Your WP Activity Log experience is improving as we work to address bugs and release new features. With this update, the plugin and all its modules have been updated to support any type of date and time format that WordPress supports. We’ve also introduced a couple of new features, and of course improved the coverage of the activity logs.

So, let’s dive right in for a highlight of what’s new & improved in this update.

Support for any type of date and time format

Previously, if you have used the WP Activity Log plugin on a website that has non-western time and date formats, such as Japanese formats, you might have noticed that the date and time were  displayed incorrectly. Most probably you have also encountered problems when trying to generate reports  or adding date filters.

Starting today, this will no longer be a problem. With this update, WP Activity Log supports any type of date and time format that’s supported on WordPress. Therefore, if you can configure it in WordPress, WP Activity Log can read and understand that format.

Keep a log of date & time format changes

To compliment the new feature above, we’ve added a number of new event IDs that can keep a log of changes to the date and time formats, and the timezone settings as well. Here is the list of the new event IDs:

  • ID 6040: Changed the Timezone in the WordPress settings
  • ID 6041: Changed the Date format in the WordPress settings
  • ID 6042: Changed the Time format in the WordPress settings

Improved activity log coverage of WordPress settings, multisite network settings & more

In addition to all the above, we’ve also drastically improved the coverage of the activity logs sensors with a number of new event IDs, focusing on WordPress settings, the application passwords and several other areas. Here’s the list of new event IDs:

New event IDs for changes in posts

  • ID 2129: User added / changed / removed a post’s excerpt
  • ID 2130: User added / changed / removed a post’s featured image

New event IDs for application passwords

  • ID 4025: User added / removed application password from own profile
  • ID 4026: User added / removed application password from another user’s profile
  • ID 4027: User revoked all application passwords from own profile
  • ID 4028: User revoked all application passwords from another user’s profile

New event IDs for changes in WordPress settings

  • ID 6035: Changed the Your homepage displays WordPress setting
  • ID 6036: Changed the homepage in the WordPress setting
  • ID 6037: Changed the posts page in the WordPress settings
  • ID 6044: User changed the WordPress automatic update settings

New event IDs for multisite network settings

  • ID 7007: Changed the setting Allow site administrators to add new users to their site
  • ID 7008: The value of the Site upload space setting was changed
  • ID 7009: The value of the file size allowed in the site upload space setting was changed
  • ID 7010: Changed the list of allowed file types on the network
  • ID 7011: Changed the value of the maximum upload file size network setting

Other new event IDs

  • ID 1010: User requested a password reset.

Refer to the complete list of activity log event IDs for more details about each event ID and what change it represents.

Standardized all activity log messages

In this update we’ve also standardized the text, format and metadata formatting of all the activity log events.

With this change, we aimed to optimize ease of use by further improving the readability of the WordPress activity log, thus making it neater and easier to understand when scrolling through the Activity Log Viewer.

As you can see in the screenshot below, from now on the formatting and order in which the metadata is reported is always the same:

Standardized activity log messages

BREAKING CHANGE: mu-plugin method for custom event IDs no longer supported

Up until this update, users had two different methods available that they could use to add custom event IDs, via a mu-plugin or by developing their own extension. However, from this update onward we will only support one method; adding custom activity log event IDs via an extension.

By dropping the old method, we were able to reduce the plugin’s code base, improve the plugin’s performance, have more manageable code, and most importantly of all, can now focus on this method and further develop it to give the users more options.

Other noteworthy improvements

Like with every other update, we have also included a number of other improvements that are worth mentioning. Below is a highlight:

  • Improved coverage of users’ login / logout / failed logins activity on custom login pages.
  • Consolidated the code that generates the activity log messages.
  • Improved a number of database queries for much better plugin performance.
  • Users who hide the plugin from the plugins page, now get a notification when a plugin update is available.
  • Support for URL rewrites and page names (correct page title reported even if the page is a URL rewrite).
  • Added support for CloudFlare HTTP headers – plugin reports correct IP when website is behind CloudFlare CDN or firewall.

For a complete list of what is new, improved and fixed in this update of the WP Activity Log plugin please refer to the plugin changelog.

Update now for a better WP Activity Log

It goes without saying that this is a big update.

We’ve done major improvements in terms of performance, reliability and activity log coverage. We’ve also improved the user experience by addressing the issues with date and time formats.

To benefit from the best performing and most reliable code, update to WP Activity Log 4.2.

Keep tabs of users & other activity on your WordPress site

Ensure user accountability, ease troubleshooting, get instantly notified of critical changes, generate user activity reports, & improve the security posture of your WordPress website.

Leave a Reply

Your email address will not be published. Required fields are marked *