I tagged Core Team for review, but I just realised that maybe I should have tagged Websites Team instead.@textagroup Do you know whether there's a specific reason theCACHING_ENABLED constant was set the way it was? To me, it seems like it's doing the opposite of what it should be doing on the line that I'm changing in this PR.

I tagged Core Team for review, but I just realised that maybe I should have tagged Websites Team instead.@textagroup Do you know whether there's a specific reason theCACHING_ENABLED constant was set the way it was? To me, it seems like it's doing the opposite of what it should be doing on the line that I'm changing in this PR.

Any idea about my question above@Frankie75321 ?

Since@tsteur came across the same and arrived at the same solution, I think this tweak is the correct solution. If there's no objection from@textagroup or@Frankie75321 or@sgiehl, I think we can merge this. On the face of it, it makes sense without the negation.

Since@tsteur came across the same and arrived at the same solution, I think this tweak is the correct solution. If there's no objection from@textagroup or@Frankie75321 or@sgiehl, I think we can merge this. On the face of it, it makes sense without the negation.

No objection from me. I came across the same thing.

Thank you for everyone's feedback. Even with the PR being approved, I don't appear to have permission to merge.@Frankie75321 or someone else with merge permissions for this repo, could you please merge this PR?