Files with .css.php and .js.php extensions not getting cached

Sorry .php files cannot be cached. They are presumed to be dynamic.

Then that is a bug on your end, Frederick. It is an incorrect presumption. How would I fix this?

It’s not about right or wrong or even a bug, it’s about safe assumptions and programming best practices (which .js.php or .css.php is not because of how web servers work).

Anyway, you can try to append those extensions to the custom file list for example.

Frederick, I was referring to the fact that you have a box to enter files that should always be cached, and it ignores files you enter that have a php extension, then that would be a bug.

I don’t get it either.. why would that be a bug? most systems (even a system of humans) are based on assumptions and decisions. In this case, it is your assumption to cache php. Personally I wouldn’t want any of my php files to be cached since I’m using php for computational purposes.

@onelife1985 – no, it’s my assumption that if you list a file in a box that says “always cache these file”, it will always cache those files.

Besides – pretty much the entire WordPress platform is used for computational purposes. There is no point in caching static pages… they are technically already “cached”, as almost no processing power is required to serve them. It’s the whole purpose of the caching plugin to store what would otherwise be dynamic pages, thus reducing the load on the server.

@mvandemar you have a good point there. But still I would recommend you to look further up at Frederick’s comment.. As he is the project manager W3TC, the system is based on the assumptions of his team (maybe community as well?), right?

Exactly.. “It’s the whole purpose of the caching plugin to store what would otherwise be dynamic pages, thus reducing the load on the server.”

What is cached is the result right? not the computational part (or else the algorithm).. You don’t want the server to go through the computational part multiple times and that’s why caching is used, to produce only once.

Based on Frederick’s comment above, php files are considered to be part of the computational part.

@onelife1985 – we’re not talking about caching something that is one section of a greater page. It’s the end product of a single output, namely either css or javascript, that just happens to have a .php extension. Therefore it should cache the output of those pages. And, again, regardless of the extension, if there is an “always cache these files” box that doesn’t always cache those files, that’s a bug. I am really not sure why you are arguing this point.

The extension of those of .php files is .php files, just because they have a prefix containing some other format does not mean that they are not generated dynamically. The final suffix of a file is intended to indicate what that file is or what it can do. I’m not going to change the settings, if you know what your site is doing you can add the settings yourself.

Frederick if you don’t want to fix it then that is of course your decision, it is your plugin. But it is still a bug if you have a feature that does not do what the description says that it does.

I don’t know why you think that I should assume a .js.php file is a static .js file. Are you sure you understand the implications of your request?

Frederick, I am not asking you to assume anything. Why would you? On the other hand, if someone enters in the name of a file inside of the text area that says “Always cache these file”, then why wouldn’t you cache them? I don’t understand what you aren’t getting… the instructions don’t say “Always cache these files, but we’re going to ignore your request if they have a php extension”, no… they say “Always cache these files”. Why does it make sense to you to have that text area there, and then ignore it?

If they were .html or .js files then there would be no need to cache them in the first place, they would already be static. Literally nothing about your argument is making any sense.

So be it.

Anyway, .php scripts usually dont initialize WP engine at all, often they include wp-load.php. As a result, no actions are called and plugins dont have a chance to do anything with output, so they can’t be cached. So I suggest to use some caching in your code. The best would be to write .css via a plugin (and update it based on actions, etc) and then just include pure .css later, instead of including .php script as css.