To add, disabling “Aggregate CSS-files?” will solve the CSS issue.
thanks
source map files are only requested when the developer console is active and are only used for debugging purposes. they are not needed or used for “normal” visits or the site. is there, except for those source map files 404’ing, any problem with the site when “optimize CSS” is active?
frank
Thanks for replying. Yes, there are CSS issue when “Aggregate CSS-files” is enabled.
only happened after the most recent update.
Once I turn off the “Aggregate CSS-files”, CSS issue gone.
The “bootstrap.min.css.map” 404 issue was spotted after “Aggregate CSS-files” is enabled too. Once turned off “Aggregate CSS-files”, 404 error gone in the console too.
OK, did a quick review of the changes in CSS optimization and the only change is how CSS in “injected” in the HTML if “inline all CSS”, but there are no changes in how CSS is aggregated.
can you explain what the CSS issues are/ how they affect the way the site is rendered? and can you share your site’s URL?
Hi, sorry for the late reply.
issue still exists: once CSS is aggregated, some CSS can’t be loaded, style changed.
OK, what happens if you untick “also aggregate inline CSS”?
Hi @optimizingmatters thanks for replying. Still the same after unticking “also aggregate inline CSS”
OK, now in the comma-separated CSS optimization exclusion field, can you try excluding one of below each line and report back?
* wp-content/themes
* OR wp-content/plugins
* OR wp-includes/
Thank you for the advice.
Aggregate CSS-files? Yes on
Also aggregate inline CSS? Yes on
excluded wp-content/themes
Then issue disappeared.
What might be the issue?
Thanks
the issue that disappeared = the 404 on the source map, or a layout problem of (part) of the page?
the “[url]/bootstrap.min.css.map” 404 error, no more. Also page can load normally
the 404 error is irrelevant (the source map is only there for developers but is not needed), but what do you mean with “page can load normally”? were there indeed layout issues that are fixed when excluding wp-content/themes?
Yes. A lot of customized font colors can’t be loaded, falls back to the default colors.
OK, now when you don’t exclude wp-content/themes but instead disable “also aggregate inline CSS”, does that help the layout issues?
