티스토리 수익 글 보기

Hi!

I am using MainWP and its mentioned that WP Activity Log is a 3rd party integration. I am doing some testing and have noticed that if a “target” site already has WP Activity Log installed, then the MainWP site gets loaded with it is well, all the log sources of the child sites appear, and I am able to filter by site in the drop down menu.

However, if MainWP is already configured and I load WP Activity Log on a new child site, it does not reflect in either the parent WP Activity Log or in the MainWP Activity Log.

The only way I have been able to get a site to appear in MainWP is by deleting the plugin (and all of its install data) on the Parent install, and re-install it again. This isn’t something i’d like to have to do each time a new site is added under our management.

Hoping to get some input on how to fix this. Currently one of the target sites is not showing, it is running the following:

### WordPress Environment ###

Home URL: https://alc***********.com
Site URL: https://alc***********.com
WP Content Path: /home/alc***********ing/public_html/wp-content
WP Path: /home/alc***********ing/public_html/
WP Version: 6.9
WP Multisite: –
PHP Memory Limit: 256 MB
WP Debug Mode: –
Language: en_US

### Server Environment ###

Server Info: Apache
PHP Version: 8.1.29
PHP Post Max Size: 128 MB
PHP Time Limit: 180
PHP Max Input Vars: 1700
ZipArchive: ✔
cURL: ✔
mail: ✔
MySQL Version: 8.0.39
Max Upload Size: 128 MB
DOMDocument: ✔
WP Remote Get: ✔
WP Remote Post: ✔
GD Library: bundled (2.1.0 compatible)

### Active Plugins (20) ###

>BackWPup: by BackWPup – WordPress Backup & Restore Plugin
>Broken Link Checker: by WPMU DEV
>CookieYes | GDPR Cookie Consent: by CookieYes
>Disable Comments: by WPDeveloper
>Duplicate Menu: by Jon Christopher
>Yoast Duplicate Post: by Enrico Battocchi & Team Yoast
>Avada Builder: by ThemeFusion
>Avada Core: by ThemeFusion
>reCaptcha by BestWebSoft: by BestWebSoft
>Gravity Forms Zero Spam: by GravityKit
>Login Logo: by Mark Jaquith
>MainWP Child: by MainWP
>Post SMTP: by Post SMTP
>SeedProd Pro: by SeedProd
>Simple History: by Pär Thernström
>Yoast SEO: by Team Yoast
>WP Crontrol: by John Blackbourn
>WP Activity Log: by Melapress
>Smush: by WPMU DEV
WPS Hide Login: by WPServeur
NicolasKulka
wpformation

one of my sites runs your plugin and the server is running an old php version.

my hosting company recommended a scan before updating ot PHP 8.3 and this is what it reported

/chroot/home/a26ac25c/698fee5af1.nxcli.net/html/wp-content/plugins/wp-security-audit-log/classes/Entities/class-abstract-entity.php

is this a real error or a misclassification by the checker? I would like to update php ASAP since current version is end-of life

warning in dashboard

Your site is currently running on an out-of-date version of PHP!

PHP is the underlying programming language that WordPress and its themes/plugins are written in. Newer releases bring more features, better performance, and regular security fixes.

Your site is currently running on PHP 8.1, which stopped receiving security updates on December 31, 2025!

Hello there, I wish to know how can we filter a special event to understand something weird happened ? We have some clients account who disapeared. And I wish to know with your log solution what’s happened and when. Thanks a lot

Getting below deprications for your plugins after updating to PHP 8.4. Please advise if they can interfere with basic functioning of your plugin and can we expect these fixed on next update?

Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /wp-content/plugins/activity-log-wp-seo/wp-security-audit-log/sensors/class-yoast-seo-sensor.php on line 216
Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /wp-content/plugins/activity-log-wp-seo/wp-security-audit-log/sensors/class-yoast-seo-sensor.php on line 217
Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /wp-content/plugins/activity-log-wp-seo/wp-security-audit-log/sensors/class-yoast-seo-sensor.php on line 218
Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /wp-content/plugins/activity-log-wp-seo/wp-security-audit-log/sensors/class-yoast-seo-sensor.php on line 219
Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /wp-content/plugins/activity-log-wp-seo/wp-security-audit-log/sensors/class-yoast-seo-sensor.php on line 220
Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /wp-content/plugins/activity-log-wp-seo/wp-security-audit-log/sensors/class-yoast-seo-sensor.php on line 224
Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /wp-content/plugins/activity-log-wp-seo/wp-security-audit-log/sensors/class-yoast-seo-sensor.php on line 226
Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /wp-content/plugins/activity-log-wp-seo/wp-security-audit-log/sensors/class-yoast-seo-sensor.php on line 227
Deprecated: Constant FILTER_SANITIZE_STRING is deprecated in /wp-content/plugins/activity-log-wp-seo/wp-security-audit-log/sensors/class-yoast-seo-sensor.php on line 228

