redsand
Forum Replies Created
-
Forum: Plugins
In reply to: [WP-SpamShield] Anti spam plugin with contact form 7Hi vajeshrathor,
I understand how frustrating that can be. Yes, WP-SpamShield will automatically protect all Contact Form 7 forms. All you need to do is install the plugin and your CF7 forms will be protected. 🙂
– Scott
Forum: Reviews
In reply to: [WP-SpamShield] It has false positivesNo, that was not the order, WP shows the date for my first review. The day I installed this plugin I give you 5 stars, since you solved my issue at the moment. That’s why I wrote “Update:”.
Ah, I see. I wish they would give dates & times of the actual text update to clarify that. Well, I apologize for misunderstanding that. However, when you posted the support thread, you did not give us really any time to respond. I wish you would, simply because I think you would continue to have a 5-star view of the plugin. We have really high standards for it, so False Positives are simply unacceptable to us.
You’re right, it was an impulse after spending too much time doing the classification algorithm job manually. That is, going over 1000 comments in search of HAM messages.
Wow, I’m really sorry to hear that. I know from experience that this is no fun.
Yes, it is. HAM messages marked as SPAM is a False Positive.
For now let’s call this a difference of opinion. 🙂 I gave a more complete explanation in my most recent response to your thread. Give us a chance to prove you wrong. 🙂
Again, you’re right. I’m moving to 3-stars as a middle ground, but I can’t lie to community users either. What happened in my case it’s a fact, needs a fix, you need to understand my point too.
While we definitely appreciate that, more important to us than ratings is that you have a 5-star experience.
As I said, I did 5-star review first. Currently in WP there is no way to delete a review or put it on hold.
We do appreciate that. Unfortunately more confusion caused by the forums. Give us a chance to help you out, and get things back to 5-star performance for you. 🙂
– Scott
Forum: Plugins
In reply to: [WP-SpamShield] False PositivesHi Ivan,
As I mentioned in my first response, this is not our main support venue…the WP-SpamShield Support Form is. I marked it as resolved because there are no more steps for us to take here. (That doesn’t mean we are done helping you.) From here on out, it’s up to you to take the next step and work through the FAQs and Troubleshooting Guide, then submit a support request.
So my marking it as resolved, was only for right here on these forums…we are still very willing to help you fix your issue. It wasn’t intended to seem dismissive.
Keep in mind that in order for us to provide high-level support, we have to have a system, and the forums here do not accommodate that.
We’ve been doing tech support for this plugin and its predecessor for almost a decade. You really should trust me when I say that over 90% of the issues are resolved by working through the Troubleshooting Guide and FAQs.
We do an insane amount of testing on different servers, OS’s, PHP versions, and make sure it is compatible with top plugins, and especially caching plugins. WP-SpamShield detects nearly every caching plugin out there, and accommodates. So we’re already way ahead of you on W3TC. 🙂
The errors you’re experiencing mean that the JavaScript that adds the validation code to your site via jQuery isn’t getting added. I took a look at your site real quick, and I can already see a number of issues that the Troubleshooting Guide would help you fix.
Just a couple thoughts… It could have something to do with your minification. One of the biggest problems with minification is that it can quite often create jQuery problems. (We know a thing or two about this….we have a minification plugin, and we’ve worked with other minification plugin authors.) If you disable caching, clear your cache, and then disable minification (just during testing). Then submit a test comment to your site. jQuery has to be handled carefull in minification, and not all plugins do it right. It needs to stay in the header to maintain compatibility with all plugins.
For example, I don’t see the main jQuery file loaded anywhere in your minified files. That would cause the error you’re having. This is covered in FAQ #15: Make sure that you have not moved jQuery to the footer, and that no other plugins have interfered with jQuery.
I realize you have an opinion on what a false positive it. That’s perfectly fine. I’m not trying to insult your knowledge. However, when something is preventing a plugin from doing its job, that’s a conflict or configuration error, not a false positive. I make this distinction because these are issues that break other plugins as well, so they should be fixed. These aren’t algorithmic errors, these are technical errors. The error you’re having is in the JavaScript and Cookies Layer, not the Algorithmic Layer.
Trust me, I don’t want false positives any more than you do. We are committed to ZERO False Positives. When a user brings one to us that is a legit false positive, we usually fix it within a day. This does not happen very often. Like I mentioned above, it is extremely rare for users to still have the issue you’re having after working through the tech suport resources we’ve provided. If it doesn’t, just submit the support request, and we will help you diesgnose the issue. Give it a shot, we’re actually pretty nice people. 🙂
Since you’re a developer, working through the Troubleshooting Guide and FAQs won’t take you very long.
– Scott
The issue you had with WP-SpamShield was a configuration issue on your site, not false positives. Please see my response to your support request.
Forum: Reviews
In reply to: [WP-SpamShield] It has false positivesHi Ivan,
I’m sorry to hear that you had a frustrating experience.
However, I have to ask, why would you post a negative review without even submitting a support request first? From what I can tell, you submitted your support request after posting the negative rating.
We offer outstanding support. You should give us a chance to help you.
Update: You claim ZERO False Positives but I had 31 false positives (7 users) from 989 spams. I had to uninstall it since real comments were being blocked.
Yes, the plugin’s claim about zero false positives is still accurate. What you’re describing is not a false positive</em>.
As noted in FAQ #3:
In the rare event you are getting reports from multiple users that their comments are being blocked, these are not false positives — it means you most likely have a conflict that is preventing the plugin from functioning properly or there is another issue in play.
There is an FAQ that applies specifically to your situation: FAQ #9 – Q: I think a legitimate user or comment may have been blocked. What’s going on here and what do I do?
This particular error is not likely to be a problem with the plugin.
Please note that it’s extremely rare for users to have this particular issue after working through the Troubleshooting Guide and FAQs.
Please take special note of Troubleshooting Step 9 and FAQ #9 as they relate specifically to the issue you are dealing with, and will give you the steps to proceed forward.
From the Troubleshooting Guide:
If this message comes up consistently even after JavaScript and cookies are enabled, and after clearing your browser cache, then there most likely is an installation problem, site configuration issue, plugin conflict, or JavaScript conflict.
It is important for all plugin users to read the documentation. We have put together some very helpful and thorough troubleshooting documentation. Please take a few minutes to work through the Troubleshooting Guide and FAQs, as these solve over 90% of issues users have.
If the information provided doesn’t solve the issue for you, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so please head over to the WP-SpamShield Support Form (our main support channel), and take a moment to fill out a support request. That will allow us to help you diagnose this, find out what the real issue is, and get things working right for you.
Please ask yourself this…When developers spend so much time developing free plugins for the WordPress community, is it really ok to post a 1-star review without making any reasonable effort to receive support? That’s simply not the right way to handle things.
If you have an issue with something, submit a support request first, and give the author time to respond. We provide free support for our plugins…all you have to do is submit a support request at the WP-SpamShield Support Page. We provide some of the best support out there.
You might want to take a moment to check out these two posts:
I would ask that you reconsider your rating, as it simply isn’t accurate or fair. It can be updated by going to: https://wordpress.org/support/view/plugin-reviews/wp-spamshield#postform
Reviews like this simply do not help the global WordPress community.
– Scott
Forum: Reviews
In reply to: [RS System Diagnostic] Great tool for debuging!Hi Anty,
Thanks for taking a moment to leave some positive feedback! I’m glad to hear you’re finding this a useful tool.
Regarding the cosmetic improvements such as colored warnings, I absolutely agree with you, and those are in the works for the future. We’re going to add more functionality that makes it even easier to help resolve issues the plugin points out, along with tips and options for how to do it. 🙂
If you have any more ideas, we’re glad to hear them.
Have a good one!
– Scott
Forum: Plugins
In reply to: [WP-SpamShield] False PositivesHi IvanRF,
I’m sorry to hear about the issue you’re having, and I’ll be happy to help.
At the top of the support forum there is a sticky post that we ask users to read first because it guides you to excellent troubleshooting options we have already put together for our plugin users.
Please take a few minutes to work through the Troubleshooting Guide and FAQs, as these solve over 90% of issues users have. (Please be sure to follow all the steps, not just read through them.)
Hi, you claim ZERO False Positives but I had 5 false positives (from 3 different users) over 728 spams.
Yes, the plugin’s claim about zero false positives is still accurate. What you’re describing is not a false positive.
As noted in FAQ #3:
In the rare event you are getting reports from multiple users that their comments are being blocked, these are not false positives — it means you most likely have a conflict that is preventing the plugin from functioning properly or there is another issue in play.
There is an FAQ that applies specifically to your situation: FAQ #9 – Q: I think a legitimate user or comment may have been blocked. What’s going on here and what do I do?
This particular error is not likely to be a problem with the plugin.
Please note that it’s extremely rare for users to have this particular issue after working through the Troubleshooting Guide and FAQs. We ask that all plugin users please make reasonable effort to do some troubleshooting on their own, as there are far more of you than there are of us. 🙂
Please take special note of Troubleshooting Step 9 and FAQ #9 as they relate specifically to the issue you are dealing with, and will give you the steps to proceed forward.
From the Troubleshooting Guide:
If this message comes up consistently even after JavaScript and cookies are enabled, and after clearing your browser cache, then there most likely is an installation problem, site configuration issue, plugin conflict, or JavaScript conflict.
If the information provided doesn’t solve the issue for you, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so please head over to the WP-SpamShield Support Form, and take a moment to fill out a support request. That will allow us to help you diagnose this, find out what the real issue is, and get things working right for you.
– Scott
Please note that the WP-SpamShield Support page is our main support venue, not the WordPress forums here, so that will always be the best way to get a quick response and resolve any tech support issues.
Forum: Plugins
In reply to: [WP-SpamShield] Login issueAt the top of the support forum there is a sticky post that we ask users to read first because it guides you to excellent troubleshooting options we have already put together for our plugin users.
Please take a few minutes to work through the Troubleshooting Guide and FAQs, as these solve over 90% of issues users have. (Please be sure to follow all the steps, not just read through them.)
If the information provided doesn’t solve the issue for you, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so please head over to the WP-SpamShield Support Form, and take a moment to fill out a support request. That will allow us to help you diagnose this, find out what the real issue is, and get things working right for you.
– Scott
Please note that the WP-SpamShield Support page is our main support venue, not the WordPress forums here, so that will always be the best way to get a quick response and resolve any tech support issues.
Forum: Plugins
In reply to: [WP-SpamShield] After latest update, cron job errorsOk. No worries. 🙂
Just go ahead and submit the support request, and we’ll be happy to help you fix your issue.
** Please keep in mind that the WordPress forums here are not our main support venue…The WP-SpamShield Support page is our main support venue. Please direct your questions there, as that will always be the best way to get a quick response and resolve any tech support issues.
Forum: Plugins
In reply to: [WP-SpamShield] After latest update, cron job errorsYes…?
I think that’s fairly self-explanatory…no?
You checked the box saying you have worked through these, but you haven’t visited the Known Issues and Plugin Conflicts page yet. This is step 2 of the Troubleshooting Guide. Please go back and work through these completely before submitting a support request.
We offer extensive support, but as noted above in my first response, users do need to work through the Troubleshooting Guide and FAQs first.
It’s simply a form validation feature. If you got that response, it means you checked the validation box saying you had worked through the Troubleshooting Guide and FAQs, but hadn’t yet visited one or more of the pages…so it just means you need to go back and finish up. Then submit your request when you’re done.
Forum: Plugins
In reply to: [WP-SpamShield] After latest update, cron job errorsForum: Plugins
In reply to: [WP-SpamShield] After latest update, cron job errorsWhat browser and OS were you using when you got the 403 error?
I stand by what I said.
I’m sorry, but the things you’re saying simply are not accurate. You’re miss-stating the facts…again. (And yes, I have repeated myself, as I’ve had to do many times with you.)
And I do take issue with sending evidence being considered harassment.
Sending of “evidence”? You made a video…to prove to us that your site had an issue. Ok. What exactly were you trying to accomplish? We understood this from the beginning….we acknowledged your site’s issues. This “sending of evidence” was the continuation of the harassment that you had already been engaged in. You had already been asked not to contact us multiple times by this point.
We had to ban you from tech support because your support request turned into abusive rants, and it became clear that you did not want help, you just wanted to take out anger on someone.
I could refute everything you’re saying point by point, but I’ve already covered these issues with you before, both in private, and on your previous tirade here on the forums, so we’d go in a big circle…again.
We absolutely did bend over backward to help you. We went above and beyond with you. But instead of being grateful, or even mildly appreciative of the fact we spent hours trying to help you, you refused to listen, and wanted to rant. And, yes, you absolutely were abusive to support. And yes, you absolutely have been harassing us.
We’ve literally been dealing with you since November of last year. Now it’s time for you to stop harassing us and move along.
I’m not going to argue with you further.
– Scott
We bent over backward trying to help you. The bottom line is that you were unwilling to follow all of the diagnostic steps we asked you to follow.
You’re using outdated PHP versions, and outdated WordPress versions. After we asked you to use WP_DEBUG to diagnose things, there were no WP-SpamShield errors, but many errors in your theme and other plugins, but yet still want to blame the issue on WPSS. We made suggestions for you to work through to help fix these issues. Diagnosing issues is a process, and if you follow the steps we ask, you can fix things. If you don’t want to try what we suggest, then there is no more we can do to help you.
The reason we suggested that you change hosts is that you told us they were unwilling to upgrade your server past PHP 5.3, which reached EOL two years ago. It’s one thing if you were choosing to use 5.3, but the fact that the highest PHP version they offer is a dead, unsupported branch, was a sign of bad hosting.
The title of your review reads:
Does what it should, but also what it shouldn’t, and dev doesn’t admit bugs
“Dev doesn’t admit bugs”…? When a user submits a bug to us, we absolutely admit it, and we try to fix it within a day. The issue you were having, was not due to a bug in the plugin, but rather issues specific to your site. We tried to help you understand this, but you seemed quite unwilling to hear this.
I’m sorry, but the inner workings of WordPress and PHP simply do not work the way you think they do.
As we told you several times, if you have a 24 second delay, then you have a serious configuration issue or PHP error happening on your site server. Nothing should ever take that long. We have optimized the plugin to be extremely efficient, as noted in the FAQs with benchmarks and explanations.
No one on our end ever denied that you had a problem on your site…I’m not sure why you felt the need to go and record a video to prove the fact after we already acknowledged that you had an issue, and worked with you for several hours over the course of several days to help you diagnose the issue..
You keep saying that it’s a WPSS issue and that a recent update caused the issue, but we literally did not change any code in the plugin that could cause the issue you’re talking about.
We’ve been diagnosing these issues on this plugin and its predecessor for almost a decade. If we tell you are incorrect, and that things simply don’t work the way you are saying, it’s not an insult. It’s a simple, unemotional, statement of fact. We’ve done tech support on thousands of sites, all kinds of server setups, and each of us has at least a couple decades of experience in this field. We do happen to have an excellent system for tech support diagnosis. If you don’t want to accept our expertise, that’s perfectly fine, but that’s your choice. Our only goal is to help you have a flawless experience.
After we tried extensively to help you for several days, you became abusive to tech support, and we had to cut it off. That is simply not acceptable.
Say what you like, but you absolutely were abusive to tech support.
Yes, we did ban you from tech support because you became abusive. After that, you continued to harass us, and we were forced to go a step further and ban you from the site. Banning is not something we take lightly. There have been very few occasions where we have ever had to do that. Someone has to reach a high level of abusiveness for us to do that. Something for you to think about.
The things you say here are simply not true:
Recent versions of WP-SpamShield do things they shouldn’t.
No offense, but this is a matter of opinion, not fact. The plugin does exactly what it says in the description. If you don’t like the philosophy behind the plugin, that’s perfectly fine. You are free to use it or not. If you want to develop your own anti-spam plugin, you can take it in any direction you like. We are using our expertise to guide the development of this plugin.
…the developer refuses to admit it and treats anyone pointing it out as dirt.
This is where I will take a strong exception to what you’re saying…we have never treated you like dirt, and we have never treated any of our plugin users “like dirt”. Saying something like that is simply slandering us and not even remotely true. It’s a bit unbelievable you can even say that, especially after we spent as much time as we did to try and help you.
We have a clean conscience that we only tried to help you. You’re free to accept that or not.
– Scott
Forum: Plugins
In reply to: [WP-SpamShield] After latest update, cron job errorsAt the top of the support forum there is a sticky post that we ask users to read first because it guides you to excellent troubleshooting options we have already put together for our plugin users.
Please take a few minutes to work through the Troubleshooting Guide and FAQs, as these solve over 90% of issues users have. (Please be sure to follow all the steps, not just read through them.)
If the information provided doesn’t solve the issue for you, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so please head over to the WP-SpamShield Support Form, and take a moment to fill out a support request. That will allow us to help you diagnose this, find out what the real issue is, and get things working right for you.
– Scott
Please note that the WP-SpamShield Support page is our main support venue, not the WordPress forums here, so that will always be the best way to get a quick response and resolve any tech support issues.