Feature #15715
closed
plugin.tx_anyname._CSS_DEFAULT_STYLE_FILE not provided
0%
Description
May plugins are using _CSS_DEFAULT_STYLE to insert it own stylesheet into the page.
Many of them are hure and people wanted to make them become external css file. Some plugin manual will told people using css @import url(xx);.
But, it do not support EXT: path lookup. User have to make a copy of their stylesheet and than hardcode the path into tstemplate. Also, large tsmptelate isn't a good idea.
I suggest add a new _CSS_DEFAULT_STYLE_FILE. Which wll use TSFE-tmpl->getFileName to reslove the file path.
It may even has addition setting,
e.g.
inline the css in html
copy css to temp folder (make EXT:plugin path hidden from web)
choose html <link> style include, or css @include style include.
Good:
It reduce the size tstemplate.
CSS will be standalone file, easier to edit by editor.
Reduce output html size.
Bad:
will not supported tsconstants in stylesheet.
(issue imported from #M2684)
Updated by Wolfgang Klinger over 18 years ago
try to use
config.inlineStyle2TempFile = 1
that should solve your problem
Updated by old_hkdennis2k over 18 years ago
Ofcouse I know that.
It is a global configuration to all the CSS file, not set by each plugins individual.
There should another way to control by plugin itself or default from plugin development.
But you can't reduce the size of tstemplate and you can quickly edit the CSS by common CSS file editor.
Also, inlineStyle2TempFile always do a md5 hash of the content. Does it waste CPU power??
Updated by Dmitry Dulepov about 13 years ago
- Category deleted (
Communication) - Status changed from New to Resolved
- Target version deleted (
0) - TYPO3 Version changed from 3.8.1 to 4.6
- PHP Version deleted (
5)
TYPO3 now has a compressor, which takes care of this.
Updated by