Hi,
It could be another plugin causing the issue. Try isolating the issue. See if Wordfence works as expected with no other plugins enabled. Start to add the other plugins back one at a time and test.
Here is our document on the issue:
https://support.wordfence.com/support/solutions/articles/1000010684-some-feature-in-wordfence-isn-t-working-what-should-i-do-
Let us know if that helps.
Thanks!
Brian
Thread Starter
pingram
(@pingram3541)
Yes I’m a wp developer too so this is almost always one of the first things I check before reporting a problem. Tested w/ twentyfifteen on clean install and only wf plugin installed and active. Same js error I reported originally.
Thanks for checking the other plugins. Are you able to block any IPs, or just not a specific range?
This might happen if you are typing a CIDR range like 192.168.1.0/24 instead of a range like: 192.168.1.0 – 192.168.1.255
If this doesn’t help, can you tell us the IP range you are trying to block?
Thread Starter
pingram
(@pingram3541)
You really should just check it yourself. I don’t believe its a validation issue or problem with my sites. I’m pretty sure you can duplicate this with a simple test. The form button requires javascript to complete the submission and the error renders the form inoperable. Like I said, checking the browser console you can see the error increment with each click. The second screenshot shows the path of the js file in the wf plugin file structure.
Before submit click – http://i.imgur.com/N1vGz9m.jpg
After submit click – http://i.imgur.com/BRm5aUR.jpg
For the record, the ranges I am adding can be found here: http://www.davemroz.com/blocking-kyivstar-from-accessing-your-wordpress-site/
Thread Starter
pingram
(@pingram3541)
Actually, I just discovered that the issue is only when I paste from my clipboard any IP range. If I delete it and type it in manually, even if it’s exactly matching my clipboard it now works. Must be some illegal character in the string. Probably still worth investigating better error handling in the form handling script but I got the range to take by manually typing in all ranges. You can still see what I’m talking about by copying and pasting the IP ranges from that link I provided. Phew, glad its figured out!
Thread Starter
pingram
(@pingram3541)
Figured it out, it was the hyphen. Deleting the hyphen and retyping it fixes the entry. Again, maybe add better error handling to provide a notice that states there is a field formatting issue.
Thanks for the follow-up — I had tried a number of IPv4 and IPv6 address ranges earlier, and the only way I came up with an error on the same line by typing was the CIDR style address (which isn’t accepted in this field), but pasting a bad character makes sense too.
It looks like the dash on that site was an en-dash (an “#8211” entity). I’ve entered a request to handle bad characters in this field, which should be included in a future version of Wordfence.
-Matt R
FB928
