The CSS code is ok.
You can use the customizer to add that CSS code: http://kometschuh.de/easily-adding-custom-css-using-the-wordpress-theme-customizer.html
We don’t have any CSS file, we render all CSS code to the HTML file.
How can I put the inline-css-code from my html file into an external style-sheet? In my case the inline-css-code is very large (more than 800 lines!!!). I don’t like it in the cource to each html file of my website.
Thx for your help!
Sina
Sorry – the source, not the *cource!
Can you give us your website’s Url?
The site above has no widget installed from us.
The CSS code at your HTML code is not our code.
Here you can see other plugins and widgets also render CSS code direct to the HTML code.
http://www.ts-rechtsanwaelte.de
I created 56 categroy post widgets. That causes a lot of style in the source …
Thank you!
Sorry there is no option to create and use a external CSS.
We discuss here ‘a lot’ what is good and the decition now is to have no additional CSS
file to minimize web requests.
Caching external files is good for images, but inline CSS ‘text’ has a size of same less kb.
As you can see there are 800 lines from us and also 800 lines from other widgets.
Plugin Author
Mark-k
(@mark-k)
@sina2008
You can Copy that CSS and add it to your child theme’s CSS, then in the widgets themeselves, you can disable the CSS generation under the “general” section.
I agree with you that inline style of 800 lines long is a little extreme , but technically it is hard to detect when a widget is being used and add its specific inline style in the head while the decision to output it might happen only at the footer. Outputting the style only when the widget is being output violates the rule of not having styles in the body as it makes page rendering slower.
The other option is to have a CSS file, but that will add another http hit and you will need to have style for all of the options and add classes all over the html, which is not nice as well.
You are welcome to open a bug report at our git, and we will will see if we can figure out something for our next release (right now comes into my mind an option or filter that will let us do better detection of widget usage, with the down side of slower generation of the html.
