flock: Still problems although updating to 2.2.5

Although updating to 2.2.5 we still get errors because of not finding files like these:


As far as we recognized it correctly all these errors are produced by Chrome and probably no other browsers.

Does anybody know why are these not existing files are called by Chrome? Or why these files doesn´t exist?

What files are those? Certainly not any I am familiar with as part of MODX.

They are probably the xxxxx.cache.php files for resources, and something is truncating the filenames.

We have an error-alert which informs us if any not existing file is called. The referrer of this files are always normal pages of our website.

I highly doubt it, they would be in a subdirectory of the context and be called {id}.cache.php; nothing in the MODX cache should ever go to the root cache directory in the default installation. This must be an add-on which is accessing these pages or misusing the cache API.

If the actual path to these files is /cache/, then it's not MODx at all. MODx cache files are in /path/to/your/web/root/core/cache/.

Hi Susan,
the call goes to to root/cache/...

@opengeek:
Do you have any idea how to find out which add-on could be responsible for theses calls?

That's not MODx then. Do you have some kind of caching enabled on the server itself? All of MODx's cache files are in core/cache. If you take a look at that directory, you'll then see a whole bunch more directories, and as far as anything with a name even vaguely like that, it's for the page caching, and those are in /core/cache/resource/<context>/resources/<resource-id>/da24152f89b34b63c5696069e3568e3c.cache.php

Susan:

Those are actually not the page caches, as those are stored as resource/<context_key>/<id>.cache.php. Those look like custom cache items stored in the resource partition along with the Resource items, typically by an extra like getPage, getCache, or Wayfinder. It is possible one of the extras is not using the cache properly, and getting cached improperly outside the resource partition. However, those would generally still be in the same structure as under the resource/ subfolder.