Not deleted, but CSS when taken out of order can get overwritten, so that’s likely what is happening
Any particular reason why you need “also aggregate inline CSS” unchecked?
frank
My cache is getting full within 3-4 days. I’m aware my site has a lot of CSS at the moment, but trying to combat having to empty cache a couple of times a week
have a look at the inline CSS and try to exclude only that which has random-looking strings in the selectors, that way you can keep “also aggregate inline CSS” while (hopefully) keeping cache size under control?
Okay thanks, I’ll look into that. For future reference, is there a way of disabling this option (or even the plugin entirely) without taking CSS out of order or getting overwritten?
no, afraid the only way to ensure correct order is either to aggregate all (so incl. inline) OR not to aggregate at all. generally the issue with things being overwritten can be worked around with some small tweaks to the CSS though, so that could also be an option?
were you able to find the right inline CSS to exclude marconi661 ?
No feedback so I assume you were able to indentify what needed to be excluded? Feel free to follow up if you still encounter issues!
have a nice day!
frank
