WPChef
Forum Replies Created
-
Forum: Plugins
In reply to: [Limit Login Attempts Reloaded] Warning Emails Don’t Show Website LinkHi, good catch. We’ll address this in the next update. Meanwhile, you can see the domain in the unsubscribe link.
Hi Newt Labs,
Upon further investigation, we found that some current users had their email notifications turned on from one of the previous updates. This was an oversight on our part. We apologize for the inconvenience. We still suggest disabling the email notifications if you don’t want these emails.Forum: Reviews
In reply to: [Limit Login Attempts Reloaded] Borderline briberyHi Cruchybar, thank you for the review. We are glad to hear you are using our free version for all of your sites. We understand your frustration by the last update. It was not our intention to turn on email notifications for current users. You can simply go into the plugin settings and turn those off. Yes, we now offer a paid version, and IT IS like magic for some that have upgraded. If you’re happy with our free service, then great, but some websites need additional help and we’re here for them. Thanks again for using Limit Login Attempts Reloaded.
Forum: Plugins
In reply to: [Limit Login Attempts Reloaded] update caused Parse ErrorHi apexbee,
Thank you for reporting this. Fixed!
Forum: Plugins
In reply to: [Limit Login Attempts Reloaded] 404 errors in consoleHi Nazar,
Fixed, thank you!
Hi Newt Labs, thanks for reporting this. In the recent update, we added a dashboard alert inviting current users to consider turning on their email notifications so they are alerted of excessive failed login attempts. This does not automatically change the setting for current users unless they opt into it. Now if you have downloaded the plugin after the recent update, the email notifications are now turned on by default so users can understand in real-time what the attack level is. These notifications can be turned off in settings as always. If you believe that your current users had their email notifications turned on by default, please let us know so we can investigate further.
Forum: Plugins
In reply to: [Limit Login Attempts Reloaded] jQuery not definedThank you!
Forum: Plugins
In reply to: [Limit Login Attempts Reloaded] jQuery not definedHi btalberg,
This is most likely a conflict with another plugin. Please try installing LLAR on an empty WP and there should be no error. To determine what plugin causes the issue, you might try deactivating other plugins one by one and note when the error is gone.
Forum: Reviews
In reply to: [Limit Login Attempts Reloaded] Enough is enoughHi goprolocal,
This means your site has issues with AJAX. You might want to check your caching level or other related settings as such misconfiguration can break other important parts of the site.
We have published a new version of the plugin with an alternative way of closing the message (top right corner), please try it out.
Forum: Reviews
In reply to: [Limit Login Attempts Reloaded] Bad placement of review notificationMost likely your site has issues with AJAX b/c of improper caching. A lot of admin panel functions depend on AJAX so we suggest you check that out since this is a sign of a bigger issue.
Forum: Plugins
In reply to: [Limit Login Attempts Reloaded] Users names are case sensitive?Hi,
Yes, they are case sensitive.
Forum: Plugins
In reply to: [Limit Login Attempts Reloaded] I always get locked out!Hi guys,
@poimandres to solve this via the plugin, you should put “HTTP_X_REAL_IP” into the trusted IP origins field. This is highly not recommended though! You should ask your hosting provider to fix the problem with your REMOTE_ADDR being incorrect.
@omaraf please copy and paste here information from the Debug tab of the plugin.
Forum: Plugins
In reply to: [Limit Login Attempts Reloaded] Bad code risk scoreHi,
We have uploaded a new version of the plugin with these issues fixed.
Thank you!
Hi Trisha,
We have removed this feature from the plugin completely.
Forum: Plugins
In reply to: [Limit Login Attempts Reloaded] Bad code risk scoreHi,
Thank you for this! We have verified the code. Here is a list of problems:
1. A cookie is set not via https.
2. No default option in a switch block.
3. Use of md5(). We do not use it to secure sensitive information though.
4. A get variable is not secured. It can be set by the admins only though.Although the issues are minor, we’ll address them anyway.