HTML Logo by World Wide Web Consortium (www.w3.org). Click to learn more about our commitment to accessibility and standards.

Moving forward with Composr

ocPortal has been relaunched as Composr CMS, which is now in beta. ocPortal 9 will be superseded by Composr 10.

Head over to compo.sr for our new site, and to our migration roadmap. Existing ocPortal member accounts have been mirrored.


Curious about some Tempcode arguments in css vs templates

Login / Search

 [ Join | More ]
 Add topic 
Posted
Rating:
#95524 (In Topic #19011)
Avatar

Community saint

I'm familiar with this Tempcode argument in global.css:

{+START,IF,{$CONFIG_OPTION,fixed_width}}{+END}
It works exactly as intended.

The following Tempcode works wonderfully in GLOBAL_HTML_WRAP.tpl to isolate codes for the Welcome page from the Site page, but it is totally ignored in Global.css and I am wondering why? It would be great if I could apply the same technique to my css on selectors affecting zone pages differently.
{+START,IF,{$EQ,{$ZONE}:{$PAGE},:start}}{+END}
{+START,IF,{$NEQ,{$ZONE}:{$PAGE},:start}}{+END}

Jean


Last edit: by Jean
Back to the top
 
Posted
Item has a rating of 5 (Liked by Fletch)  
Rating:
#95537
Avatar

Community saint

I found my own answer after remembering that global.css is compiled and cached and any tempcode additions should be done via "no-cache.css"

Doing so worked perfectly!:cool:

Jean
Back to the top
 
1 guests and 0 members have just viewed this: None
Control functions:

Quick reply   Contract

Your name:
Your message: