Closed klor closed 10 years ago
Hello klor,
thank you for your report. We're planning to fix this issue in the next update.
Thank you in advance for your patience!
Marvin
Hello klor,
I've added a fix for this bug. The fix is included in the AIOM 3.1.4 Beta repository.
Can you please verify if this solution could be working for your bug?
Thank you in advance,
Marvin
AIOM seems to conclict with ProcessWire Core's cache. In AIOM I have set Lifetime to 2419200 for my CSS and JS files. In ProcessWire, I cache the pages -- here: Templates > Go to the Cache tab. and set Cache Time to 86400 (24 hours).
The reason for this issue is that AIOM updates the file name for the cached CSS and JS files while ProcessWire's Page Render cache does not update the file names simultaneusly.
File names cached by ProcessWire's Page Render Cache (in my case, these files do not exist to end-users / 404):
For instance, these file names were shown to me because I was logged in (valid files / 200):
... and these were the file names presented to the end-user (the files did not exist / 404):
My workaround was to copy the contents of the AIOM files into static files outside the AIOM folder -- since this will allow cached PW-files to always point at the correct CSS/JS file. Example: