PumpinIron
Well-known member
Lately I've been getting a ton of users telling me they can't edit the "About" field of their profile. Whenever they try to fill it out and save it, they get an error saying that spam was detected (or something along those lines).
When checking the spam log in my Admin CP, I see lots of errors. here's an example of one:
Action: Moderated | Askimet Matched
Generated by: Mountain Main | Yesterday at 2:33 PM | Content: user_about
Any way I can fix this issue, or at least set it up so that the spam filter isn't active when users are editing profile fields?
It seems like it's very overly aggressive or something.
When checking the spam log in my Admin CP, I see lots of errors. here's an example of one:
Action: Moderated | Askimet Matched
Generated by: Mountain Main | Yesterday at 2:33 PM | Content: user_about
Code:
array(4) {
["url"] => string(24) "/account/account-details"
["referrer"] => string(51) "https://wranglertjforum.com/account/account-details"
["_GET"] => array(0) {
}
["_POST"] => array(8) {
["option"] => array(1) {
["receive_admin_email"] => string(1) "1"
}
["profile"] => array(2) {
["location"] => string(9) "Tennessee"
["website"] => string(0) ""
}
["custom_fields"] => array(10) {
["gender"] => string(4) "male"
["occupation"] => string(7) "Retired"
["vehicle"] => string(4) "2001"
["model"] => string(5) "Sport"
["engine"] => string(3) "4.0"
["mods"] => string(245) "3” Teraflex Lift,Front steering upgrade,Dana 35 Heavy Chrome Moly Axles in rear with locker,4:10 gears,9,500 lb. Winch,33x12:50 Firestone Destinations mounted on 15x10 Procomp Alloys,numerous LED lights. This is and will be an ongoing project."
["facebook"] => string(0) ""
["twitter"] => string(0) ""
["gplus"] => string(0) ""
["skype"] => string(0) ""
}
["about_html"] => string(140) "<p>Married 40 years and we have a son. I am retired from our local Utility Board after 38 years service. I ride a Harley and enjoy life.</p>"
["_xfToken"] => string(8) "********"
["_xfRequestUri"] => string(24) "/account/account-details"
["_xfWithData"] => string(1) "1"
["_xfResponseType"] => string(4) "json"
}
}Any way I can fix this issue, or at least set it up so that the spam filter isn't active when users are editing profile fields?
It seems like it's very overly aggressive or something.