I am sure you have already considered this but in case not, take into account that sigplus CSS rules are marked as
!important, giving these rules much higher precedence than normal rules:
Code:
div.sigplus-gallery ul > li {
margin:0 !important;
border:0 none transparent !important;
padding:0 !important;
}
The reason for high precedence is because many templates have rules of their own that would interfere with sigplus (e.g. formatting rules for lists, spacing, etc.), and often these rules have an article or page section identifier in them, e.g.
Code:
#myid .blog
elevating rule precedence. Since most sigplus rules are not specific to a particular gallery and sigplus cannot know in advance what
#myid the template will employ, the only way to enforce precedence over template rules is to use
!important. The downside is that custom rules you introduce must not only have relatively higher precedence but also employ
!important to be considered.
In addition, sigplus galleries are always annotated with the class
Code:
sigplus-gallery
and sigplus galleries that are left-aligned and float have
Code:
sigplus-gallery sigplus-left sigplus-float
You might want to attach additional CSS content to these rules if you are intent on changing their appearance. Moreover, the attribute
id lets you assign a unique identifier to the gallery, again easing reference to a particular one. True, sigplus 1.3.x/1.4.x does not support the attribute
class in the activation tag.