Support » Plugin: WP Activity Log (formerly WP Security Audit Log) » Front End Login Issue

  • Hello,

    I am using the latest versions of WPAL and Simple WordPress Membership Plugin.

    In the “Front-end events” for WPAL I have the boxes for “front-end users registrations” and “front-end users logins” checked; however, nothing is logged in the “Audit log viewer” when I register / login from the front end. If I log in or register from wp-admin, everything shows.

    Just to test things, I download two alternative plugins “Stream” and “Activity Log”. Both of these plugins are able to detect the front end login/registration; however, they do not appear to detect login failure from the front end, which is important to me.

    To test things in WPAL, I enabled the request log. The results are as follows:

    When a user fails front end login:
    [2020-04-18 18:05:42] POST /wp-cron.php?doing_wp_cron=1587233142.0875780582427978515625
    [2020-04-18 18:05:42] POST /wp-admin/admin-ajax.php?_fs_blog_admin=true

    When a user registers for an account on the front end:

    [2020-04-18 18:13:01] POST /wp-cron.php?doing_wp_cron=1587233581.2709810733795166015625

    Any idea how I can make it work? Thank you!!

Viewing 1 replies (of 1 total)
  • Plugin Contributor robertabela


    Thank you for posting this question @ttpyro

    For the records, we are copying what we’ve sent you over email here:

    Our plugin does not capture the logins from the Simple Membership plugin because it initializes the login sequence earlier than the init(), which is when all the other plugins are loaded (

    Although there is nothing official, this is not a recommended practice. There is a general consensus that plugins should be loaded after init(), as the WordPress documentation recommends. As a matter of fact, this is the first login plugin for which we cannot detect logins. Our plugin detects logins from WooCommerce, Easy Digital Downloads, Ultimate Members and several others.

    The other activity log plugins detect this login because they are also loading their plugin before the init(). We do not load this plugin because of performance. Our plugin is designed to detect logins and what logged in users do, so there is no point in loading it too early. Otherwise, it will affect the performance of the front end of the website, and we do not want that.

    The good news is that there are two solutions to this problem. The first one would be to talk to the developers of the plugin Simple Membership and ask them to move the login after the init(), unless they have a specific reason for triggering it so early. If they have a reason, I’d like to learn about it.

    The second option would be for us to create a sort of API which you can trigger via some code. So basically when you add this code to the plugin’s login page, our plugin is initialized before the login occurs, so we can capture the login.

    Would like to hear what your thoughts are on the above. Thank you very much for reporting this issue and for using our plugin.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.