Table of contents ▼▲
Auth_acl.css issues: skin element not working
hi, darren, take a look at this fragment of a login page html output -- looks like only the default skin auth_acl.css in wikidx distribution gets used for page rendering! i'm not using the default skin here but my own orange skin, now three lines look ok but check out that fourth one:
<link rel="stylesheet" media="screen" type="text/css" title="Default" href="/skins/orange/css/default.css" />
<link rel="alternate stylesheet" media="screen" type="text/css" title="Print Preview" href="/skins/orange/css/printable.css" />
<link rel="stylesheet" media="print" type="text/css" title="Print Preview" href="/skins/orange/css/printable.css" />
<style type="text/css"> @import '/skins/default/css/auth_acl.css' ; </style>
hereâs another issue: acl_login.frm and acl_register.frm tag a separator row in authentication forms as different classes (a typo i guess), compare:
acl_login.frm
The 'row_spacer' issue was a typo. Fixed in v0.5.
The Reasoning behind this is to allow new skins to be developed without the need for duplicating the 'default' skin files each time if not needed. This is the case for *.inc , *.js, *.css, etc... Darren
<div class='row_spacer'> </div>
acl_register.frm
<div class='rowspacer'> </div>
The 'row_spacer' issue was a typo. Fixed in v0.5.
As for the css being used fromt he 'default' skin. This is intentional. The Template will look for css files in the 'current' skin, (ie orange in your case), and if not found, will look in the default skin. If not found there an error will be issued.
The Reasoning behind this is to allow new skins to be developed without the need for duplicating the 'default' skin files each time if not needed. This is the case for *.inc , *.js, *.css, etc... Darren