redsand
Forum Replies Created
-
Forum: Reviews
In reply to: [RS System Diagnostic] Exceptional!Forum: Plugins
In reply to: [WP-SpamShield] NGiNX server?It’s all good…I knew what you meant. I read “fastest”. I think you’ll find the info interesting. At least it will give you another insight.
True story. 🙂
Take care. Hopefully we’ll talk soon.
– Scott
Forum: Reviews
In reply to: [WP-SpamShield] It’s nearly perfectForum: Reviews
In reply to: [WP-SpamShield] Absolute Must Add Plugin!Hi @lt3030,
I just want to say thank you for the wonderful review. It does our heart good to hear real life examples of stopping spam like this. 🙂
We’ll keep working hard to keep spam away from your websites. Take care!
– Scott
Forum: Plugins
In reply to: [WP-SpamShield] NGiNX server?Hi @philbee,
Thank you for the kinds words. 🙂
I understand completely. There are a lot of moving parts to a WordPress site, and it’s not always easy to catch each warning.
Here’s something that you might find interesting: Believe it or not, the idea that the “a lot of the best managed WP providers run NGiNX-only setups” is actually a myth. There is a lot of marketing hype that propagates that idea, but it’s not true. In our experience, the reverse is true. If I get into more detail here, it’s likely to start a debate (because you know that 100+ other people will jump in lol), but if you would like more info, hit me up through our contact page, and I’ll be happy to share some info with you by email. (Just a heads up with the contact form: don’t mention “WP-SpamShield” on the form, or the pre-filter will refer you to the support page.)
No worries…I totally understand. 🙂 You’re always welcome.
Take care!
– Scott
- This reply was modified 9 years, 5 months ago by redsand.
Forum: Plugins
In reply to: [WP-SpamShield] NGiNX server?Hi @philbee,
Thanks for the positive feedback! 🙂
If a site is getting that warning, it means that it does not meet the plugin’s minimum requirements. This requirement has been in place since the beginning of WP-SpamShield.
Please review the plugin’s minimum requirements and the Known Conflicts page for a full explanation. Here is an excerpt:
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. … 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.)
Unfortunately there is a lot of confusion with Nginx. There are several ways to deploy Nginx. Many of our sites use Nginx, but not as the primary server. We use it as a reverse-proxy in front of Apache. It gets complex, but there are a lot of benefits to using this setup.
Even though some elements may work on standalone Nginx, not everything will work properly. Your site running on standalone Nginx and doesn’t meet the plugin’s minimum requirements, and that’s why you’re getting the “Not Installed Correctly” message. That’s warning has actually been there for a long time, but we recently expanded it. It’s not a matter of adapting it for Nginx…Nginx just doesn’t have the capability to support all of the plugin’s features. We allowed the plugin to continue to run on standalone Nginx setups with the warning (for good people like you), but it’s become quite a headache because some users won’t read the instructions and then leave angry negative reviews or support requests. It’s a bit funny, because we are up front and tell users that not everything will work on standalone Nginx, and then some people come back to us angry because not everything works…on standalone Nginx. SMH. 🙂 So, unfortunately we are not going to allow it to run on standalone Nginx servers in the future, since they do not meet the plugin’s minimum requirements. It’s just the cleanest solution.
Unfortunately you may want to find an alternative plugin, unless you plan on switching your server setup. As much as it can be a pain to switch, for optimum WordPress experience, I would recommend setting your server up to run Apache as the primary server with Nginx as a reverse-proxy (cache). With that setup, you would have blazing speed, better plugin compatibility, better security, and overall fewer issues. You can export your site data, files, and databases, reinstall your server with the new config, and then import your site data, files, and databases. I’m sorry I don’t have better news for you.
We are working on developing an Nginx-only anti-spam plugin, but we can’t reveal any info on that yet. 🙂
– Scott
Forum: Plugins
In reply to: [WP-SpamShield] Woocommerce spam protection ? Is this plugin compatible ?You are very welcome. We think so too! 🙂
Forum: Plugins
In reply to: [WP-SpamShield] Issue with WooCommerce@makeonlineshop I definitely understand your concern. This is why it’s important as a website owner to always test out all essential website functionality when changes are made to the site, including adding new plugins/themes. We have a quick test you can run to make sure things are working after install, and the plugin also has a logging mode so you can see what was blocked. And, if you have any issues, we are always happy to provide tech support. Hope that helps!
– Scott
Forum: Plugins
In reply to: [WP-SpamShield] Woocommerce spam protection ? Is this plugin compatible ?Hi there @makeonlineshop,
I have good news for you. Yes to all of the above, and it’s the only anti-spam plugin that can do this. 🙂
WP-SpamShield protects:
- comment spam
- contact form spam
- trackback / pingback spam
- new user registration spam (including registration forms for almost all third party plugins) – WooCommerce included
- all contact forms from third party plugins
We’ve made sure it is compatible with WooCommerce.
I would say, give it a test, and you’ll be quite pleased.
For more information, and full documentation, you can check out the plugin’s homepage. If you ever need help, we’ll be happy to help you out. Just head over to the plugin’s support page.
I hope this helps! 🙂
– Scott
Forum: Plugins
In reply to: [WP-SpamShield] Conflicts with AdBlock/AdBlock Plus?No problem…happy to help! 🙂
Forum: Plugins
In reply to: [WP-SpamShield] Conflicts with AdBlock/AdBlock Plus?Hi @edikitt,
You’ll be fine with any of the top ad-blockers. AdBlock, AdBlock Plus, uBlock Origin (our favorite) are fine. We’ve never had a complaint from any of the popular ad-blockers. We added that info into the Troubleshooting Guide so people are aware that they have to make sure their browser plugins aren’t hindering normal web functionality. The plugin doesn’t use any functionality that those filters would trip on. It’s built for maximum compatibility. All of the known conflicts are listed in the plugin docs, so if it’s not in there, it’s not an issue.
Hope that helps!
– Scott
Forum: Plugins
In reply to: [WP-SpamShield] Antispam for Form plugins disabled by defaultHi @joeri1977,
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
Forum: Plugins
In reply to: [PHP Compatibility Checker] Fatal error on plugin activationHi @octalmage,
If the plugin doesn’t work 100% in PHP 5.2, I’d recommend adding a minimum requirements section to your plugin docs that state this, and then have the plugin detect PHP version upon activation, and automatically deactivate if PHP is < 5.3.
@octalmage & @jkf1:
If you want the plugin to work on 5.2, then you just need to add one line of code towards the beginning of the plugin…something like this:if ( !defined( '__DIR__' ) ) { define( '__DIR__', dirname( __FILE__ ) ); }That’s a lot simpler then asking a user to search & replace all instances of
__DIR__.– Scott
Hi @lacqui,
This is how the plugin is designed to work, and this is the standard implementation for FeedBurner, FeedPress and FeedBlitz. If you implement the .htaccess redirects as instructed by each of these three services, it would function exactly the same way.
This plugin is designed to provide an easy way for people to implement their FeedBurner, FeedPress, and FeedBlitz feeds. It’s not designed to provide advanced custom feed redirection options…that’s simply outside the scope of the plugin.
– Scott
Forum: Plugins
In reply to: [RS Head Cleaner Plus] Customizer Preview Not Working in 4.7Hi @pregwebwp,
I’m sorry to hear about the issue you’re having. We’ve testing the plugin thoroughly with WordPress 4.7, and have confirmed it to work with no issues in the Customizer Preview. It’s likely that there is a more specific conflict occurring on your site. I would recommending working through our WordPress Debugging Guide, and submitting a support request so we can help you look into this further.
– Scott