Forum Replies Created

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

    (@redsand)

    You’re welcome. πŸ™‚

    I haven’t checked the WP core changelog specifically for that, but it’s possible that a change was made recently to disable autocomplete on forms as a potential (debatable) security/privacy enhancement.

    Plugin Contributor redsand

    (@redsand)

    Hi rperrett,

    That wouldn’t have to do with WP-SpamShield. That would have to do with WordPress itself setting a cookie that stores the user info in the browser, and whether autocomplete is disabled on your forms. WP-SpamShield doesn’t interactive with that process, so it wouldn’t be the source of your issue here. You may have changed some settings on your site, or have another plugin or script that is affecting that.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    No worries! πŸ™‚

    Plugin Contributor redsand

    (@redsand)

    You updated to 1.9.7.1.1 just now? That shouldn’t happen if you have things set properly in your settings. Since you’re still having the issue, as I mentioned, I’ll need you to contact us through our support page.

    Plugin Contributor redsand

    (@redsand)

    Made a quick update. Try 1.9.7.1.1. You should have no problems now. πŸ™‚

    Plugin Contributor redsand

    (@redsand)

    Hi Sean,

    Ah, see that’s a whole different animal. That would have been helpful if you had mentioned that in the first place. πŸ™‚

    I’ll be happy to look into that for you. However I will need you to contact us through the support form as mentioned, as this is not our main support venue.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi spirish,

    The plugin isn’t broken with https enabled. If you’re getting that error, it means you have a configuration error in your main settings page.

    On the main WordPress settings page (“General Settings”), both URL fields (“WordPress Address (URL)” and “Site Address (URL)”) need to have the same URL scheme (“https://” or “http://”) – they have to match.

    That error message you are getting (and subsequent deactivation) from WP-SpamShield is happening because it is doing error checking, and found the problem in your settings: One URL is “http://” and one is “https://”, which will present problems for your site, and prevent certain things from working, including WP-SpamShield. If you fix that error in the settings (so both should start with “https://”)…everything will work again.

    If you have any further issues or questions, please submit a support request at the WP-SpamShield Support Form (our main support venue), and we’ll be happy to help you out.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi Kristie,

    I’m sorry to hear about the issue you’re having and I’ll be happy to help.

    If you haven’t had a chance to yet, please take a few minutes to work through the Troubleshooting Guide and FAQs, as these solve 90% of issues users have.

    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 those don’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 take care of this as quickly as possible for you.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi Birgit,

    21 is greater than 3, so unfortunately 5.3.3 is much older than 5.3.21, and you’re not above the requirement.

    Please see the PHP Releases for more info.

    PHP 5.3.3: http://php.net/releases/#5.3.3 (Released: 22 July 2010)
    PHP 5.3.21: http://php.net/releases/#5.3.21 (Released: 17 Jan 2013)

    PHP 5.3.3 is 6 years old. PHP 5.3.21 is 3 years old.

    Please upgrade to a newer version of PHP as soon as possible. PHP 5.5, 5.6, or higher are recommended.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    When this thread was started, there was a specific conflict that has been fixed a long time ago.

    If you experience a JavaScript and Cookies error now, that is a general issue, that can easily be fixed. You need to work through the Troubleshooting Guide and FAQs. Please see my original response above. If the issue continues after you’ve done that, then please submit a support request at the WP-SpamShield Support page. (Link is in my original response as well.)

    Hey Malcolm!

    You are very welcome! Thanks for your great communication via email and working together to create a solution. πŸ™‚

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi lelik72,

    The plugin would not reduce your Google Speed like that. If it’s going down, then there is a problem on your site…likely either a plugin conflict, or configuration issue. For example, sometimes people install two minificaiton plugins, not realizing they won’t work together. Ther resulting code can be a mess. The problem isn’t either plugin, but the combination of the two.

    I have to ask, why would you post a negative review without even submitting a support request first?

    Right on the main plugin page we have this notice:

    As with any JS/CSS minification & caching plugin, it’s important to test, test, test. Because of the type of plugin it is, this plugin may not work for every site out there, but that does not mean the plugin is broken. If you have any issues, please submit a support request so we can look into it and make it as compatible as possible for everyone.

    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 WordPress Plugin 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.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Not the same issue at all. That was a conflict with another very specific plugin, that we issued a fix for a long time ago.

    Please follow my instructions above. What I said really is true.

    That particular error, can affect your entire site, not just WooCommerce. It can affect comments, contact forms, registrations, etc. In every case it boils down to one of a very few basic issues. The documentation we have put together covers these.

    It is very rare that we have users continue to have that issue (JavaScript and Cookies error) after reading the plugin documentation, and working through the Troubleshooting Guide and FAQ’s.

    Plugin Contributor redsand

    (@redsand)

    Hi egabillat,

    I’m sorry to hear about the issue you’re having and I’ll be happy to help.

    If you haven’t had a chance to yet, please take a few minutes to work through the Troubleshooting Guide and FAQs, as these solve 90% of issues users have.

    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, then there most likely is an installation problem, site configuration issue, plugin conflict, or JavaScript conflict.

    If those don’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 take care of this as quickly as possible for you.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi Totobuvika,

    I’m sorry to hear that you had an issue.

    However, I have to ask, why would you post a negative review without even submitting a support request first?

    The issue you are experiencing is covered in the Troubleshooting Guide and FAQs, along with the causes, and solutions to fix the issue. It’s not an issue with the plugin.

    It is important for all plugin users to read the documentation. 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.)

    Please take special note of FAQ 9, as it specifically addresses your issue:
    Q: I think a legitimate user or comment may have been blocked. What’s going on here and what do I do?” Read the full FAQ: http://www.redsandmarketing.com/plugins/wp-spamshield/faqs/#faqs_9

    Excerpt from the FAQ:

    …There could be a plugin conflict that is preventing the plugin from working properly. (Especially if you get a Javascript and Cookies error message when these are enabled.) Obviously we work hard to keep this to a minimum, but it is possible that that it could happen on rare occasion. Please see the Troubleshooting Guide for info on how to test for this… The plugin may be installed incorrectly or there may be an issue with the installation. This would keep the plugin from working properly. (This could also cause a Javascript and Cookies error message similar to previous point.) Please see…

    For the rest of the FAQ, please click here to read it.

    From the Troubleshooting Guide:

    If this message comes up consistently even after JavaScript and cookies are enabled, then there most likely is an installation problem, site configuration issue, plugin conflict, or JavaScript conflict.

    For the rest of the Troubleshooting Guide, please click here to read it.

    If the information provided doesn’t solve the issue for you, we can help you you fix the issue on your site. We’ll need a bit more info from you on the specifics, and will 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.

    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. Reviews like this simply do not help the global WordPress community.

    – Scott

Viewing 15 replies - 661 through 675 (of 1,410 total)