Additional CSS Definitions are missing after installing Blog.

[Grover]

Hi,

See the attached screenshot. I just installed the vB Blog on my forum and I noticed that some textcolours of the small font are not right. They should be light-gray.



I have the following style setup:
vBulletin 3 (main)
My Forum Style (child) (default)I checked out the Additional CSS Definitions in the main style vBulletin 3 :




/* ***** styling for 'big' usernames on postbit etc. ***** */
.bigusername { font-size: 14pt; }

/* ***** small padding on 'thead' elements ***** */
td.thead, th.thead, div.thead { padding: 4px; }

/* ***** basic styles for multi-page nav elements */
.pagenav a { text-decoration: none; }
.pagenav td { padding: 2px 4px 2px 4px; }

/* ***** de-emphasized text */
.shade, a.shade:link, a.shade:visited { color: #777777; text-decoration: none; }
a.shade:active, a.shade:hover { color: #FF4400; text-decoration: underline; }
.tcat .shade, .thead .shade, .tfoot .shade { color: #DDDDDD; }

/* ***** define margin and font-size for elements inside panels ***** */
.fieldset { margin-bottom: 6px; }
.fieldset, .fieldset td, .fieldset p, .fieldset li { font-size: 11px; }

/* ***** don't change the following ***** */
form { display: inline; }
label { cursor: default; }
.normal { font-weight: normal; }
.inlineimg { vertical-align: middle; }
.underline { text-decoration: underline; }


And the Additional CSS Definitions in the child style My Forum Style look like this:




/* ***** styling for 'big' usernames on postbit etc. ***** */
.bigusername { font-size: 14pt; }

/* ***** small padding on 'thead' elements ***** */
td.thead, div.thead { padding: 4px; }

/* ***** basic styles for multi-page nav elements */
.pagenav a { text-decoration: none; }
.pagenav td { padding: 2px 4px 2px 4px; }

/* ***** define margin and font-size for elements inside panels ***** */
.fieldset { margin-bottom: 6px; }
.fieldset, .fieldset td, .fieldset p, .fieldset li { font-size: 11px; }

/* ***** don't change the following ***** */
form { display: inline; }
label { cursor: default; }
.normal { font-weight: normal; }
.inlineimg { vertical-align: middle; }


So, some CSS is missing there. I don't know how upgrading works regadering the Additional CSS Definitions, but I would assume that those definitions are updated when I upgrade my board or add a new product like the Blog? (I don't know which version of vB or if the Blog should have added those definitions?)

How does this all work : why am I missing those definitions?

[Onimua]

It was vBulletin that added those definitions I believe back in 3.6.6, since they're first used in Project Tools.

Is it customized CSS? vBulletin doesn't touch the CSS if it's been edited (like templates) so you'd have to manually add them in.

[Grover]

It was vBulletin that added those definitions I believe back in 3.6.6, since they're first used in Project Tools.

Is it customized CSS? vBulletin doesn't touch the CSS if it's been edited (like templates) so you'd have to manually add them in.

Thanks for informing me, Onimua.

Look at the screenshot for my Additional CSS Definitions. Both textfields show red text, which means that they are not the default definitions (?).



I always thought that textfield 1 (with '/* ***** styling for 'big' usernames on postbit etc. ***** */' and all the rest of it in it) were the default vBulletin definitions that you shouldn't change. And that textfield2 was meant to put your own definitions in.

Question 1 : Is this correct thinking?

To my memory I never changed textfield 1. The red contents of textfield 1 (as shown in the screenshot) were:



/* ***** styling for 'big' usernames on postbit etc. ***** */
.bigusername { font-size: 14pt; }

/* ***** small padding on 'thead' elements ***** */
td.thead, div.thead { padding: 4px; }

/* ***** basic styles for multi-page nav elements */
.pagenav a { text-decoration: none; }
.pagenav td { padding: 2px 4px 2px 4px; }

/* ***** define margin and font-size for elements inside panels ***** */
.fieldset { margin-bottom: 6px; }
.fieldset, .fieldset td, .fieldset p, .fieldset li { font-size: 11px; }

/* ***** don't change the following ***** */
form { display: inline; }
label { cursor: default; }
.normal { font-weight: normal; }
.inlineimg { vertical-align: middle; }



Question 2 : Since I think I have never changed textfield1, how come the new values are not added to textfield1?

I reverted textfield1 now, and it looks like this :



The contents are now:



/* ***** styling for 'big' usernames on postbit etc. ***** */
.bigusername { font-size: 14pt; }

/* ***** small padding on 'thead' elements ***** */
td.thead, th.thead, div.thead { padding: 4px; }

/* ***** basic styles for multi-page nav elements */
.pagenav a { text-decoration: none; }
.pagenav td { padding: 2px 4px 2px 4px; }

/* ***** de-emphasized text */
.shade, a.shade:link, a.shade:visited { color: #777777; text-decoration: none; }
a.shade:active, a.shade:hover { color: #FF4400; text-decoration: underline; }
.tcat .shade, .thead .shade, .tfoot .shade { color: #DDDDDD; }

/* ***** define margin and font-size for elements inside panels ***** */
.fieldset { margin-bottom: 6px; }
.fieldset, .fieldset td, .fieldset p, .fieldset li { font-size: 11px; }

/* ***** don't change the following ***** */
form { display: inline; }
label { cursor: default; }
.normal { font-weight: normal; }
.inlineimg { vertical-align: middle; }
.underline { text-decoration: underline; }


So everything is fine now, but I don't understand why textfield1 wasn't updated during upgrading of previous vB versions. I upgraded a few days ago from vB 3.6.4 to vB 3.6.8 and I do not use/own the Project Tools, but installed the Blog.

Regarding the purpose of this second textfield... I also reverted this to see what would happen.



... and as you can see the textfield2 becomes blank after reverting. This is a bit confusing to me, because reverting should take things back to the newest contents of a file, but the contents of textfield2 are always blank by default, apparantly?

Do you maybe have an answer to my questions?

[Onimua]

The second text area is blank, yes. There's nothing in it default.The new CSS classes that were added (the shade classes) were added as default to vBulletin itself, not dependent on the Blog or Project Tools.

In your first screenshot, it seems that you did customize your CSS in the first text area, and if that was the case, it would explain why the new CSS wasn't added in. If it's showing red text, it indicated that you did make some sort of change to it. It counts all the content as a whole, so even if you remove one line the entire text area would be highlighted as being customized.

You can change the information in the first text area, and add your own information in the second; it just depends on what you're doing and you know what you're doing. As far as I can tell, vBulletin's doing what it should when it comes to having customized CSS.