Hello @mksnmks,
Thanks for feedback. We are using memcached-redux as drop-in for memcached (not memcache) and it looks not compatible with php7+
If you have memcache driver, you can use Memcache for object caching and it’s compatible with php7+
If these are not a problem, and you know that this plugin is fully compatible with PHP7, then it would be helpful to add this plugin’s name to the PHP compatibility whitelist, and include some information about PHP version compatibility in the “details” page.
Sure thing!
Cheers,
Hi Mustafa Uysal (@m_uysl),
Re
We are using memcached-redux as drop-in for memcached (not memcache) and it looks not compatible with php7+
Does that mean that the plugin is “not” compatible with PHP7, or just that part of the plugin is not compatible.
If it is just a part of the plugin’s set of features, then it could be set to “not available” or “available in future” for when PHP7 is detected.
Re
you can use Memcache for object caching and it’s compatible with php7+
Do you have instructions on this? If so, then if Memcache can be run along with this plugin, then “How to” instructions could be included in the plugin.
But
It would be quite good to have the plugin detect PHP7 and then switch to using Memcache – I don’t know; is that possible?
Just to let you know –
I am not running this plugin yet. I installed it and scanned it, and won’t run it until I am confident that it will work okay. This is my standard procedure for any plugin not known to be compatible – avoids negative experience and related feedback.
I am looking forward to giving it a try.
Thanks
Does that mean that the plugin is “not” compatible with PHP7, or just that part of the plugin is not compatible.
just that part only.
Do you have instructions on this? If so, then if Memcache can be run along with this plugin, then “How to” instructions could be included in the plugin.
that depends on PHP driver that you are using for using the memcached (service)
I am not running this plugin yet. I installed it and scanned it, and won’t run it until I am confident that it will work okay. This is my standard procedure for any plugin not known to be compatible – avoids negative experience and related feedback.
Thank you so much, this plugin will be fully compatible with PHP7+ soon.
Cheers.
Hi Mustafa Uysal (@m_uysl),
Is it possible to have the ability in the program to detect which memory caching system is used, and then provide the settings for that system?
If so, then any settings which are in common for all memory caching systems, can be made evident (e.g. either bunched together, or “settings in common”, or color highlighted).
It might be possible to allow the user to supply their preferred settings for more than one memory cache system (whether available or not), and then they can switch from one to the other (e.g. if more than one can be done, or after an upgrade).
Recommended settings for each system can be supplied by the plugin.
But also if the user make s an adjustment for one system of memory caching, then the plugin could recommend adjustments to settings for the other memory caching systems.
This would be handy for upgrade paths, where users may have optimised the settings for their own site, and can upgrade and at the same time have a similar set of settings for the new caching system.
Just a thought -could be another Topic
but
Is it possible to flush the cache of just the page that is edited, or the product in WooCommerce that is edited.
Re “PHP7+ soon”
How soon?
I am testing quite a few things on the site at present, and would like to include this in the testing.
Thanks
Is it possible to have the ability in the program to detect which memory caching system is used, and then provide the settings for that system?
Yep, already checking which PHP drivers are supporting on your ENV. (redis, memcache, memcached) If you able to select one of them, you can use it. (configuration depends on your selection http://docs.poweredcache.com/article/6-object-cache)
If so, then any settings which are in common for all memory caching systems, can be made evident (e.g. either bunched together, or “settings in common”, or color highlighted).
It might be possible to allow the user to supply their preferred settings for more than one memory cache system (whether available or not), and then they can switch from one to the other (e.g. if more than one can be done, or after an upgrade).
Object caching (memory caching) is not work like that. WordPress comes with built-in object caching mechanism, drop-ins allow to making them persistent on memory.
Is it possible to flush the cache of just the page that is edited, or the product in WooCommerce that is edited.
Yep, we already support that feature. (see)
I am testing quite a few things on the site at present, and would like to include this in the testing.
Probably, within a week or two. Sorry for delay.
Thanks.
Hi,
Looks like our options are redis and memcached.
There is also opcache and apcu available – can you make use of these?
Apologies for the delay are happily accepted.
Keep up the good work.
Thanks
Looks like our options are redis and memcached.
Yes, for now.
There is also opcache and apcu available – can you make use of these?
Yeah, those are useful options too. I will check them later. #26, #27
Cheers,
Hello @mksnmks,
Powered Cache version 1.1.2 has been released and scanned with PHP7 compatibility checker. It looks %100 supporting PHP7+ now 🙂
Thanks for feedback and hope you like our plugin.
Regards!
Hi,
Thanks for the info.
We will try to run a test of it soon, within a fortnight at the latest (hopefully, time allowing).
We are updating plugins tonight.
You might like to add this information to the “Details” tab of the plugin page in WordPress.
Perhaps something like ;
“This plugin is compatible with the php versions ??? and 7+, so this plugin will remain compatible in your upgrade path to PHP v7+ .”
Thanks
Hi,
Just to note, update version 1.1.2 became available for automatic update, about 5 hours ago.
Hi @mksnmks,
I’ve added new question to faq section about PHP7, I think that’s enough for the explanation 🙂 Simply, If the WordPress requirements meet, that will work (doesn’t matter PHP 5.2.x or 7.x)
Just to note, update version 1.1.2 became available for automatic update, about 5 hours ago.
Yep, that’s depends on transients cache.
Thanks.
