More than one wordpress instance with plugin on LAMP

https://atec-systems.com/WP-Plugins/atec-cache-apcu.zip – 1.6.9
https://downloads.www.ads-software.com/plugin/atec-cache-apcu.1.7.zip – 1.7

no 1.7.1

v1.7.1 is prerelease and only available through atec-deploy.

sorry, my fault. I had changed the upload script.
files are updated.

please redeploy now.

i can not update 1.71 via deploy plugin. i see new version 1.71, but 1.6.9 version installs.

1.7.1, all plugins was disabled and removed, server was rebooted…. 1.7.1 was installed via deploy plugin. No salt – https://ibb.co/C8wrVND

May be we need something in logs, or php extension or something else?

I deactivated, activated and redeployed plugins in both blogs for several times…. it was only “no salt”, it was salt only for one blog (strinfs woith salt and with double “__”) and now i see this – https://ibb.co/mtVLGm7

I have four blogs on my home lab and usually run wordpress instances for tests… The process of starting caching doesn’t seem transparent to me.

Now it seems to me that the “Cache” tab now correctly displays “server level” information, including the number of cached pages and their size, and the “Page Cache” tab displays “blog level” information. This is a normal state of affairs, I think. Especially if it is described in the documentation. If the problems with the installation are not widespread and I was the only one lucky (I mean reinstalling version 1.7.1 multiple times), then the plugin works as expected and is perhaps the best solution to date. Perhaps on the “plugin side” it is worth checking for salt generation. Or implement entering or creating a “salt” in the settings. Thank you for your prompt replies. I understand that now it is not fashionable to translate your products into Russian, but if you are interested in this, I could do the translation. Also, after using it for some time, I will write a review in Russian on my blog and possibly in WordPress services.

And one more thing…
1. My wordpress health check found no page caching pluhins (http headers?)

2. Recommeneded values for cache are for one typical wordpress blog i think. Active jit brakes my server…. may be “Help: Recommended settings” should be more detailed

i hope i have fixed it now with v1.7.2.

please deactivate, redeploy, activate.

I have no problem with the people from russia.
you are welcome to translate.
do you know how it works?

You can find atec-cache-apcu-ru_RU.po file in languages folder, you are welcome to translate.
also review is welcome.

please redeploy v1.7.2

WP is looking for X-Cache-Enabled: which is provided by the plugin.
please check browser console, network, response header, you should see something like this

X-Cache:

HIT

X-Cache-Enabled:

true

X-Cache-Type:

APCu v1.7.2

X-Powered-By:

PHP/8.3.8

I can also recommend using atec-debug while looking for errors, now that you have all plugins at your hand.

It is strange. I see this:

X-Cache: HIT
X-Cache-Enabled: true
X-Cache-Type: APCu v1.7.2

for some pages (from the “Page cache” list), but not for main page. And there is no main page of the blog on the list

looks like it works now?

pages that are not cached should have a X-Cache-Fail header

https://1drv.ms/u/c/8141b97a31d6826a/EUEANu1icvFPsaq45GSCpU8BuB1y8YW4wqDno_Lx60Ywog?e=ecPXB1

I tried ro translate it, but it is not clear without a context.

For example
msgid “TARGET file already exists”
msgid “SOURCE”
msgid “TARGET”

I saw it only in logs


> pages that are not cached should have a X-Cache-Fail header
Yes. site-health.php check is very strange feature of wordpress. It will be one worning in my site-health.php log… Amen.