Christian Ringele ha scritto:
Hi Matteo,
This cssSelectorRule seems to be outdated, meaning that the css could not be
applied to a image variation rule defined in STK.
Hi Christian,
thanks for your reply.
I've found where that line of log is written. It is written by my
teasers, because they extends the ImageModel.java class.
Debugging, I've found a curious behaviour.
This freemarker istruction:
[#if model.image??] (it is a basic instruction for teasers)
produce these actions:
1) Magnolia goes into content & templates
2) Finds the content nodes, template definitions, node data collection names
3) Builds a String like "#home #main-box-1 .teaser-group" and try to
discover if a image variation name is built with cssRule defined as that
strings.
I think it is too complicated.
I can not define new css rules for each content / content node /
collection... I would like to feel free to avoid it.
Or maybe I expected that no errors (and maybe no computation) are thrown
in the log.
But it is just my opinion..
This feature is still present in next 4.3 release?
Matteo
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
