[Forum] if statements in .css templates

[nforums]

Do if statements in .css templates work? I'm trying to show something in one area for members and another for guests and the only thing I have to change is the position from absolute to relative but it doesn't seem to be working as planned

	position:<vb:if condition="$show['member']">relative<vb:else />absolute</vb:if>;

[beatyourtruck]

I am pretty sure that IF statements do not work in CSS files. At least I have never seen them or used them in that way? Someone please feel free to correct me if I am wrong but IF is for php pages, not for css.

[Andy]

Create a plugin.

Hook location: cache_templates

if ($vbulletin->userinfo['userid'] > 0) {
  $var = 'relative';
}

if ($vbulletin->userinfo['userid'] == '') {

  $var = 'absolute'
}

vB_Template::preRegister('vbulletin.css',array('var' => $var));

Change vbulletin.css to whichever template you need to register the variable in.

At this point you can use the {vb:raw var} in the css as needed. Example:

position:{vb:raw var};

[nforums]

Create a plugin.

Hook location: cache_templates

if ($vbulletin->userinfo['userid'] > 0) {
  $var = 'relative';
}

if ($vbulletin->userinfo['userid'] == '') {

  $var = 'absolute'
}

vB_Template::preRegister('vbulletin.css',array('var' => $var));

Change vbulletin.css to whichever template you need to register the variable in.

At this point you can use the {vb:raw var} in the css as needed. Example:

position:{vb:raw var};

Thanks Andy, that'll work for now.

But holy ****, why wouldn't they let the standard conditionals available in the CSS templates, since they are now seperate tempaltes from the "additional css" box in previous versions.

[Lynne]

Thanks Andy, that'll work for now.

But holy ****, why wouldn't they let the standard conditionals available in the CSS templates, since they are now seperate tempaltes from the "additional css" box in previous versions.

They are evaled differently than templates, I think. I don't think they run them through anything to eval conditions.

Good solution Andy... although, I am with Dave in that it would be really, really nice to put conditions directly in the css templates.

[thincom2000]

The problem with conditionals is that the CSS couldn't be cached in that case. Otherwise people would still be getting the unregistered-user CSS after they've logged in.

[Lynne]

The problem with conditionals is that the CSS couldn't be cached in that case. Otherwise people would still be getting the unregistered-user CSS after they've logged in.

Ah yes, I knew I had thought this through before and figured out why you couldn't do this.....

[markbuckin]

update for anyone who finds this while searching about using custom variables within the css files - spent a couple hours banging my head against a wall on this as I want to have 1 template across multiple sites, with site-specific customisations done via plugins, including different CSS.

anyway, as of 4.1.0, the plugin (containing the variables) hook location needs to be template_compile not cache_templates.