redsand
Forum Replies Created
-
Forum: Plugins
In reply to: [WP-SpamShield] Support form malfunctioning while trying to report issuesHi @petriknz,
I’m sorry to hear about the issue you’re having. During the time you had the issue with the support form, we were doing some site maintenance. Unfortunately there is never a perfect time for that. Everything is working fine again.
I checked the site logs and was able to grab your email address from the support request. I had tech support email you, so keep an eye out for that. We’ll be glad to help you out and resolve the issue.
– Scott
Forum: Reviews
In reply to: [WP-SpamShield] PleasedHi @mrgaric,
We really appreciate you taking a minute to let us know how the plugin is working for you.
Hearing stories of WP-SpamShield annihilating spam really makes our day! 🙂
If you ever need any help, just let us know. Have a good one!
– Scott
Forum: Reviews
In reply to: [WP-SpamShield] Awesome Plugin!Hey there @bciintegrated,
Thanks for the great review and for letting us know! 🙂
Have a good one!
– Scott
Forum: Plugins
In reply to: [WP-SpamShield] Incompatible with Jetpack Comments 5.0Hi @iotus,
We received your support request at the WP-SpamShield Support page. We ask that users not post duplicate support requests, as that only reduces our ability to provide timely tech support. Thanks!
Just a quick note regarding your follow up comment:
That’s not something we’ve ever seen or had a report of. We’ll help you address that issue as well though.
– Scott
Forum: Plugins
In reply to: [Gwolle Guestbook] Some Entry´s on Settings Page don`t workHi Marcel!
Sure…if you like, an FAQ would be good.
Basically if WP-SpamShield is active and its Anti-Spam for Miscellaneous Forms is not disabled, it will handle the anti-spam for Gwolle GB automatically, and any anti-spam features in Gwolle GB are unnecessary, and will be adjusted automatically to prevent conflicts.
We’ve got your back. 🙂
All of WP-SpamShield’s protection features are available to your plugin’s users.
If you activate the two plugins together, you can test it out. Just modify anti-spam settings in the Gwolle GB settings, and if WP-SpamShield will auto-correct anything that would conflict. We did a lot of testing to make sure everything works smoothly. If users don’t want to use WP-SpamShield’s protection for Gwolle GB, then all they need to do is disable Anti-Spam for Miscellaneous Forms in WPSS settings.
We’ll be happy to help fine-tune anything, or answer any questions if you would like…We have a compatibility page for other developers here. You can use the contact form at the bottom to get in touch with us directly.
Hope that helps!
– Scott
Forum: Plugins
In reply to: [Gwolle Guestbook] Some Entry´s on Settings Page don`t workHi @simmsen,
All CAPTCHAs should be deactivated when using WP-SpamShield, as they are not needed, and will cause conflicts. WP-SpamShield supports Gwolle GB, and protects it automatically from spam, without needing any kind of CAPTCHA. Please see Troubleshooting Guide Step 14 for more info. If you have any further issues, we’ll be happy to help.
– Scott
Forum: Plugins
In reply to: [WangGuard] Alternatives going forward with or without WanguardHey John!
No problem. 🙂
Sounds good…we’re ready to help when you do. I’m confident we can help you get everything running smoothly.
Forum: Plugins
In reply to: [WP-SpamShield] Nginx no longer working…unless I have missed another nginx-issue you have mentioned?
Yes.
Like I said:
This is not a support issue.
Our support page is here if you’d like to discuss further.
Forum: Plugins
In reply to: [WP-SpamShield] Nginx no longer workingWhat am I missing though, what part of Apache is a necessity for this plugin to work?
I tried to discuss that with you couple months ago. You did not seem open to hearing any of what I had to say.
P.S. this should remain open for anyone to see and not become a personal exchange of emails, as nginx is a common webserver and others might be affected and want to understand as to why explicitly nginx is not supported.
Please see the support forum guidelines:
…the forums are not the appropriate place for starting topics unrelated to support issues.
This is not a support issue.
Our support page is here if you’d like to discuss further.
Forum: Plugins
In reply to: [WP-SpamShield] Nginx no longer workingHi @davidh64,
Again: Aside from .htaccess (which does not contribute to the functionality and ability to block spam), no Apache-specific features are used that would actually require Apache to be used with this plugin.
I’m sorry that you feel this way, but that is simply not accurate. I think you might be working with incomplete information.
We’ve made an effort to answer your questions previously and discussed the issue with you at length.
This is a two month old thread. I’m not sure what more can be accomplished here, as you don’t seem to be requesting support. As noted previously:
At this point though, this thread is a discussion of a disagreement with our development decisions rather than a support issue.
If you would like to discuss further, or ask specific questions, please contact us at the plugin’s support page, and we’ll be happy to help.
Forum: Plugins
In reply to: [WangGuard] Alternatives going forward with or without WanguardHey @johnp,
I’m sorry to hear that you’re having issues with spammers even with WP-SpamShield installed.
It’s extremely rare for anything to get by WP-SpamShield like that. The only time we’ve seen it is when there is a conflict. There are one or two plugins out there that cause the registration process to bypass any anti-spam plugins.
I’d recommend checking out our Troubleshooting Guide, and Known Issues and Plugin Conflicts pages.
I’m not sure that there are any plugins out there that are more effective at blocking registration spam.
If you would like to submit a support request, we can help you resolve the issue in no time. 🙂
– Scott
Forum: Reviews
In reply to: [WP-SpamShield] Blocking tons of Spam!Hi @arfestina,
Thanks for taking the time to share your good experiences with the plugin!
We’re glad we can help keep spam away from your site. 🙂
– Scott
Forum: Plugins
In reply to: [Contact Form 7] Forms submit errors (JavaScript and Cookies)We only recommend using that as a temporary measure. If you’re still having any issues, we’ll be happy to help you resolve them — just submit a support request.
We have agreed that some VPN endpoints and network locations are blocked and this is written with some experience.
WP-SpamShield does not restrict site access. A network location would only be blocked from posting if these have a proven track record of malicious activity, and these are being used primarily for hacking. Again, the plugin does not block site access, only posting.
This is not a “major issue with the site configuration…That’s a site management issue,” it is also not true that “The plugin gives admins free reign to do what they need to do.” since these rules are enforced and not configurable.
The plugin’s filtering functions literally do not run when an admin user is logged in. There is no need to configure since they are free to do anything. If you’re having an issue, then the user is not an admin, or not logged in. So, yes, there would be a major issue with site configuration. Our tech support team would be happy to help you fix this, but please don’t blame that issue on the plugin.
However when genuine customers or the shop owner is blocked…
Let’s just stop right there…that does not happen. The shop owner is not blocked under any circumstances. Again, when a site owner is logged in, the plugin’s filtering functions literally do not run. Programmatically, what you’re describing cannot happen.
The shop owner cannot explain to the customers who never arrived that they might need to change their network connection as per advice from RedSand support. And the limited rules configurability and automatic-switch-off logging somewhat obscure any underlying problem.
You’re arguing theoretical issues that you’ve never actually seen or experienced, and that could never happen. The plugin does not block anyone from visiting a site. That’s not how the code works. There are no “customers who never arrived”. We have multiple built-in protections for online shops to make sure that all ecommerce runs smoothly. That is a very high priority for us.
True, I don’t have enough data to tell what percentage of genuine users from Eastern Europe or Russia etc might be blocked due to the rules implemented, maybe you do.
No users are being blocked, from eastern Europe, Russia, or elsewhere.
Hence my conclusion: really good at blocking, may want to be careful depending on the target audience for your site.
I realize you want to make a philosophical argument, but the things you’re saying simply are not true. The code simply does not work like you’re saying. Please stick to facts and your own actual experiences.
If you have any tech support issues, we will be happy to help, but please do not spread rumors or theorize about what you think the plugin would do.
Forum: Reviews
In reply to: [WP-SpamShield] Does a job on spam – AND CPU utilization tooThe beauty of reviews is that it’s a system for users to report their experiences.
No one is disputing that.
We don’t dispute a bad review if it’s warranted. If you had contacted us, and we treated you badly, or were not able to fix something, it would be understandable.
One of the major reasons that it is essential to submit support requests before negative reviews, is that most of the time that users come in with a support issue, and they are confident it is due to a specific thing, it actually ends up being caused by something else.
Our diagnostic process is very in-depth and scientific — think of it like WordPress CSI. We go much deeper into the guts of WordPress, PHP, databases, servers, etc than most users would be able to, so we always get to the bottom of things, and identify the real issue.
Our tech support team members are the same people who develop the plugin — seasoned experts — not like Level 1 techs you might talk to elsewhere. So, it’s a whole different experience, and one reason why our tech support is so good.
If people skip the diagnostic process, and then post negative reviews online with their conclusions, all it does is spread inaccurate info, and makes it more confusing for others in the future. There is a lot of incorrect info floating around online and in forums like this, and it makes it that much more difficult for the WordPress community to solve problems in the future.
However, if they do go through the support process first, and still want to post a negative review, at least it will be more accurate, and more helpful to others.
Open source only works if everyone helps build up the overall community. Even if users don’t build the software themselves, at the very least, when a problem arises, they can submit support requests and contribute by helping the developer improve the software. By extension, this helps the entire community.
Think of how many developers will get discouraged and not want to contribute to open source any more if the community is run in a way that encourages negative reviews without support requests. That’s a bit of a toxic environment. We don’t get especially discouraged personally when this happens, but many will, and it has happened many times. There are some very talented young developers who no longer build open source software, because of repeated situations like this.
Even if you are unwilling to reconsider your review, please take a few minutes over the next couple days to at least read these two posts mentioned above:
Just something to think about for the future. 🙂
It’s great for you to “fight the good fight” like you do; it lets people know you really care about the performance of your product. Keep it up.
Thank you…we absolutely will continue to push for excellence, and will always work to better our products.