Many hosting environments won't allow you to change the memcached pecl installation. Is there any way to "soften" the warning message? I know many environments that won't upgrade to version 3.x for a while yet.

Comments

Jeremy’s picture

Jeremy CreditAttribution: Jeremy commented
Status: Active » Closed (works as designed)

Unfortunately earlier versions of the memcache PECL extension have known bugs leading to cache clearing errors. If websites are running with an earlier PECL extension they may experience problems.

If you disable the memcache module (but leave the settings.php configuration) you will remove the warning -- proceed at your own risk.

More information here:
#1806120: Wildcard flushes do nothing

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented

It may be better to have a warning message and have a page or closed issue on this project with a link from the warning message to explain in a bit more detail why they are getting the message.

"You can still use this module but issues with Memcache 2.x may cause monkeys to fly out of your butt. Upgrading to Memcache 3.x will lower the chances of monkey infestation of your rear end. Read more about Memcache Butt Monkeys here."

Something along those lines anyway...

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented

By the way, I only say this because (technically) the memcache 3.x release is in beta and doesn't tend to get installed at first. We may run into sticklers for "the rules" and installations are limited to stable packages.

Jeremy’s picture

Jeremy CreditAttribution: Jeremy commented

The requirement for 3.0.6+ has been documented in the README for a long time; all we've done is note it in the code too so people who may not have read the documentation are aware.

3.0.6 has been available for nearly 3 years. The code is quite stable, and IMO is mis-labeled by PECL as beta at this point. While I understand your concerns that technically it's not a stable release, the fact of the matter is that 2.2.7 has a bug that 3.0.6+ does not.

Please encourage the folks at http://pecl.php.net/package/memcache to tag a stable 3.x release.

Shane Birley’s picture

Shane Birley CreditAttribution: Shane Birley commented

You're preaching to the choir, man. I *agree* fully that it is mis-labeled, all I am saying is that since we're tasked with dealing with it (and also wanting to reduce the questions in the issue queue) -- just making people aware that the message may appear for them and the reason is because of Memcache Butt Monkeys -- we should provide as much information as possible for them to pressure their hosting environments to upgrade.

And, I note, the change from -beta4 (or before) to -beta5 will freak end users out. I just want to make them aware that it isn't OUR fault.