redsand
Forum Replies Created
-
Yes, I understand about FREE technology, being a plugin developer, myself for over a decade, and doing high-level web development for over two decades.
This is not about mere promotional ads. This is about excessive ads and branding.
And no, I’m not new to any of this. I’m a seasoned pro with plugin development, cleaning out PHP db’s by hand, and SEO.
I stand by what I reported. This is a legit issue, that needs to actually be fixed.
I’ve told you what my issue is, you’re unwilling to fix it; that’s it.
Hmm, that’s not true. We already fixed the issue you initially complained about.
- We’ve already fixed the original source of your 1-star review.
- You now have a new issue: You claim that a piece of code would hurt a site’s rankings. You have no data to back up your claim, that this plugin would hurt a site’s rankings.
- You don’t want to understand what the code actually does.
- You don’t want to submit a support request.
- You don’t get your way, so you try to bully.
Who’s to say that even we acquiesced to your attempt to bully, that you would ever be satisfied?
I’m sorry but that’s not how this works. Eventually you’ll find that trying to bully other plugin developers will not work. It may even come back to bite you.
There is not much we can do to help you.
Take care.
– Scott
- This reply was modified 9 years, 4 months ago by redsand.
Yes, using your plugin as a platform to slander other plugin developers…is vindictive.
We help people rank higher in search engines. If, to make sure they keep on ranking well, we have to tell them to not use your plugin, that’s what we’ll do.
We do the same thing — help clients rank higher in search engines, day in and day out. We’ve been doing this for a couple decades. Nothing in this plugin would ever hurt SEO rankings.
Again, as mentioned, we don’t do support here. If you are interested in resolving the issue:
Please direct all support requests to the plugin’s official support venue,
WordPress Plugin Support.Yoast,
We can keep fighting here, or we can get to the point at hand: you shouldn’t have to special case for bots. You need to fix the underlying problem if you do.
If you have an issue that you actually want resolved then contact us through our official support form. I’ll be happy to discuss. You don’t actually understand what the code is doing, and why it’s important.
If you post negative info about our plugins, without actually getting in touch with us, (and not here at the forums — as mentioned several times — we do not do support here), then would fall into the slander category.
– Scott
@joostdevalk, That’s called vindictive. Good plugin developers have discussions before doing things like that.
You’re the one with the question…I’m not going to chase you. You’re welcome to contact us though.
- This reply was modified 9 years, 4 months ago by redsand.
Let’s have a little honesty. These are your last three plugin reviews:
- 1-Star, no prior support request – “Instead of helping to improve Yoast SEO, this author breaks it” — “Remove Branding for Yoast SEO” Plugin
- 1-Star, no prior support request – “Breaks Yoast SEO” — “Remove Yoast SEO comments” Plugin
- 1-Star, no prior support request – “Breaks AMP Plugin” — “RS Head Cleaner Plus” Plugin,
which like the “Remove Yoast SEO comments” plugin, removes the
<!-- This site is optimized with the Yoast SEO plugin -->code in the process of minifying HTML code.
Hey, we were just minding our own business. Nobody on my end started anything with you. I’m just calling it like I see it.
Wow, Yoast, you’re a man of your word…you just changed your review from one negative review to another negative one. Sounds about right after seeing seeing how you go after other plugin developers that may show the issues with your plugins.
After seeing those reviews, at least I discovered the real reason for this review.
You still haven’t even submitted a support request.
Don’t worry, I’m not expecting any good reviews from you. That’s not your style. Take care.
You’re welcome to think what you like, but that’s simply not accurate. Acting condescending doesn’t prove anything. You don’t know everything about SEO.
If you want to have a conversation, you’re welcome to contact us at the support page, as mentioned above, and I’ll be happy to explain. As noted, this isn’t our main support venue, and we don’t do support here.
- This reply was modified 9 years, 4 months ago by redsand.
Just to clarify, that’s not what cloaking is. Your understanding of cloaking is incorrect. Cloaking is serving different content to search engines, in order to game the system.
That code is there to make sure that if a search engine requests the wrong CSS file while minification is enabled, it will get the correct CSS file. All of the same CSS will be there — this just prevents issues.
This code actually is important to the site’s SEO, and prevents problems with search engines. By definition, this cannot be cloaking.
Search engines don’t dictate to site owners that they should not detect search engines — they just don’t want it to be used for evil. That’s not what’s happening here.
There is no support issue here. Everything is coded as it should be.
As noted above, if you have any further support issues, or you require further explanation, please direct them to the plugin’s official support page.
– Scott
Mods don’t remove reviews.
If you want to change your rating, just use this link: https://wordpress.org/support/plugin/rs-head-cleaner/reviews/?#new-post
Forum: Reviews
In reply to: [WP-SpamShield] Not for nginxRequires Apache…nope abandoned that a long time ago!
The plugin has never been compatible with standalone Nginx servers. It will work perfectly on an Apache/Nginx hybrid setup. This has always been clearly stated in the plugin minimum requirements.
How does that warrant a 1-star review?
If you try to use software on a system it’s not compatible with, that’s a user error, not a flaw in the software.
Apache and Nginx are not perfectly interchangeable. They have some significant differences. Apache is more powerful. Nginx lacks certain features in order to gain speed. To get the best of both you can use a Apache/Nginx hybrid setup.
It is important for all plugin users to read the documentation.
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. 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
We just released an update with the fix. You should be good to go now. 🙂
Hi Joost,
We’re already working on a fix. When someone alerts us to an issue, we try to fix it as soon as possible. It’s ~11:30 PM here right now, and we’ll have a release with a fix in the morning.
I understand the lack of happiness factor. However if you reach out to us via support forms, we will endeavor to solve any issues and repair the happiness. 🙂 We are fast.
One tip — when you need to check lots of plugins to find the source of the issue, we grep the WP plugins directory, and find the code in seconds.
Good code feedback is always appreciated!
You’re 100% right about the documentation not mentioning the async/defer. I did a double-take when I read that, but confirmed you’re right. I could have sworn it was there, and I suspect it mistakenly was removed at some point. (I will get to the bottom of that.) There is a vague reference to “defer” on the plugin homepage — “Defer Parsing of JavaScript (Google PageSpeed)” — but I don’t think that counts. We definitely need to fix that.
We’re currently deciding if we even need the async/defer feature right now. I’m leaning toward no, or at least making it opt-in. Overall, right now, we’re about 60/40 towards no or opt-in.
We did find the source of the issue. It’s really an issue with both plugins…if either one of the following fixes had previously been in place there would have been no issue.
- Our plugin needs to detect AMP URLS, and not touch them.
- The AMP plugin needs to follow WordPress core coding standards a little tighter.
In line 22 of file
amp-post-template-actions.phpin the AMP Plugin, it has the following code:<script custom-element="<?php echo esc_attr( $element ); ?>" src="<?php echo esc_url( $script ); ?>" async></script>This should be:
<script custom-element='<?php echo esc_attr( $element ); ?>' src='<?php echo esc_url( $script ); ?>' async></script>The standard that WordPress uses for enqueued scripts being printed in the head, is to use the single quote, not double quotes. (Unless there is something about AMP specs requiring double-quotes, but I don’t recall seeing this. Correct me if I’m wrong.) We’ll verify and report the issue to the AMP plugin.
Either way, we need to anticipate scripts not always following the coding standards, so we will add appropriate fixes on our end.
Absolutely…fixing the issue is a given with us. In most cases, we fix the issue within 24 hours of reporting it, and issue an update.
– Scott
I have to ask, why would you post a negative review without even submitting a support request first?
As a fellow developer, I would expect better from you…you know this isn’t the right way to handle things.
Your plugins have had issues with their code in the past, and we have contributed to the solution, and not gone straight to a 1-star review.
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. No one is asking for a 5-star rating, just a fair one.
– Scott
Forum: Reviews
In reply to: [WP-SpamShield] Seems to do the job. Widgets don’t workHi Dan ( @kaweah )
Well thanks for the detail, Scott. This shows some level of care.
You’re very welcome. Our goal is for each user to have a perfect experience. We’re always working towards this goal.
I think your logs must have failed to track me somehow. I distinctly recall combing through your conflicts page. I think you should perhaps consider the possibility that your user tracking code has a bug.
I do appreciate your feedback. We’re always open to the possibility of there being an error and we have no problem admitting if we are wrong or make a mistake, but that just wasn’t the case here. We have backup methods built into the whole process to make sure it’s accurate, along with a self-monitoring system that automatically reports bugs and errors to us.
The thing a lot of users don’t realize is that when we receive a support request, our tech support team has to go through the Troubleshooting Steps and FAQs step by step if the user doesn’t. Unfortunately there is a lot of bad info floating around about diagnosing WordPress issues, and so a lot of assumptions get made, and this leads people in many wrong directions. If users are willing to spend a few minutes working through the Troubleshooting Guide and FAQs, we’ll bend over backwards to help the user fix things 100%, even if it takes hours. We always get to the root of the issue.
I’d be fully willing to give your information pages another try, but please understand: I don’t need the widget…I am going through this to help you improve and promote your excellent product.
I understand, and for that we sincerely appreciate you. 🙂
– Scott