I still haven’t gotten over what was my problem. I DON’T want to have memcached installed. WP-FFPC after installtion crashed my wordpress installtion with the error:
PHP Fatal error: wp-ffpc Memcached extension missing
Which is why I *tried* to install memcached. In fariness, I got some way with it.
When I type memcached at the bash prompt, I get:
can’t run as root without the -u switch
So I tried running memcached -u, it says
memcached: option requires an argument — ‘u’
Illegal argument “u”
From what I can gather, I need to add a user to the server. So I then tried to find out how to do that. The guides I have seen blithly skip through it as though the reader knows what they are doing.
There are simply no guides out there written at a level that I can understand.
But what I was asking was why does WP-FFPC crash even before I can get to the back end options because memcached is not installed? Surely it should be set to disk caching as default and then offer choices based on what IS installed?
@cotswoldphoto
I was able to reproduce the issue; there are two things off which I need to check.
First, the E_USER_ERROR level is in reality a FATAL error, not an error error as its name indicates…
The second is that this should only happen if the settings were saved and the extension was removed later on. I have a feeling that this is due to the default settings.
I’ll correct this soon, but I need to figure out, why is it happening.
I have been trying other plugins, such as w3 total cache, and was not entirely pleased with their performance. I thought I had deleted them, but it is possible some remnant existed?
Also, I had recently upgraded to PHP 5.5, but I am just in the process of downgrading to 5.4 as I write.
I’ve just pushed 1.6.4; it should reduce the log severity and remove this issue.
Hi
On installing I got this:
Warning: wp-ffpc Memcached extension missing, wp-ffpc will not be able to function correctly! in /home/xxxxxxxxx/public_html/wp-content/plugins/wp-ffpc/wp-common/plugin_utils.php on line 126
But at least I could get to the settings 🙂
So, I changed to memcache, and got this:
Warning: Memcache::connect(): Can’t connect to 127.0.0.1:11211, Connection refused (111) in /home/xxxxxxxxx/public_html/wp-content/plugins/wp-ffpc/wp-ffpc-backend.php on line 935
So, I changed to APC, no problems. Which is better, APC or memcache, and why did I get the second error? Did I need to change the 127.0.0.1 address and the port?
BTW. Your plugin transformed the load speed of my site. I now need to look at why Yslow scores so low. Looks like minified files and expires headers, neither of which does WP-FFPC handle (although W3 Total Cache used to). As Arnie says, I’ll be back.
Static files are not served by wp-ffpc and their expire headers should be set by the webserver. This plugin is to speed up serving the HTML, not for fixing misconfigured environments, like Total Cache.
You do not need to touch the host/port for APC as APC is a built-in thing for PHP, but in case youre using PHP 5.4 or higher, use APCu + Opcache instead, as APC is unstable for those versions.
So, I added a few bits of code to handle the static stuff and now have Page Speed of 97% (A) and yslow of 79%/80% (C/B) (seems to vary!! Mainly due to using externals files such as Google fonts, which only a CDN would fix).
Cool.
I shall do a bit of playing around and send a cup of coffee when I have a minute.
I still wondered whether APC or Memcache was faster, and how do I fix the error:
Warning: Memcache::connect(): Can’t connect to 127.0.0.1:11211, Connection refused (111) in /home/xxxxxxxxx/public_html/wp-content/plugins/wp-ffpc/wp-ffpc-backend.php on line 935
If I enable memcache?
You should not see that memcache connect error if you’re using APC at all.
Something might have gone wrong with your setting; could you please use the reset settings button and re-save the settings after that with APC selected to see if the error goes away?
As for the speed, these are my results:
https://petermolnar.eu/linux-tech-coding/wp-ffpc-speed/
Yes indeed, I do not see the error with APC enabled. I just wondered why it had an error if I had memcache enabled instead. By making a pre-cache, it was slightly faster again. 🙂
You should have a Paypal donation by now 😉
I just received the mail about it, thank you 🙂
As a mater of interest, which do you think would be faster?
PHP5.4/APC
(APC seems to be OK with PHP5.4, which is what I have right now).
or
PHP5.5/APCu/Zend Opcache
BTW. I forgot to ask, how did you measure those speed tests on your blog?
PHP5.5/APCu/Zend Opcache should be faster, according to theories, but I have not yet tested it.
Measurement was with Chromium and its net tab of F12.
So, I did a series of tests on page loading on my site with these 2 combinations:
PHP5.4 + APC + Memcache; WP-FFPC set to APC
PHP5.5 + APCu + Zend Opcache (settings optimised for WP); WP-FFPC set to APCu
PHP5.5 + APCu + Zend Opcache (settings optimised for WP) + Memcache; WP-FFPC set to APCu
Options 1 and 3 give much the same performance. 2 takes twice as long to load.
Not sure why? Is WP-FFPC optimised for Zend Opcache?
