Forum Replies Created

Viewing 15 replies - 406 through 420 (of 1,410 total)
  • The Firewall worked as intended on the vast majority of sites it was installed and we have not seen a decrease in usage of the plugin since it was introduced.

    It may work now (I don’t know)…but it certainly didn’t work reliably when you first introduced it. Disagree all you like, but if you go back to the support forum on that day, it was lit up like crazy. That’s why you had to release updates rapidly over the next day.

    Maybe one day we can make every single user of our software happy.

    That’s a bit of a rude statement…implying that only a few people had issues. Your support forum only has 101 of 386 support threads resolved. Over 2/3 are unresolved. That’s not something to ignore.

    You should take what I’m saying a bit more seriously. I’ve been a WordPress plugin developer for a decade, and am quite familiar with compatibility issues and the challenges of keeping all users happy. That’s not what the issue is. The issue is that you guys make drastic changes.

    @mellowvision,

    I agree with you on this one. WordFence has been making too many drastic changes between versions. Add WAF, take away cache…it’s just not stable. BTW, WP Super Cache coupled with Autoptimize (or another JS & CSS minification/caching plugin) make a good replacement.

    @wfasa,

    If you guys can understand…that the way you’re making huge changes with little or no notice…can really damage trust in your plugin. It has drastic affects on user sites. Many of us have clients who rely on us, and changes affect them, then they blame us, and so on. Not good.

    You really need to reconsider how you handle that. When you added the WAF in 6.1.1, it was a broken update and caused a lot of mayhem. (That’s when we left.) It was a major addition, and not well tested. Same with removing the cache. (Although, I never really thought it should have a cache…that never made sense.)

    • This reply was modified 9 years, 8 months ago by redsand.
    Plugin Contributor redsand

    (@redsand)

    I just wanted to follow up. We never received any further info from you.

    We ran some tests, and did find a bug in the contact form settings that affects version 1.9.9.3. This is fixed in version 1.9.9.4.

    Plugin Contributor redsand

    (@redsand)

    Hi davbarrio,

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

    • This reply was modified 9 years, 8 months ago by redsand.
    Plugin Contributor redsand

    (@redsand)

    We’re glad to help. πŸ™‚

    I’m so sorry to hear you were dealing with that for weeks. Wow, please don’t hesitate so long to ask for help in the future…We are here to help. As you can see, we solve problems pretty quickly. πŸ™‚

    You’re very welcome. Have a good one.

    Plugin Contributor redsand

    (@redsand)

    Hi @vitsippa,

    I’m sorry to hear that.

    The support request form works. If it didn’t accept your request, then please re-read the error message carefully and follow its instructions.

    I also clicked those links next to the form again and again and ticked the box, but it will not let me send my question.

    The point of that is not just to click the links, but to follow the steps listed before submitting the form. If it says that something was missed, then it is correct…something was missed. We regularly run tests and review the logs to make sure everything is working properly. We’ve reviewed the logs in this case as well and can confirm everything is working properly.

    All support requests need to go through the support page, not the contact form. (The contact form will not accept plugin support requests.)

    Since we do log all requests, we’ll have tech support email you and help you look into things.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    You’re welcome.

    I’m sorry to hear that. If they can’t explain why, then that should be a red flag. Sounds like it might be time to find a better host.

    Plugin Contributor redsand

    (@redsand)

    Hi ac1643,

    We’ll be happy to help you out. As we’ve noted on your previous support request:

    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.

    Please address your questions there so we can look into it for you.

    If the support form doesn’t submit, you just need to follow the error prompts, and then it will work just fine. πŸ™‚

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi MarietteJ,

    You’re fine with your current setup. What you have is an Apache/Nginx hybrid setup where Apache is the primary server and Nginx is the reverse-proxy in front of it. That’s a very good setup. In the plugin’s minimum requirements it says:

    Your server must be configured to allow the use of an .htaccess file. The vast majority of users will have no issue here, because most web hosts allow this by default. However, if yours does not, you will need to contact them and ask them to enable it on your site. If they won’t, then it’s time to get a better web host. WordPress loses a lot of functionality if you don’t have use of .htaccess enabled, so this is important for full functionality of WordPress and other plugins as well.) Note: By definition, a standalone Nginx server would not meet this requirement, but an Apache/Nginx hybrid setup would. (Nginx is setup as a reverse-proxy in front of Apache. This type of setup offers high-performance and is recommended.)

    So that would not be the problem.

    Our main support venue is the WP-SpamShield Support Page, not the forums here, so please head over there and submit a support request, and we’ll be happy to help.

    Before submitting the support request, please take a few minutes to work through the FAQs and Troubleshooting Guide completely, as they resolve over 90% of the issues users run into. Troubleshooting Guide Step 7 addresses your specific issue, but it’s important to go through all the steps as there may be other issues.

    – Scott

    Hi @lp5,

    WP-SpamShield shouldn’t be causing any issues with registration. We’ve done extensive testing to make sure the two plugins work together. If you’re having any problems, there may be a conflict or other issue. Please take a look at the FAQs and Troubleshooting Guide. If that doesn’t fix it for you, then you can submit a support request at the WP-SpamShield Support Page and we’ll be happy to help you get things working right.

    – Scott

    Hi @missile,

    Scott Allen here – developer of WP-SpamShield. WP-SpamShield wouldn’t block Google from accessing or indexing a page. (Talking about its normal behavior.) Of course, if there is a glitch, error, conflict, etc, anything can happen.

    We do a ridiculous amount of testing, and it’s a high priority for us to keep any plugin we develop from interfering with a site’s ranking.

    There may be an error happening under the hood, or a conflict. Please take a look at our FAQs and Troubleshooting Guide, and then fire off a support request. We’d like to look into this for you. You have my personal promise to respond to your support request ASAP.

    – Scott

    @alkerion,

    You’re welcome. πŸ™‚

    I hear you.

    Hi Alkerion,

    Ah, now that you mention it, I know why WP Approve User isn’t sending out the emails…an update in WordPress a few versions back made some changes with new user email functionality that broke a few plugins. We had to make changes to adjust for it too. I’ll see about putting a support request to the plugin dev. It would only need a small tweak to make it work again.

    The reason we recommend WP Approve User is that we’ve audited code in both plugins, and WP Approve User is written by one of the WP Core Developers, and it does have quality code. It does need an update though…As you mentioned…not getting the emails would make it useless. Who knows…maybe we can create a fork of it if it doesn’t get updated.

    You’re very welcome! Glad to help.

    – Scott

    Hi Alkerion,

    We reported this issue to the developer almost a year and a half ago, and even provided the code to fix the issue, and all communication attempts have been ignored. I wouldn’t expect a fix. I’d recommend switching to another plugin, such as WP Approve User.

    – Scott

    Plugin Contributor redsand

    (@redsand)

    Hi Alkerion,

    Thank you for reporting this.

    Yes, you are quite correct…these should not be capitalized. We will look into it further, and make appropriate fixes in the next release.

    – Scott

Viewing 15 replies - 406 through 420 (of 1,410 total)