That’s not true, it’s not fair as well.
Why you didn’t even contact us and ask us to help you?
Can you contact us using this email – support@wpdevart.com, maybe we can help you.
It IS recommended (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.4) that a site in maintenance should deliver a 503 Server Header.
While presenting a 200 OK header while in maintenance mode, you are telling the client that all is OK and what you are seeing is what they are meant to see. For SEO reasons, crawlers will index your maintenance content.
Now with this said, although it is a standard and best practice to handle header responses correctly, it is not required.
Hi Justin,
right that is exactly what I meant 🙂
@wpdevart, you’re selling a premium plugin and I think should make your free version better. The plugin doesn’t work for 100%!
A customer of mine used it yesterday because he thought it’s a professional solution. Today I notoced that almost all pages are still visible. This happens because the file cache still exists. Sure you can say that this is not your plugin’s responsibility, but I’m sure most of your users doesn’t know about it. Maybe you should add a HUGE note about flushing cache?
At the end this is my honest review on a WordPress plugin and nothing personal. Because the cache issue is not directly related to this plugin, I change my review to 2 stars. 🙂
Thanks Justin, we know that it isn’t required, but we will change it on upcoming version.
Sorry, Olaf Lederer, but we can’t say thank you for your review.
We always try to help our users and make our plugin better, but why people rate our plugin just because they have some troubles with cache we don’t understand.
I don’t have trouble using it, it doesn’t work like it should do.
Some tips: Add the information about flushing the cache (test if a cache plugin is enabled).
Remove the Warner brother logo, using the logo is against the law (in western countries).
Great to hear that you will change the repsonse header to 503. You know, my negative review is related because my customer has used the plugin in good faith and it more a disaster than helpful (because of the cache and the 200 response header).
If I understand you right, in your opinion a review must be positive?
Dear developer.
Is the 503 issue fixed now?
I really like the idea of this plugin but have the same concern about the 200 status , just wondering if it’s been changed to 503 now
