redsand

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.

@cavalary,

We bent over backward trying to help you. The bottom line is that you were unwilling to follow all of the diagnostic steps we asked you to follow. You’re using outdated PHP versions, and outdated WordPress versions. After we asked you to use WP_DEBUG to diagnose things, there were no WP-SpamShield errors, but many errors in your theme and other plugins, but yet still want to blame the issue on WPSS. We made suggestions for you to work through to help fix these issues. Diagnosing issues is a process, and if you follow the steps we ask, you can fix things. If you don’t want to try what we suggest, then there is no more we can do to help you.

The reason we suggested that you change hosts is that you told us they were unwilling to upgrade your server past PHP 5.3, which reached EOL two years ago. It’s one thing if you were choosing to use 5.3, but the fact that the highest PHP version they offer is a dead, unsupported branch, was a sign of bad hosting.

As we told you several times, if you have a 24 second delay, then you have a serious configuration issue or PHP error happening on your site server. Nothing should ever take that long. We have optimized the plugin to be extremely efficient, as noted in the FAQs with benchmarks and explanations.

You keep saying that it’s a WPSS issue and that a recent update caused the issue, but we literally did not change any code in the plugin that could cause the issue you’re talking about.

We’ve been diagnosing these issues on this plugin and its predecessor for almost a decade. We’ve done tech support on thousands of sites, all kinds of server setups, and each of us has at least a couple decades of experience in this field. We do happen to have an excellent system for tech support diagnosis. If you don’t want to accept our expertise, that’s perfectly fine, but that’s your choice. Our only goal is to help you have a flawless experience.

After we tried extensively to help you extensively for several days, you became abusive to tech support, and we had to cut it off. That is simply not acceptable.

We have a clean conscience that we only tried to help you. You’re free to accept that or not.

– Scott

exedesign2,

The sarcasm isn’t necessary. We genuinely try to help all our users. Plugin authors are not required to provide support of any kind, yet we provide some of the best support out there. You might want to be reconsider being snarky to people that you’re asking for help from.

As I mentioned in my first response, this is not our main support venue…the WP-SpamShield Support Form is. I marked it as resolved because there are no more steps for us to take here. (That doesn’t mean we are done helping you.) From here on out, it’s up to you to take the next step and work through the FAQs and Troubleshooting Guide, then submit a support request.

The plugin does not have a generalized conflict with Gravity Forms. We have done a lot of testing to ensure compatibility. If there is an issue, it is something specific to the site that you are referring to.

On forums it is only possible to provide general info, and it is simply not possible to provide good support. However, through the link I gave you, you can get excellent support. There is no reason to keep working on it…we’ll be happy to help you fix it.

If you simply submit a support request, as I mentioned, we will help you figure out what the real issue is. We have an excellent diagnostic process, and users are often surprised to find that the issue was not what they thought.

– Scott

Eh great plugin by the way. I understand it’s a lot of time to make and support. Thanks, 🙂

Thank you. 🙂

Hi alexlii,

Thank you. 🙂

These are covered in more depth in the plugin documentation, but I’ll give you the short answer here.

1. There are different implementations of Nginx, so it depends on the type of install. The type of install we recommend for WordPress is a hybrid Nginx/Apache setup, with have Nginx as a reverse-proxy in front of an Apache server. WP-SpamShield is compatible with this type of setup.If your site is running a standalone Nginx setup, it will not be compatible. As noted in the plugin’s Minimum Requirements, your server must be configured to allow the use of an .htaccess file, which standalone Nginx does not have.
2. Yes it does work on Multisite. It should be noted that it must be activated individually per site, not network activated.

Keep in mind that if you’re running standalone Nginx, there are going to be a lot of limitations on what plugins you can use, as many use .htaccess and lose at least some functionality without it. We did a survey of top WordPress plugins and found that more than 40% of the top 20 plugins lost significant functionality on Nginx because it doesn’t use .htaccess. See this for more info on WP-SpamShield and Nginx. So just be aware of that.

Hope that info helps!

– Scott

Hi alicrosswrites,

Please revisit the plugin’s description…that’s not what this plugin does.

What you’re asking is more of a site design issue.

You use the native WordPress feed URL in all code in your site (not the FeedBurner URL), and then this plugin will redirect users to the FeedBurner feed.

So, to add a subscribe widget, you can either use a Text widget, or find a plugin that adds the specific functionality you’re looking for.

Hope that helps!

– Scott

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.