logtivity / readme.txt

readme.txt in Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity 3.3.10, at readme.txt

561 lines 24.8 KB

Raw Download Zip

1	=== Activity Logs, User Activity Tracking, Multisite Activity Log from Logtivity ===
2
3	Contributors: logtivity, stevejburge
4	Tags: activity log, user activity, audit log, event monitoring, logs
5	Requires at least: 6.6
6	Tested up to: 7.1
7	Stable tag: 3.3.10
8	Requires PHP: 7.4
9	License: GPLv2 or later
10	License URI: https://www.gnu.org/licenses/gpl-2.0.html
11
12	Logtivity is the activity log service for WordPress admins. Track user activity and site events across every WordPress site you maintain.
13
14	== Description ==
15
16	<strong>When you set up Logtivity to monitor your WordPress sites, you can relax. We track everything that happens on the sites you maintain, and Logtivity also sends you alerts for important events!</strong>
17
18	Logtivity is a unified platform that tracks activity across all your WordPress sites. We record everything that happens, and then send you alerts for important events! You can install Logtivity’s plugin and then use our service to keep a close eye on everything that happens on your sites.
19
20	If you work with clients, they never have to know that you’re using Logtivity. You can either show a white label version of the activity logs, or you can hide Logtivity entirely.
21
22	### WordPress Activity Logs ###
23
24	Logtivity provides the best activity logs for WordPress agencies. You can record all the user activity on your clients' sites. Then you can use the activity log data to send notifications to email or Slack. Plus, you can easily search and export the information. And you can turn the activity log data into beautiful, useful charts.
25
26	If you have customers on your clients' WordPress site, you’ll find Logtivity to be invaluable. Because Logtivity records all the important activity, you can see real customer journeys across the WordPress sites. This can be incredibly helpful for customer support: the activity log will show exactly what a user has done on your site.
27
28	To get started, simply install the Logtivity plugin and then connect your site to [Logtivity](https://logtivity.io). You’ll immediately start to see the results.
29
30	[Click here to see more about activity logs](https://logtivity.io/features/event-tracking/).
31
32	### Instant Alerts for WordPress Sites ###
33
34	With Logtivity alerts, you can keep an eye on all your clients’ sites. You can set up flexible alerts for single sites or all your clients’ sites.
35
36	These notifications can go directly to your email inbox or to Slack channels.
37
38	If you have many sites, you can set up global alerts. For example, even if you have 100 sites, you only need to configure the alert once.
39
40	One Logtivity customer chooses to receive an email every time a plugin or theme is updated. Another WordPress agency has a Slack alert for every time an administrator logs in.
41
42	[Click here to see more about alerts](https://logtivity.io/features/instant-alerts/).
43
44	### Charts from Your Activity Logs
45
46	Logtivity is a WordPress activity log with a big difference. You can track all the activity on your clients’ sites, and you can also turn that information into beautiful and useful charts.
47
48	Displaying data in charts gives you a helpful and organized overview of your clients’ key metrics. You can use these charts to show logins, purchases, subscriptions, cancellations, downloads, or any other key events. If it happens in WordPress site, Logtivity can turn it into a bar chart or a line chart.
49
50	You can also customize the date range for charts. Your charts have advanced date ranges, so you can zoom in to view any time period.
51
52	[Click here to see more about charts](https://logtivity.io/features/customisable-reporting-dashboard/).
53
54	### Large Activity Log Exports ###
55
56	Normal WordPress activity plugins can not handle large amounts of data.
57
58	Logtivity is able to handle exports for even the biggest WordPress sites! If your clients’ site uses Logtivity, you can export millions and millions of logs.
59
60	In the image next to this text, you can see over a dozen CSV files. Each of these files is a Logtivity export that contains 100,000 logs. This export has 13 files, so it’s over 1,300,000 million logs in total.
61
62	Logtivity is the activity log solution for large WordPress sites!
63
64	[Click here to see more about log exports](https://logtivity.io/features/large-exports/).
65
66	### View Activity Logs Inside WordPress ###
67
68	Logtivity has a central dashboard where you can see the logs for all your clients’ WordPress sites.
69
70	Plus, you and your clients can also view and search the logs from inside each WordPress site.
71
72	The image on this screen shows what you’ll see inside WordPress after installing the Logtivity plugin.
73
74	All of the activity log data is visible and searchable in the WordPress admin area. And if you want more information on any specific log entry, you can click the “View” button next to each log.
75
76	[Click here to see more about the WordPress integration](https://logtivity.io/features/easy-wordpress-integration/).
77
78	### Logtivity has a White Label Mode for Agencies ###
79
80	The most frequent users of Logtivity are WordPress agencies and maintenance services who want to keep an eye on lots of websites.
81
82	Agencies and maintenance services often white label the services they use, and so we’ve made this possible for Logtivity also.
83
84	There’s a “White Label Mode” in Logtivity, so you can provide the smoothest experience possible for clients. You can remove all the references to Logtivity from the WordPress admin area.
85
86	[Click here to see more about the White Label mode](https://logtivity.io/features/white-label/).
87
88	### Join Logtivity and Start Your Monitoring ###
89
90	> <strong>Logtivity is a SaaS service</strong><br />
91	> You will need to create a Logtivity account to store your activity logs and create alerts. <a href="https://app.logtivity.io/register" rel="friend" title="Logtivity">Click here to get started with Logtivity!</a>
92
93	== Screenshots ==
94
95	1. The best activity log for WordPress sites
96	2. See your clients' site logs inside WordPress
97	3. Get alerts for all key WordPress events
98	4. Create charts from your activity logs
99	5. Export large data files from your activity logs
100
101	== Installation ==
102	#### From your WordPress dashboard
103	Visit 'Plugins > Add New'
104	Search for 'logtivity'
105	Activate Logtivity from your Plugins page.
106
107	#### From WordPress.org
108	Download logtivity.
109	Upload the 'logtivity' directory to your '/wp-content/plugins/' directory, either through the UI (Plugins > Add new) or via SFTP or example.
110	Activate Logtivity from your Plugins page.
111
112	#### Once Activated
113	Visit 'Tools > Logtivity' to view the settings page.
114	Enter your Logtivity API Key, configure your options and your event monitoring will start!
115
116	== Frequently Asked Questions ==
117
118	= What plugins do Logtivity activity logs support? =
119
120	Logtivity has some support for most WordPress plugins. If the plugin uses post types, we record when most post types are updated, created or deleted.
121
122	We currently have integrations with Easy Digital Downloads, Memberpress and Download Monitor. These integrations allow you to track things like Memberpress subscription creations, changes, or cancellations and also track when files are downloaded through Download Monitor.
123
124	We are working on more detailed event monitor support for some key plugins, including eCommerce plugins such as WooCommerce and Easy Digital Downloads.
125
126	Please contact us for specific details on any plugin that you are using.
127
128	= Can I log custom events? =
129
130	Yes, our user activity tracking plugin provides a flexible API to log and store custom events with Logtivity. An example of logging a custom event is below. This example is recording information from Stripe.com for a customer:
131
132	`
133	Logtivity::log()
134	->setAction('My Custom Action')
135	->addMeta('Meta Label', $meta)
136	->addMeta('Another Meta label', $someOtherMeta)
137	->addUserMeta('Stripe Customer ID', $stripeCustomerId)
138	->send();
139	`
140
141	[Click here to see more about custom activity logs](https://logtivity.io/docs/custom-events/).
142
143	= What user activities does Logtivity record? =
144
145	Logtivity records all core WordPress actions. In addition to support for the WordPress core, Logtivity records events for many plugins and themes.
146
147	[Click here to see more about what Logtivity records](https://logtivity.io/docs/what-logs/).
148
149	= Does Logtivity have activity logs for WordPress user logins? =
150
151	It’s important to have an activity log on your WordPress site. You need user tracking because you need to know many people are visiting, making purchases, and logging in to your site. Yes, you can track visitors with Google Analytics, and you can track purchases with your payment gateway, but it’s harder to track WordPress-specific information such as log ins. Using Logtivity, you can get an overview of who is logging in to your site, and how many people are logging in every day.
152
153	If Logtivity is active on your site, you can go to the “Logs” screen and search for all the “User Logged in” events. You can use the search boxes to drill down for more specific user tracking information. For example, you can use the “Context” box to search for a particular user role. You can use this to search for all "Administrator" logins or all "Editor" logins.
154
155	You can also use the search option as a security log and look for nefarious patterns in the audit logs. For example, you can search by IP address to see if one person is using multiple logins. Or you can search by username to see if one account is being shared by different people.
156
157	[Click here to see more about activity logs for user logins](https://logtivity.io/track-user-logins-wordpress/).
158
159	= Is Logtivity a GDPR-compliant activity log? =
160
161	Yes, Logtivity gives you complete control over the user tracking information recorded in the audit logs. You can choose your GDPR settings. You can decide to only log a profile link, user ID, username, IP address, or nothing at all.
162
163	* Inside your WordPress site, go to “Tools” and then “Logtivity”.
164	* You can uncheck the boxes on this screen to stop Logtivity from recording personal user trackking data.
165
166	Here's an overview of the key GDPR-compliant settings:
167
168	* Store User ID: If you check this box, when logging an action, we will include the users User ID in the logged action.
169	* Store Users Profile Link: If you check this box, when logging an action, we will include the users profile link in the logged action.
170	* Store Users Username: If you check this box, when logging an action, we will include the users username in the logged action.
171	* Store Users IP Address: If you check this box, when logging an action, we will include the users IP address in the logged action.
172
173	[Click here for more about the GDPR and activity logs](https://logtivity.io/docs/personal-data/).
174
175	= Can I disable all activity logs and only store custom logs? =
176
177	Yes! You can easily disable all event monitoring that this plugin provides so that you can only store the user tracking audit logs that matter to you manually. You can also disable built in logs on an individual basis via the filter example below:
178
179	`
180	add_action('wp_logtivity_instance', function($Logtivity_Logger) {
181
182	if (strpos($Logtivity_Logger->action, 'Page was updated') !== false) {
183	$Logtivity_Logger->stop();
184	}
185
186	});
187	`
188	[Click here for more about disabling activity logs](https://logtivity.io/docs/select-events/).
189
190	= Can I rename the activity logs? =
191
192	Yes, it is possible to rename the events that are stored in Logtivity’s audit logs. For example, you can add this code to your site’s functions.php file. This code will result in an event “File Downloaded” being logged as “Resource Downloaded”.
193
194	`
195	add_action('wp_logtivity_instance', function($Logtivity_Logger) {
196	if (strpos($Logtivity_Logger->action, 'File Downloaded') !== false) {
197	$Logtivity_Logger->setAction('Resource Downloaded');
198	}
199	});
200	`
201	[Click here for more about renaming activity logs](https://logtivity.io/docs/rename-events/).
202
203	= Can I export the activity logs? =
204
205	Yes, Logtivity makes it easy to export your user activity data into a CSV file. Follow these steps for your audit log export:
206
207	* To get started, visit the “Logs” area inside [https://app.logtivity.io](https://app.logtivity.io).
208	* You can either search for a specific result, or you can use export all your event monitoring logs.
209	* When you see the logs you want to export, click “Actions” and then “Export to CSV”.
210	* Logtivity will show you the following message: “Export scheduled”.
211	* When the export file is ready, Logtivity will send you an email with a download link to the CSV file.
212
213	[Click here to see more about exporting activity logs](https://logtivity.io/docs/export-data/).
214
215	= Can I send activity log notifications to Slack channels? =
216
217	Yes, You can use Logtivity to send alerts to your Slack account. Follow these steps to connect Logtivity to a channel in your Slack account:
218
219	* In the Logtivity app, click on the name of your team.
220	* Click "Alert Channels".
221	* Check the "Slack" box.
222	* Enter the name of your Slack channel.
223	* Click the "Add Channel" button.
224	* You will now see a screen where Slack asks you to allow Logtivity access. Click the "Allow" button.
225	* You will be redirected back to the Logtivity app.
226	* Any alert for this Logtivity team will now be sent to your Slack account.
227
228	[Click here to see more about activity logs and Slack notifications](https://logtivity.io/docs/slack/).
229
230	= How does Logitivity compare to other activity log plugins? =
231
232	There are some good WordPress activity log plugins including WP Activity Log, WP User Activity, User Activity Log, Activity Log, WP Cerber, Jetpack activity log, User Activity Tracking and Log, WP Stream, Simple History, Aryo Activity Log and more.
233
234	Logtivity is different from those plugins in several important ways:
235
236	* It is a hosted service, so you don't have to store all the data in your site's database. This can really slow down your site! Logtivity allows you to store much more data, and export it more easily.
237	* Deeper integration with key plugins such as Easy Digital Downloads and MemberPress.
238	* Visualize your data with Logtivity's charts.
239
240	= How does Logitivity compare to other management services? =
241
242	There are some hosted solutions such as ManageWP, MainWP, WPMU Dev, Jetpack, WP Umbrella, WP Remote, InfiniteWP, CMS Commander, iControlWP and more. Logtivity is different because it is focused on more advanced tools for agencies. With Logtivity you have very detailed activity logs. We're committed to building expert levels tools to help WordPress professionals.
243
244	= Logitivity branding information =
245
246	Logtivity is the official brandname. When writing about this activity plugin, please make sure to uppercase the L:
247
248	* Logtivity (correct)
249	* logtivity (incorrect)
250	* Logtivity.io (incorrect)
251	* Log tivity, loggtivity, logg tivity (all incorrect)
252
253	== Changelog ==
254
255	= 3.3.10 07 Oct 2026 ==
256	* Improved debugging option
257	* Send inventory on all plugin/theme changes
258
259	= 3.3.9 22 Sep 2026 =
260	* Update Code Snippet Logger for newest version
261	* Stricter test for production/development configurations
262	* Improved plugin status logging
263	* Various security/accessibility fixes
264
265	= 3.3.8 02 Sep 2026 =
266	* Security updates / sanitize all inputs
267	* Never log draft posts
268	* Always use user role for contexts
269	* Display notice if not using production application.
270	* Remove error logging/capture
271	* Accessibility improvements
272
273	= 3.3.7 15 Apr 2026 =
274	* Catch null auth header on API call
275	* Catch bad auth header on API call
276	* Allow null post ID for getting titles
277
278	= 3.3.6 15 Dec 2025 =
279	* Include plugin version number in api responses
280	* Stricter consistency with action texts
281	* Fix: Exceptions were never being logged
282
283	= 3.3.5 25 Nov 2025 =
284	* Pay attention to filtering out separate post meta logs
285
286	= 3.3.4 10 Nov 2025 =
287	* Fix: "Nesting Level" error on Woo Commerce option updates
288
289	= 3.3.3 - 03 Nov 2025 =
290	* Display log times using General Settings
291	* Fix: Bulk user updates can cause WSOD
292	* Fix: WSOD with more complicated arrays
293	* Fix: Sometimes post id doesn't exist
294	* Fix: EDD Logger unable to handle empty customer name
295	* Fix: Handle no previous post information
296
297	= 3.3.2 - 22 Oct 2025 =
298	* Remove separate post-meta logger
299	* Consolidate all post logging to single entries
300	* Provide more consistent display of field keys and values
301	* Prevent permissions error on activation with leftover settings
302	* FIX: WSOD on older versions of WordPress
303
304	= 3.3.1 - 07 Oct 2025 =
305	* Fix WSOD on some cached sites
306
307	= 3.3.0 - 25 Sep 2025 =
308	* Provide more detailed information for term updates
309	* Provide more detailed information for user updates
310
311	= 3.2.1 - 02 Sep 2025 =
312	* Fix: issues with disable log string matching
313	* Fix: Improve domain matching for API token security
314	* Update: Allow send method to return response
315	* Update: Send additional data from options endpoint
316	* Update: Link to Team API
317	* Update: Improve error message retrieval from latest response
318	* Fix: Disabled log string matching
319	* Fix: Improve domain checks on API Endpoints
320	* Update: Always include occurred_at in request properties
321
322	= 3.2.0 - 28 Jul 2025 =
323	* Add JSON Web Token halper class
324	* Add REST api listener
325	* Retrieve more detailed error information on connection fails
326	* Normalize response data
327	* Fix automatic settings checkin
328	* Prevent disconnect on timeout errors
329
330	= 3.1.12 - 4 Jun 2025 =
331	* New: Register Site with Team API
332	* Update: Adjust screen styles and messaging
333
334	= 3.1.11 - 15 May 2025 =
335	* Update: Improvements to welcome messaging
336	* Update: Redirect on activate
337	* Update: WordPress version compatibility
338
339	= 3.1.10 - 8 May 2025 =
340	* Fix: error handling conflict with other error handlers
341	* Fix: Allow passing null to method
342	* Fix: Allow optional second argument
343	* Check in periodically when in failed/paused state
344	* Add codeception testing suite
345
346	= 3.1.9 - 14 Apr 14 2025 =
347	* Fix fatal error on new installs
348
349	= 3.1.8 - 14 Apr 2025=
350	* Add option to verify site url with the app
351
352	= 3.1.7 - 27 Mar 2025 =
353	* Fix: Check for installed custom capabilities
354	* Improved input sanitization
355
356	= 3.1.6 - 6 Mar 2025 =
357	* Update: Automatically check and ensure capabilities exist
358
359	= 3.1.5 - 25 Feb 2025 =
360	* Add: new capabilities - 'view logs', 'view log settings'
361
362	= 3.1.4 - 9 Jan 2025 =
363	* Fix: Deprecation warning, #50
364	* Fix: Unable to uncheck settings
365
366	= 3.1.3 - 21 Nov 2024 =
367	* Fix: Grammar, #46
368	* Change: Language for disabled logs, #47
369	* Change: Checkboxes checked by default, #48
370	* Fix: Close potential security issue
371
372	= 3.1.2 - 30 Sep 2024 =
373	* Backout to v3.0.2 due to breaking changes
374
375	= 3.1.1 – 12 Sep 2024 =
376	* Fix: Updating failed. The response is not a valid JSON response, #38;
377
378	= 3.1.0 – 11 Sep 2024 =
379	* Change: Update plugin description, #31;
380	* Change: Enable the settings by default, #12;
381	* Change: Welcome message, #11;
382	* Change: Hide the "Disable Individual Logs" box if is empty, #22;
383	* Change: Text updates, #23, #33;
384	* Change: Check if api exists in order to hide the free trial sidebar, #36;
385	* Change: Go fullwidth when API exists
386	* Fix: Text is not translatable, #24;
387	* Fix: Redesign the modal for log details, #19;
388	* Fix: Redirect users to Settings page on plugin activation, #8;
389	* Standards updates/code refresh
390
391	= 3.0.2 – 19 Jun 2024 =
392	* Fix incompatibility with Code Snippets plugin
393	* Design changes
394
395	= 3.0.1 – 6 Jan 2024=
396	* Change Logtivity settings URL in white label mode.
397	* Fix User Logged In event firing when external system logs in for backups etc.
398
399	= 3.0.0 – 11 Nov 2023 =
400	* Add site health features.
401
402	= 2.3.0 – 2 Mar 2023 =
403	* Add ability to set a custom name for the plugin when listed in /wp-admin/plugins.php
404	* Reduce timeout when checking in the with API for settings updates to ensure to not affect performance.
405
406	= 2.2.1 – 16 Feb 2023 =
407	* Fix error on PHP7.0 on activation.
408	* Rename 'Profile Updated' log to User Updated.
409
410	= 2.2.0 – 7 Feb 2023 =
411	* Add support for globally disabling default logs and enabling/disabling Options table and Post Meta changes.
412
413	= 2.1.1 – 18 Jan 2023 =
414	* Fix undefined variable $meta in _logs-loop.php admin page when not connected to Logtivity.
415
416	= 2.1.0 – 6 Dec 2022 =
417	* Add ability to hide Logtvity from the WP UI using global settings.
418	* Check for new global settings every 10 minutes.
419	* When registering a site dynamically, pull in the site name.
420
421	= 2.0.1 – 7 Nov 2022 =
422	* Wrap better messaging on logs page when there are no results.
423	* Refine Option Updated meta sent.
424	* Add wrap error logging in try catch just incase of issue during logging.
425
426	= 2.0.0 – 26 Oct 2022 =
427	* Add error logging.
428	* Refine Option meta update logging by only logging updates done via a POST request. This avoids logging of less useful updates such as plugins setting last_check/synced timestamps that don't need to be logged.
429
430	= 1.20.1 – 17 Jun 2022 =
431	* Fix minor layout issue in log modal.
432	* Disable some unuseful Option Updated logs.
433
434	= 1.20.0 – 17 Jun 2022 =
435	* Add integration with Code Snippets plugin.
436
437	= 1.19.0 – 16 Jun 2022 =
438	* Start logging after plugins_loaded hook to ensure everything has loaded first.
439
440	= 1.18.0 – 13 Jun 2022 =
441	* Add logging of Option Updates.
442	* Allow wildcards when disabling specific logs.
443
444	= 1.17.1 – 4 Jun 2022=
445	* Fix occasional User Logged Out logging unnecessarily.
446	* Hide latest response info when debug mode is off.
447
448	= 1.17.0 – 13 May 2022=
449	* Added ability to globally disable logs across all sites from the Logtivity dashboard.
450	* Added ability to white label the Logtivity plugin across all sites from the Logtivity dashboard.
451
452	= 1.16.0 – 2 May 2022 =
453	* Add support for WP All Import
454
455	= 1.15.0 – 19 Apr 2022 =
456	* Add ability for admins to disable individual actions from being logged.
457
458	= 1.14.0 – 10 Apr 2022 =
459	* Add logging of post meta changes.
460
461	= 1.13.0 – 26 Mar 2022 =
462	* Add logging of Term Created and Deleted.
463
464	= 1.12.0 – 24 Mar 2022 =
465	* Fix unexpected ) error on old vesions of php.
466	* Add logging of Term Updated.
467
468	= 1.11.1 – 20 Feb 2022 =
469	* Fix md5 hash of site_url relative to previous release of detecting url change.
470
471	= 1.11.0 – 20 Feb 2022 =
472	* Disable logging if site_url changes and show notice to admin to stop accidental logs coming from dev/staging environments.
473
474	= 1.10.0 - 14 Feb 2022 =
475	* Add ability to register site with Logtivity from within the plugin by running a code snippet.
476
477	= 1.9.2 – 23 Jan 2022 =
478	* Allow the Logtivity config to be set via filters.
479
480	= 1.9.1 – 22 Dec 2021 =
481	* Fix bug where logs weren't displaying when Logtivity debug mode was set to false.
482
483	= 1.9.0 – 22 Dec 2021 =
484	* Moved settings page to top level menu item to allow for sub menu.
485	* Added new logs page in wp-admin to allow viewing logs inside WordPress.
486
487	= 1.8.2 – 10 Dec 2021 =
488	* Fix unnecessary encoding of hyphens being passed to the context field in the API.
489
490	= 1.8.1 – 9 Dec 2021 =
491	* Fix conflict between Logtivity and Jetpack Widget Visibility where updating widget visibility in the customiser would fail.
492
493	= 1.8.0 – 8 Dec 2021 =
494	* Added Formidable Pro integration.
495	* Added CSS tweaks to Logtivity Settings page.
496
497	= 1.7.1 – 7 Nov 2021 =
498	* Change action that Logout log hooks into to ensure user_id is attached to log.
499
500	= 1.7.0 - 17 Aug 2021 =
501	* Improvements to Settings page.
502	* Log EDD License Renewed
503	* Log EDD License Renewal Notification Unsubscribed
504	* Log EDD License Status Changed to [new_status]
505	* Log EDD License Upgraded
506	* Log EDD Site Deactivated
507	* Log EDD Site Added
508	* Log EDD Subscription Renewed
509	* Log EDD Subscription Created
510	* Log EDD Subscription Updated
511	* Log EDD Subscription [status] eg. Expired, Cancelled etc.
512	* Log EDD Subscription Deleted
513	* Log EDD Payment Method Updated
514
515	= 1.6.1 – 4 Aug 2021 =
516	* Begin adding support for the Easy Digital Downloads Software Licensing Addon.
517	* Log License Created events.
518	* Log License Activated events.
519	* Log License Activation Failed events.
520	* Log License Deactivated events.
521	* Don't log new comments when they are marked as spam.
522
523	= 1.6.0 =
524	* Added initial Easy Digital Downloads core integration.
525	* Track when Core Settings are updated.
526	* Track when Permalinks are updated.
527	* Track when Memberpress Transactions are Created/Updated.
528	* Track when Memberpress Emails are sent.
529	* Track when a Memberpress User Profile is updated.
530	* Track when Memberpress Settings are Updated.
531	* Track WordPress comments CRUD.
532
533	= 1.5.0 =
534	* Renamed Download Monitor Action name to File Downloaded.
535	* Added Request URL as log meta.
536	* Added Request Type as log meta.
537
538	= 1.4.0 =
539	* Removed deprecated async method from Logtivity_Logger class.
540	* Added API Key verification when updating Logtivity settings.
541
542	= 1.3.1 =
543	* Fix user info not always being picked up on User login action.
544	* Fix 0 being logged for username when not logged in.
545	* Fixed duplicate logs being recorded when Updating a post in Gutenberg.
546
547	= 1.3.0 =
548	* Added revision link to Post Updated logs.
549	* Added Role to Content parameter for User Logged In and User Logged Out.
550
551	= 1.2.0 =
552	* Added context parameter to API calls to separate out Actions from Titles.
553
554	= 1.1.0 =
555	* Add logging when updating menus.
556	* Add logging when updating widgets.
557	* Fix spelling mistake in postPermanentlyDeleted method.
558
559	= 1.0 =
560	* Fix php warning when tracking a logout event.
561