digregp
Forum Replies Created
-
Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysThank you – that fixed the issue with the date filter. Back to the original issue. I did some testing and have confirmed (in our installation) that the cause of the report only showing 2 days is related to the Auto Prune Login Events setting. When this is selected the login events are removed from the database and only leave 2 days (it took a day for it to happen). When it is unchecked, the report has kept the login events for days. I assume the cron events “swpm_daily_cron_event” or “swpm_twicedaily_cron_event” might be doing some housekeeping.
Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysThank you. Looking forward to an update.
- This reply was modified 6 days, 19 hours ago by digregp.
Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysJust noticed that you made the following changes in the latest release:
- The Recent Login Events section in the Reports menu now displays login events from the last 30 days by default.
You are accomplishing this by setting the date filter. ISSUE: Strangely enough, any logon past 12pm today is not showing up. I had to change the “End Date” to tomorrow for those events to show.
Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysAwesome – great work. Thank you for bearing with me. I love the plugin and all of the associated add ons. It has worked well, and I only reach out to you to try to make it better. You have been very responsive and I appreciate all you do. Cheers!
Ok I will explain the issue in more detail.
See image below
The left menu has a Simple History link to your plugin. When I click on that and it opens the simple history page, the event times are correct. They conform to our set timezone.
In the image below, Hostgator provides a dashboard and under the screen options dropdown on the upper right, you can select Simple History which creates a tile on the dashboard. The events listed in that tile are the same as on the simple history page, but the times are UTC. They do not conform to the system set timezone. So can you please check if your dashboard tile is simply using UTC, or if uses the WordPress set timezone. Hope this helps.
Hello. I saw you released an updated version. I do not see that the dashboard widget/tile, or the history at the top toolbar of the WordPress admin menu has been corrected.
Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysJust to be clear, when I say the failed logon limit is not working, after reaching the limit, there is a blackout period for that IP address. If you log in correctly within that blackout period, the logon completes. I assume it would deny the logon until that blackout period ends from that IP address (regardless of username). I do notice that a failed attempt beyond the failed logon limit number is not recorded in the swpm_events_tbl. Subsequently a successful logon from that IP address deletes the failed logon records as I mentioned before.
I wound up deleting all of the stale records in the swpm_events_tbl. They were all failed logon attempts with the member_id and the user_agent as null.
Debug entries are as follows (note xxx@xxx.com does not exist in membership, yyy@yyy.com does exist in membership):
2026/08/26 12:18:23] – SUCCESS: Failed login attempt. The visitor IP address: xxx.xxx.xxx.xxx has 1 attempts left.
[2026/08/26 12:19:07] – SUCCESS: Authentication request – Username: xxx@xxx.com
[2026/08/26 12:19:07] – FAILURE: Failed login attempt limit reached for visitor IP address: xxx.xxx.xxx.xxx
[2026/08/26 12:19:51] – SUCCESS: Authentication request – Username: xxx@xxx.com
[2026/08/26 12:19:51] – FAILURE: Failed login attempt limit reached for visitor IP address: xxx.xxx.xxx.xxx
[2026/08/26 12:20:38] – SUCCESS: Authentication request – Username: xxx@xxx.com
[2026/08/26 12:20:38] – FAILURE: Failed login attempt limit reached for visitor IP address: xxx.xxx.xxx.xxx
[2026/08/26 12:21:13] – SUCCESS: Authentication request using email address: yyy@yyy.com, Found a user record with username: yyy@yyy.com
[2026/08/26 12:21:13] – SUCCESS: Authentication request – Username: yyy@yyy.com
[2026/08/26 12:21:13] – SUCCESS: SwpmAuth::set_cookie() – Value of ‘remember me’ parameter:
[2026/08/26 12:21:13] – SUCCESS: The ‘Remember me’ option is unchecked for this request, setting expiry to be a session cookie. The session cookie will expire when the browser is closed.
[2026/08/26 12:21:13] – SUCCESS: Authentication successful for username: yyy@yyy.com. Triggering swpm_after_login_authentication action hook.
[2026/08/26 12:21:13] – SUCCESS: Trying wp_signon() with username: yyy@yyy.com
[2026/08/26 12:21:13] – SUCCESS: wp_authenticate action. User with username: yyy@yyy.com is already logged in.
[2026/08/26 12:21:13] – SUCCESS: Failed login limit has been reset for visitor IP address: xxx.xxx.xxx.xxx
[2026/08/26 12:21:13] – SUCCESS: wp_login hook triggered. Username: yyy@yyy.com
[2026/08/26 12:21:13] – SUCCESS: Setting current WP user to: yyy@yyy.com
[2026/08/26 12:21:13] – SUCCESS: Triggering swpm_login_auth_completed_filter hook.
[2026/08/26 12:21:13] – SUCCESS: Triggering swpm_after_login hook.- This reply was modified 1 week, 3 days ago by digregp.
Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysHello again! Well, I believe the recent login events is now working. 3 days ago I “Reset All Login Entries”. Things seem to be showing up now as I used only have 2 days, now everything is being captured. Interestingly I looked in the database at the swpm_events_tbl, and prior to me resetting all login events, in all of the records, the member_id and the user_agent were null. Since the reset, they are all populating properly. Maybe a reset cleaned up the table. The “bad” records never deleted when I reset all login entries, so I am wondering if I should delete those records manually from the swpm_events_tbl?
Looking at the failed login attempts issue, I noticed something very interesting in the swpm_events_tbl. If as user has a failed login attempt it is captured in the table. If any successful login attempt occurs from that IP after that, the record of the failed attempt(s) are deleted from the database. So the event IDs show a gap in sequence. Maybe this is by design. This could provide some info as to why the failed login attempts limit is not working. I never see any type of entry in there related to FAILURE: Failed login limit could not be reset for visitor IP:xxx.xxx.xxx.xxx. Curious how that login limit is recorded in the database. Is it in another table? Like you said, it could be conflicting with another plugin. I also added all login pages to the no cache setting for the hosting provider. Thanks again for your help!!Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysHello – My plugins are set to auto update so I assume the add ons and plugins are the latest version. I see them updating, and currently no updates are available. Do I have to download any updates and manually install?
Recent login issue:
I am the only admin so no data was cleared, and no settings toggled. It has never showed more than 2 days of login history. I cleared the data yesterday to start fresh, so we will see tomorrow if the history has more than 2 days of data. I installed a secondary plugin that captures history and that is doing the trick for me right now. I would still like to get this feature working as it should. Is there a table in the database where I could look to see if the data is in there?
Failed Login Attempt Limit:
I removed the ip addresses and login names, for privacy reasons, but they were there. The ip address was the same and did not rotate or change. I actually missed redacting some of the info and had the moderators remove the data for me because I could not edit the post (too late). The log keeps showing that the person was already logged in. Maybe that is the problem. I added the login screen to the exclusion list for caching and it still happens. Also it is not setting the variable: FAILURE: Failed login limit could not be reset for visitor ip:xxx.xxx.xxx.xxx. Something is preventing that as well. Is this variable specific to your plugin, or could it be used by another plugin?
Just curious if you were able to reproduce the issue, or is it just an issue with our setup? The plugin is working (login/logout) so the users are not affected, but any ideas would be helpful to try.Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 Days[2026/08/24 12:56:59] – SUCCESS: Authentication request using email address: , Found a user record with username:
[2026/08/24 12:56:59] – SUCCESS: Authentication request – Username:
[2026/08/24 12:56:59] – SUCCESS: Failed login attempt. The visitor IP address: has 1 attempts left.
[2026/08/24 12:57:26] – SUCCESS: Authentication request using email address: , Found a user record with username:
[2026/08/24 12:57:26] – SUCCESS: Authentication request – Username:
[2026/08/24 12:57:26] – FAILURE: Failed login attempt limit reached for visitor IP address:
[2026/08/24 12:58:44] – SUCCESS: Authentication request using email address: , Found a user record with username:
[2026/08/24 12:58:44] – SUCCESS: Authentication request – Username:
[2026/08/24 12:58:44] – SUCCESS: SwpmAuth::set_cookie() – Value of ‘remember me’ parameter:
[2026/08/24 12:58:44] – SUCCESS: The ‘Remember me’ option is unchecked for this request, setting expiry to be a session cookie. The session cookie will expire when the browser is closed.
[2026/08/24 12:58:44] – SUCCESS: Authentication successful for username: .Triggering swpm_after_login_authentication action hook.
[2026/08/24 12:58:44] – SUCCESS: Trying wp_signon() with username:
[2026/08/24 12:58:44] – SUCCESS: wp_authenticate action. User with username: is already logged in.
[2026/08/24 12:58:44] – SUCCESS: Failed login limit has been reset for visitor IP address:
[2026/08/24 12:58:44] – SUCCESS: wp_login hook triggered. Username: pete***
[2026/08/24 12:58:44] – SUCCESS: Setting current WP user to: pete***
[2026/08/24 12:58:44] – SUCCESS: Triggering swpm_login_auth_completed_filter hook.
[2026/08/24 12:58:44] – SUCCESS: Triggering swpm_after_login hook.
[2026/08/24 12:58:49] – SUCCESS: SwpmAuth::logout() – Logout request received for username:
[2026/08/24 12:58:49] – SUCCESS: SwpmAuth::logout() – Logout actions executed successfully.This is showing how the failed login attempt limit is not working. This is a separate issue to the history not keeping for more than 2 days. Appreciate your help!
- This reply was modified 1 week, 4 days ago by Yui. Reason: redacted for privacy
Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysThank you. I will see in a week or so about the login history.
- This reply was modified 1 week, 5 days ago by digregp.
Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysHello. Yes I am running the latest plugin version on WP7.1.
I am running add ons for your plugin – quite a few:
Download monitor, after logon redirection, custom messages, form builder, google recaptcha, full page protection, member listing, member data exporter, partial protection.I enabled debug mode and had one failure right off the bat: FAILURE: Failed login limit could not be reset for visitor ip:
The Failed Login Attempt limit does not work as well. Even if I disable our security plugin. It allows the user to login after the limit of failed attempts.
@eskapism Good morning. I would rather not as it contains user logon data. Just know that the dashboard is showing the same events, just with a time 4 hours earlier. Our timezone is set to America/New York.
Forum: Plugins
In reply to: [Simple Membership] Recent Login Events on Reports Page Only Goes Back 2 DaysYes Login Event Tracking has been enabled for months.
I still can only see 2 days of data.
Also, the login count by date tab only shows 2 days worth of data, today and yesterday. It lists previous days, but the count is 0 for each day.
Is anyone else seeing this issue? Thank you very much.