Dear Support Team,

We recently upgraded our PHP version from 8.1.16 to 8.3. Following the update, we started receiving deprecation warnings related to the WP Activity Log plugin on our site.

Kindly look into this issue. Please let us know if you require anything further from our side to assist with the investigation.

Hello.

We only want to track actions by admin users, not system.

I’ve added ‘WooCommerce System’ and ‘Unknown User’ to the excluded users field in ‘excluded objects’, but the activity log still includes these items. How can I filter them out.

I can’t disable events, as some of these events could be actioned by an actual human user and not just the system.

Thanks,

Ian.

Hi,
at the moment you can only set hours to automatically log out inactive users. So the smallest number is 1 hours – this is way too long!! So it would be nice if you could switch this to minutes in a future update, so that we can enter something like 30 minutes in there!

Hi, I’ve set “Multiple Sessions” to “Allow one session only”, but can login with the same user on different Browsers. That shoudln’t be possible, no!?

Hello,
we are still receiving error messages even after updating to 5.5.3. The whole site is up to date. Hosting: GoDaddy – if that is important.

Could you please suggest anything to resolve this?

Many thanks for considering my request.

Regards, M

Error message:


In this case, WordPress caught an error with one of your plugins, WP Activity Log.

First, visit your website (https://email.cloud.secureclick.net/c/7381?id=61091793.10212420.1.bdf7b0182d5941996b4f928f0a7f2b94 and check for any visible issues. Next, visit the page where the error was caught (https://email.cloud.secureclick.net/c/7381?id=61091793.11913577.1.fa6cd145799376c24f16418a6a2b80cc and check for any visible issues.

Please contact your host for assistance with investigating this issue further.

If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.

https://email.cloud.secureclick.net/c/7381?id=61091793.11913578.1.d286edb73817470daa0e99b1fc229b25

To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.8.3
Active theme: Twenty Twenty-Four (version 1.3) Current plugin: WP Activity Log (version 5.5.3) PHP version 8.3.26 Error Details

An error of type E_ERROR was caused in line 290 of the file /dom568978/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php. Error message: Uncaught TypeError: strpos(): Argument #2 ($needle) must be of type string, false given in /dom568978/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php:290
Stack trace: 0 /dom568978/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php(290): strpos('https://email.cloud.secureclick.net/c/7381?id=61091793.11841901.1.9fddcb489e26c4bbea8348f7c4a1248f', false) 1 /dom568978/wp-includes/class-wp-hook.php(324): WSAL\WP_Sensors_Helpers\WooCommerce_Sensor_Helper_Second::editing_product(Object(WP_Post)) 2 /dom568978/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(Object(WP_Post), Array) 3 /dom568978/wp-includes/plugin.php(517): WP_Hook->do_action(Array) 4 /dom568978/wp-admin/edit-form-advanced.php(482): do_action('post_edit_form_…', Object(WP_Post)) 5 /dom568978/wp-admin/post.php(206): require('/dom568978/wp-a…') 6 {main}

thrown

Error Details

An error of type E_ERROR was caused in line 899 of the file /wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php. Error message: Uncaught TypeError: strpos(): Argument #1 ($haystack) must be of type string, null given in /wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php:899
Stack trace: 0 /wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php(899): strpos() 1 /wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php(1376): WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::get_plugin_dir() 2 /wp-includes/class-wp-hook.php(324): WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::on_available_plugin_update() 3 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 4 /wp-includes/plugin.php(517): WP_Hook->do_action() 5 /wp-includes/option.php(2697): do_action() 6 /wp-includes/update.php(578): set_site_transient() 7 /wp-includes/update.php(1031): wp_update_plugins() 8 /wp-includes/class-wp-hook.php(324): _maybe_update_plugins() 9 /wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() 10 /wp-includes/plugin.php(517): WP_Hook->do_action() 11 /wp-admin/admin.php(176): do_action() 12 /wp-admin/post.php(12): require_once(‘…’) 13 {main}

thrown

After recently upgrading your plugin to version 5.5.2, I noticed that my admin > plugins page (and the admin > updates page) both were showing blank pages. It took me a few hours to track it down to your plugin (error_log file wasn’t reflecting any actual errors related to this), and found that by deleting your plugin was the only way to get the blank admin pages back again.

I manually uploaded the latest version and reinstalled, only to run into the same issue again. The issue is same in PHP 8.2 and 8.3.

Just an FYI so you can address this.

I get the below error when trying to access the plugin page.
WP 6.8.3
PHP 8.3
Woo 10.2.2

Uncaught Error: strpos(): Argument #1 ($haystack) must be of type string, null given
in /var/www/sandbox.example.dev/htdocs/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php on line 899

Call stack:

1. strpos()
   wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php:899
2. WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::get_plugin_dir()
   wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php:1376
3. WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::on_available_plugin_update()
   wp-includes/class-wp-hook.php:324
4. WP_Hook::apply_filters()
   wp-includes/class-wp-hook.php:348
5. WP_Hook::do_action()
   wp-includes/plugin.php:517
6. do_action()
   wp-includes/option.php:2697
7. set_site_transient()
   wp-includes/update.php:394
8. wp_update_plugins()
   wp-includes/class-wp-hook.php:324
9. WP_Hook::apply_filters()
   wp-includes/class-wp-hook.php:348
10. WP_Hook::do_action()
    wp-includes/plugin.php:517
11. do_action()
    wp-admin/admin.php:386
12. require_once('/var/www/sandbox.exa...s/wp-admin/admin.php')
    wp-admin/plugins.php:10

025/10/22 15:27:14 [error] 21351#21351: *162876 FastCGI sent in stderr: "PHP message: PHP Warning: Undefined property: stdClass::$plugin in /www/domain/public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php on line 1374PHP message: PHP Fatal error: Uncaught TypeError: strpos(): Argument #1 ($haystack) must be of type string, null given in /www/domain/public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php:899
Stack trace:
#0 /www/domain/public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php(899): strpos(NULL, '/')
#1 /www/domain/public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-wp-plugins-themes-sensor.php(1376): WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::get_plugin_dir(NULL)
#2 /www/domain/public/wp-includes/class-wp-hook.php(324): WSAL\WP_Sensors\WP_Plugins_Themes_Sensor::on_available_plugin_update('update_plugins', Object(stdClass), 0)
#3 /www/domain/public/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters('', Array)
#4 /www/domain/public/wp-includes/plugin.php(517): WP_Hook->do_action(Array)

Warning message loop

PHP Warning: Attempt to read property “ID” on null in /public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php on line 2530
PHP Warning: Attempt to read property “ID” on null in /public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php on line 2531
PHP Warning: Attempt to read property “post_title” on null in /public/wp-content/plugins/wp-security-audit-log/classes/WPSensors/class-woocommerce-sensor-helper-second.php on line 2532

Hello.

Does the plugin have an API (functions or hooks) for logging custom events?

Something like Elementor’s Activity Log aal_insert_log().

I couldn’t find API documentation on your website.

Thanks.

Hi,
Can I see search queries users made within the site?

Specificaly, on the forms entries page, when I click the gear to manage columns – buttons are not visible: https://app.screencast.com/B5VasBbGsus9A

Disabling the plugin helps to resolve the issue: https://app.screencast.com/BbvMmwLkfgCkF/e

• This topic was modified 3 months, 4 weeks ago by Dima.
• This topic was modified 3 months, 4 weeks ago by Dima.

Please help me with:
Track if someone clicks on:

1. Social Share Button
2. Star Rating
   Thanks a lot…

WP Activity Log V5.5.0

Most if not all log entries have incorrect IP addresses such as 130.176.212.117 and 15.158.196.97.

These are both Amazon accounts but are logged when I login from 58.171.237.67.

The rest of the logged data is correct.

Hi, when we updated to your latest version, we are no longer able to manually upload a theme using the “Upload Theme “button. When we click that button nothing happens. The upload file options does not show. But for those sites that that has older WP Activity Log version, that functionality still works. Also, I tried deactivating your plugin and that also works. That’s how I figured, this plugin is causing the issue.

Looking forward to your help. Thank you!

I am facing an intermittent issue on my WordPress website that seems to have started after installing the WP Activity Log plugin.

Issue Description:

• On three separate occasions, all pages of the site (except the homepage) suddenly started returning a 404 error page.
• The issue sometimes resolves itself after a while, but in one case I need to re-save (flush) the permalink settings in WordPress to get the site working again.
• Our hosting provider (Hostinger) also recommended flushing permalinks. After the second occurrence, I proactively re-saved permalinks as a precaution. However, the issue still occurred a third time.

Timeline / Observations:

• This issue started only after installing WP Activity Log.
• It does not happen consistently — only intermittently.
• Since then, the plugin has been kept activated and no issues have happened for the last 24 hours.

Questions:

• Could WP Activity Log (or any of its settings) cause temporary permalink or rewrite conflicts leading to 404 errors?
• Is this a known issue, and are there any recommended troubleshooting steps to identify if the plugin is indeed the cause?
• Are there specific logs I should capture (or enable within the plugin) to provide you more details if the issue happens again?

The Activity Log Viewer shows 10 records per page by default.

Click “Screen Options” then change the value from (say) 10 to 30 then click Apply. The new value is not saved, and Log Viewer continues to display 10 records per page.

• This topic was modified 4 months, 2 weeks ago by flymike.

I just noticed that the “UPLOAD THEME” button doesn’t display the upload field when the WP Activity Log plugin is activated.

I’ve deactivated it and the button works again.

Just letting you know in case you haven’t noticed this bug.

Hello,
I received your weekly email notification

The email has info about logins to my website .
However , My website is a dedicated for blogs . No login is needed.
Look below at the log . 1227 failed logins ?
I do not have any login to my users ?

Is it a bug in your log email ?

Eran feit

Here is the message :
********************
User Logins
There were 7 logins on your site from 2 unique users.
Failed User Logins
There were 1227 failed logins due to a wrong passwords on your site.
There were 542 failed logins due to a wrong usernames on your site.
********************

• This topic was modified 4 months, 3 weeks ago by feitgemel.

I was having some problems with running cron and I noticed that this plugin was causing issue:

xyz@abc:~/webapps/xyz$ wp cron event run --due-now

Executed the cron event 'wp_privacy_delete_old_export_files' in 0.015s.

Executed the cron event 'wsal_cleanup_hook' in 0.021s.

Executed the cron event 'task_runner_worker_cron_preload-urls' in 0.006s.

Executed the cron event 'action_scheduler_run_queue' in 0.019s.

Executed the cron event 'ws_form_wp_cron_action_database' in 0.015s.

PHP Fatal error:  Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, cannot access private method WSAL\Utils\Migration::migrate_users() in /home/xyz/webapps/xyz/wp-includes/class-wp-hook.php:324

Stack trace:

#0 /home/xyz/webapps/xyz/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

#1 /home/xyz/webapps/xyz/wp-includes/plugin.php(565): WP_Hook->do_action()

#2 phar:///usr/local/sbin/wp/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(358): do_action_ref_array()

#3 phar:///usr/local/sbin/wp/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(238): Cron_Event_Command::run_event()

#4 [internal function]: Cron_Event_Command->run()

#5 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func()

#6 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}()

#7 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(497): call_user_func()

#8 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(470): WP_CLI\Dispatcher\Subcommand->invoke()

#9 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(493): WP_CLI\Runner->run_command()

#10 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1295): WP_CLI\Runner->run_command_and_exit()

#11 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()

#12 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(84): WP_CLI\Bootstrap\LaunchRunner->process()

#13 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(35): WP_CLI\bootstrap()

#14 phar:///usr/local/sbin/wp/php/boot-phar.php(20): include('...')

#15 /usr/local/sbin/wp(4): include('...')

#16 {main}

  thrown in /home/xyz/webapps/xyz/wp-includes/class-wp-hook.php on line 324

Fatal error: Uncaught TypeError: call_user_func_array(): Argument #1 ($callback) must be a valid callback, cannot access private method WSAL\Utils\Migration::migrate_users() in /home/xyz/webapps/xyz/wp-includes/class-wp-hook.php:324

Stack trace:

#0 /home/xyz/webapps/xyz/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()

#1 /home/xyz/webapps/xyz/wp-includes/plugin.php(565): WP_Hook->do_action()

#2 phar:///usr/local/sbin/wp/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(358): do_action_ref_array()

#3 phar:///usr/local/sbin/wp/vendor/wp-cli/cron-command/src/Cron_Event_Command.php(238): Cron_Event_Command::run_event()

#4 [internal function]: Cron_Event_Command->run()

#5 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/CommandFactory.php(100): call_user_func()

#6 [internal function]: WP_CLI\Dispatcher\CommandFactory::WP_CLI\Dispatcher\{closure}()

#7 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Dispatcher/Subcommand.php(497): call_user_func()

#8 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(470): WP_CLI\Dispatcher\Subcommand->invoke()

#9 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(493): WP_CLI\Runner->run_command()

#10 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1295): WP_CLI\Runner->run_command_and_exit()

#11 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(28): WP_CLI\Runner->start()

#12 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(84): WP_CLI\Bootstrap\LaunchRunner->process()

#13 phar:///usr/local/sbin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(35): WP_CLI\bootstrap()

#14 phar:///usr/local/sbin/wp/php/boot-phar.php(20): include('...')

#15 /usr/local/sbin/wp(4): include('...')

#16 {main}

  thrown in /home/xyz/webapps/xyz/wp-includes/class-wp-hook.php on line 324

Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.

Hi

I am trying to resolve some login issues to my site, WP Activity Log has been a great help is sorting out most of the issues.

I currently have user who can’t login and their activity is being recorded by WP Activity Log. On the log entry it shows the users email address and then ‘Deleted user’

What does ‘Deleted user’ mean? I can find the user in the Users area and there is nothing to show the user has been deleted.

Cheers Rob

• This topic was modified 4 months, 4 weeks ago by rgilchrist.

It seems with your plugin in file wp-security-audit-log/classes/class-wp-security-audit-log.php on line 956 you are adding some inline CSS that affects every single SVG menu icon.

Is it possible for you to update the CSS selector to something like “#adminmenu #toplevel_page_wsal-auditlog div.wp-menu-image.svg” so that you aren’t applying this style to other 3rd party plugins?

I had to completely remove WP Activity Log because it was throwing a fatal error on the Audit Log screen. This happened suddenly overnight while I was on PHP 8.2. I rolled back to PHP 8.1 to see if that fixed the issue, but it did not.

Error:
Uncaught Error: Class name must be a valid object or a string in /wp-content/plugins/wp-security-audit-log/classes/Helpers/class-view-manager.php:483

Steps taken:

1. Tried disabling all other plugins — still crashed.
2. Tried rolling back to 5.4.1 — same error.
3. Switched PHP from 8.2 to 8.1 — same error.
4. Could not enable the plugin even in Troubleshooting Mode (site failure message).
5. Removed the plugin entirely and replaced it with a different logger.

This appears to be an internal bug with the plugin itself and not a conflict. Please advise when a fixed version is available that works with current WordPress and PHP versions.

I am using the WP Activity Log Viewer and I’d like to know if there is a way to mask/remove the IP location of the monitored users. This seems to be a GDPR issue and I’d like to have it not logged if possible.

Thank you,
Matei

Hi,

We recently experienced an unexpected issue on our website https://www.brucelipton.com, where a block of PHP code was being displayed on the frontend. The issue persisted even after clearing the cache and appeared to be related to the WP Activity Log plugin.

After investigating, we noticed the code originated from WP Activity Log. The issue was resolved after updating some related plugins, but we wanted to bring this to your attention in case it’s a known issue or requires further action.

You can view the code that appeared on the frontend via this link: https://codeshare.io/5OKD4j

Please let us know if you have any insight or recommendations to help prevent this from happening again.