these constants will not conflict with AO no, but I don’t think this will activate page caching as that is not part of WordPress core?
This way i am asking you…
if have benefited from it even if you are not put an actual plugin managing WordPress.
PHP-FPM will read it and process it?
yeah, but PHP-FPM will read & process it, but they are merely constants that are being set and in and off themselves they do nothing. you could also add
define( 'WP_SAYS', 'cheese' );
and it would have the same effect if there is nothing in the code somewhere that reads that constant and does something with/ based on it.
as far as I know the constants you set will not trigger page caching in WordPress core as there is no page caching in core, so you would need a plugin to do something with those constants?
this way i ask you, because you say the truth 🙂
Do you have a recommendation for me? except for key-CDN? this plugin is a nightmare.
well, WP Super Cache is a golden oldie, still use it myself on some site. Or the newer Speed Booster Pack maybe? 🙂
what is a speed booster? wp super cache is too much, i already have Nginx.
i need something lite style KeyCDN with good support and connect properly to the new
WordPress API and not hide him.
(btw the problem with KeyCDN he creates another layer of cache on top of AO and this layer is hiding the API REST URL, AND let’s NOT TALK ABOUT, THAT THE BOTH EVERYTIME READ ANOTHER VERSION OF YOUR SITE BECAUSE THIS PLUGIN, THE WORST IS THE SUPPORT).
If i was able to activate that and use it only with the php or a plugin only create the advance-cache.php for php-fpm.
bat-cache is a good idea but is not operate properly and didn’t was update for long time 🙁
speed booster pack? what is it?
i already have Nginx.
is nginx doing page caching already?
