redsand

I’m sorry, but you are mistaken. WP-SpamShield works quite well with WooCommerce. If you are getting a 500 error, then WP-SpamShield is not what is causing the issue here. We prioritize ecommerce plugins like WooCommerce and do extensive testing to ensure compatibility.

This should be a support request, not a review.

I am 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?

We offer outstanding support. You should give us a chance to help you.

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

If the information provided doesn’t solve the issue for you, we can help 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:

• There’s a wrong way to give plugin feedback on WordPress.org
• How to Leave a Good Bad Review

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

Hey Sam,

No worries! We just want you to have a flawless experience. 🙂

– Scott

Hi Sam,

We responded to your support request via email. It makes it difficult to help you when you go back and forth between the main WP-SpamShield Support channel and here.

I’m glad you were able to sort out one of your configuration issues.

As noted in the Known Conflicts page, we do provide limited support for IIS:

What does limited support mean? It means we will do our best to make sure the code is compatible with as many systems out there as possible, and when there are issues, we will do our best to help, but being that there are a lot more things that can go wrong when PHP is running on IIS, you need to realize that the issue may not necessarily be the plugin but the server configuration…

Unfortunately, the nature of IIS just makes it a less-than-ideal system for running WordPress (and PHP in general). If a user requests help, we will do what we can to help.

However, with a properly configured server, users can run WordPress and WP-SpamShield quite smoothly, and most do.

Regarding your particular issue, please see the following from the Known Conflicts page’s IIS section:

If you are using IIS, remember that one of the Minimum Requirements for the plugin is that your server is configured to use an .htaccess file.

This can be done using Helicon Ape, which adds some valuable Apache functionality to IIS:

“It literally implements Apache configuration model and nearly all Apache modules in a single IIS add-on, not only making IIS compatible with Apache, but also extending it`s functionality by a number of highly essential features. Includes following modules: mod_rewrite, mod_proxy, mod_auth, mod_gzip, mod_headers, mod_cache, mod_expires, mod_replace and others.”

IIS’ equivalent to .htaccess is the web.config file. Both are directory-level overrides for certain server configuration settings.

Allowing two separate directory-level override files to function on a server at the same time is generally not a good practice and can cause conflicts and other problems. Yet, many IIS servers running WordPress end up doing this. If your site is properly configured to use .htaccess, you need to ensure that your site is configured to NOT use web.config in your WordPress site directory and below. This can be accomplished a number of ways, one being the AllowSubDirConfig setting ( https://blogs.msdn.microsoft.com/sroun/2014/11/13/allowsubdirconfig-clarification/ ), which is similar to the Apache setting AllowOverride.

Additionally, since you will be using .htaccess, URL Rewrite Module 1.1 should be disabled for the site, or alternatively, you can use the ‘iis7_supports_permalinks’ hook (with a function that returns ‘FALSE’) to tell WordPress that IIS does not support permalinks. Then it will fall back to the default setting of checking for an .htaccess file, and use the Apache style permalinks.

We are happy to help, but again, the best way for us to do that is if you continue the thread started through the plugin’s main support channel – the WP-SpamShield Support page. If you have any further questions or issues, please continue there.

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

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

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.

Hi helloeng,

That sounds like you have a configuration issue. Nothing was changed regarding that section of code in the latest update or any recent updates.

At the top of the support forum there is a sticky post that we ask users to read 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.

Hi jdcarlson,

We marked it resolved here, because there are no more steps for us to take here at the WordPress.org forums.

As noted in my response above, this is not our main support venue. Keep in mind that WordPress plugin developers are not obligated in any way to provide support, but yet we voluntarily provide some of the best support out there. (See the plugin reviews.)

It’s really not possible to provide the best support here at the forums because real site debugging involves getting into the technical aspects, which you wouldn’t want to be published publicly on a forum. That’s why the WP-SpamShield Support page is our main support venue. We’ll follow up with you primarily there from here on out.

Don’t worry…we’re taking care of you. 🙂

– Scott