Forum Replies Created

Viewing 15 replies - 496 through 510 (of 1,410 total)
  • Plugin Contributor redsand

    (@redsand)

    You’re very welcome. šŸ™‚

    Hmm, nothing should be causing the button to disappear like that. The default settings are for it to be visible 100% of the time, and there is nothing in the plugin that would make it invisible. The contact form fields can be customized via CSS settings on your site, so that would be the only way to make it disappear, unless you have a JavaScript doing something like that. All of the plugin’s CSS and JavaScript code is written and tested to be compliant with modern coding and browser standards.

    If the button is disappearing, that is most likely an issue specific to your site. (Possibly a CSS or JavaScript issue.) If you have any browser plugins that modify CSS or JavaScript, those could also potentially be a source of conflict, depending on your settings. (Also, be sure that you are using the most up to date version of a modern browser such as Chrome, Firefox, Microsoft Edge, etc. Older broswers may not render code correctly according to modern coding standards.)

    I would recommend checking your CSS settings (in theme/child theme/custom CSS/etc) to make sure you don’t have a CSS setting causing it to be invisible (hidden).

    If you check through that thoroughly, and still have issues, please see the FAQs and Troubleshooting Guide linked above, and then submit a support request, and we’ll be happy to help and investigate the issue.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi alistairg,

    I just wanted to say thank you for taking the time to post your review! I know that our plugin users are busy people, and your time is valuable, so it really means a lot to us when users post reviews and thoughtful feedback like this. šŸ™‚

    I’ll be happy to clarify on functionality and perhaps answer your concern.

    The plugin does not claim to filter swear words and such, for a couple reasons: to protect freedom of speech so that people can choose whatever language they like. Swearing is not offensive to everyone, and so we want people to be able to speak as they like. For example, for those who serve in the military (which I did) and other professions, swearing is merely a part of everyday language. Also, usage varies in different countries, and in English and other languages, swear words vary by location and dialect. I do understand how it may offend others though.

    However, if a site owner wishes to block swear words (or anything else), you can do this by enabling Enhanced Blacklist in the WP-SpamShield settings, and enter any swear words (or other words) that you want to block into the blacklist box.

    Administrators such as yourself will be whitelisted, so that would explain why things weren’t triggered when you tested it yourself. (This would remain true even after adding items to the blacklist.) You will need to have someone else test from another location, who does not have a user account on the site. You are not a spammer, and the plugin knows this. šŸ™‚

    We built over 100+ filters into the plugin to ensure it’s accuracy. I think you will find it quite accurate.

    We will add more information about this into the documentation to help people get the most out of the plugin.

    If we can help in any other way, please let us know. Feel free to submit a support request at the WP-SpamShield Support page. We also have a number of helpful FAQs and Troubleshooting Guide.

    I hope you have an outstanding week!

    – Scott

    Forum: Plugins
    In reply to: [Maintenance] WP-SpamShield

    @egabillat

    Excellent. Glad to help! šŸ™‚

    Plugin Contributor redsand

    (@redsand)

    Hi flyfisher842,

    I’ll be happy to help.

    This particular question has been answered a number of times already both here in the forums, and in the plugin documentation, so forgive me if I re-use the bulk of one of my earlier replies. šŸ™‚

    WP-SpamShield protects a lot more than comments & contact form pages (please see documentation for full list of features). Also, remember that jscripts.php is not just simple JavaScript…There are two layers of protection, so in addition to the JavaScript, it has an algorithmic layer. Things won’t function correctly if you stop it from loading as it’s designed to.

    However, you don’t need to worry about site speed with WP-SpamShield. The plugin is extremely well-optimized already, and no further optimizations need to be made to it. I do realize that not all plugin authors keep site speed optimization in mind…but we definitely do.

    Keep in mind that just because a script comes up on a list of scripts from an automated analysis tool labeled as “render-blocking”, that doesn’t necessarily mean it is actually slowing down your site. There is absolutely no hit to your site’s load time from jscripts.php.

    Installing WP-SpamShield actually helps speed up a site on the whole.

    We cover all the specifics in depth in two FAQs – please give these a read:

    This will answer your questions in detail. šŸ™‚

    Let us know if we can help with anything else.

    – Scott

    Forum: Plugins
    In reply to: [Maintenance] WP-SpamShield

    @egabillat, @fruitful:

    Perhaps I can help. (I’m the developer of WP-SpamShield) This has been listed on our known issues page for some time: http://www.redsandmarketing.com/plugins/wp-spamshield/known-conflicts/

    Maintenance alters the WordPress login process. Hooks from the standard WordPress login page process are missing in the Maintenance plugin. (Not saying this is bad, just explaining.) WP-SpamShield depends on these to check if it’s on a login/registration page, add code to the login page in order to validate, etc. This would affect compatibility of many plugins, not just WP-SpamShield. Keep in mind that WordPress login & registration process are somewhat tied together so some of the hooks affect each other.

    @egabillat:
    As of right now, to use these plugins together, be sure that you check the option for “Disable anti-spam for miscellaneous forms” in the WP-SpamShield settings.

    @frutiful:
    If you make sure it has all of the standard hooks that fire throughout the login process, it will help fix this issue. (For example, WP-SpamShield looks for ‘login_init’, ‘login_head’ hooks to detect login pages with non-standard names, to make sure it doesn’t run the Miscellaneous Form Anti-Spam check on login pages.) Otherwise the plugins will remain in conflict. If you would like to contact us to work on bridging compatibility gaps, we’ll be happy to help.

    Plugin Contributor redsand

    (@redsand)

    Hi royalmicer,

    I’ll be happy to help. We’ll look into that. Thank you.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi WebEndev,

    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.

    We will be happy to help you out. You will need to take the following steps:

    1. The Troubleshooting Guide and FAQs are the place to start.

      Please take a few minutes to work through these, as they solve over 90% of issues users have. (Please be sure to follow all the steps, not just read through them.)

      Once you have gone through the Troubleshooting Guide and FAQs, if that doesn’t solve the issue, we’ll need a bit more info from you on the specifics, and we’ll need to email back and forth, so you should move on to the next step.

    2. Submit a support request at the WP-SpamShield Support Form, our main support channel for the plugin. We have an excellent diagnostic process.

    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.

    Plugin Contributor redsand

    (@redsand)

    @cuta: I think you misunderstand what the plugin does. Your photo simply shows you saved a web page to your computer. Anyone can do that. That’s not what the plugin prevents.

    The plugin is proven to reduce automated scraping.

    As noted in the documentation:

    Unfortunately, no plugin can stop 100% of scrapers, but this plugin can dramatically reduce the amount of scraping that is done on a website.

    Plugin Contributor redsand

    (@redsand)

    Hi Nanowisdoms,

    The new issue you are experiencing would be a completely separate issue, and would not be caused by WP-SpamShield. C’mon now…give us a little credit! šŸ™‚

    Like I said above, if you have any further questions, please contact us by email as part of your existing support request, and we’ll be happy to help.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    We do appreciate the suggestions. Trust me, we’re quite familiar. šŸ™‚ Amazon SNS IP’s aren’t configured such that Reverse DNS lookups will show what Amazon SNS subdomains they match with, and the Amazon SNS subdomains in the SNS request don’t match the IP address (or even C-block) of the server that the request is originating from. It gets a lot more complex than most people realize. PayPal IPN for example, uses a much more standardized system, and makes it easier to validate. Just know that we are on top of it. šŸ™‚

    Plugin Contributor redsand

    (@redsand)

    No worries. One thing to note on this point you mentioned:

    Say for example like Amazon changes its API call, then knowing that amazon was a trusted source and not it’s not meeting the specs, you could alert the user this source has changed and is being rejected.

    We can’t mark Amazon as a trusted source, as a lot of bad activity (both spam and malicious traffic) does come from Amazon servers, as they are also a web host, and have a huge amount of IP addresses. So we have to go according to their spec in order to whitelist anything from them.

    Plugin Contributor redsand

    (@redsand)

    Thanks for sharing your feedback. We always listen to user suggestions.

    You are absolutely correct that we are concerned about our users, and will be committed to keeping the highest quality for the plugin.

    Plugin Contributor redsand

    (@redsand)

    Thanks for the update. Works fine.

    You’re very welcome. šŸ™‚

    Obviously Spam-Shield is sensitive to such things and is blocking more than just spam form submissions.

    This is all explained in the plugin documentation, and in the FAQs, and Troubleshooting Guide.

    Blocking spam form submissions is one thing, blocking transaction requests, like Amazon SNS bounce notifications, is quite another and impact operations that can affect one’s reputation.

    All WordPress . org plugin use is based on the principle that you take responsibility for your website. We are offering you a free gift, and how you choose to use it is up to you. If there is any risk to your reputation from an element of your website not functioning as you like, then you need to employ a full-time web developer to manage it. Please do not try to assign that burden to free plugin developers. We are merely creating something in hopes it may benefit the community. Keep in mind we are under no obligation to provide support, yet we do so anyway. All responsibility for a website belongs to the website owner, not anyone else.

    As we state in our documentation, we are committed to zero false positives, and when one is reported, we fix it immediately.

    How can we be better alerted that SpamShield is blocking non-form related visits — and what those are, so we can see if there any important ones being blocked?

    Logging is included in the plugin. It is explained in the documentation that the plugin blocks many types of spam. FAQs cover what to do if something was blocked that you believe should not have been.

    So Spamshield needs to first know/learn what is “normal” for the website before it starts filtering. And then, once it is filtering, it needs to create dashboard and email alerts when something “normal” is all of a sudden being blocked.

    Instead of doing this, we have the plugin only filter bad requests. What you had was a one-time issue that we corrected as soon as it was reported. Using the method you suggest assumes we would accept a certain amount of error within the plugin. We do not. If a legit issue gets reported, we fix it.

    How sensitive is the patch to changes Amazon may put in their URL requests?

    It follows Amazon Specs as outlined on: http://docs.aws.amazon.com/sns/latest/dg/json-formats.html

    If you have any further questions, please submit them to us via email on your support request thread on the WP-SpamShield Support page and we’ll be happy to answer them.

    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.

    Plugin Contributor redsand

    (@redsand)

    Fixed in version 1.9.8.7.

Viewing 15 replies - 496 through 510 (of 1,410 total)