The background color is being removed from the TR (row) tag of tables. So if I have bgcolor="#DEE3E7" in the TR tag of a table it will not be displayed. I have verified that the background value does still exist in the database (it should, I never edited the page!), but it is stripped upon display of the Content page. Any idea what would cause it to be removed?
Recently I upgraded to 7.5 3.2b patch, BBtoNuke 2.0.21, and Nuke Sentinel 2.5, and I am not sure which one introduced the problem. I didn't think to check my Content pages up every upgrade.
I performed the updates in the following order:
o 3.2b Patch
o BBtoNuke 2.0.14
o BBtoNuke 2.0.15
o BBtoNuke 2.0.16
o BBtoNuke 2.0.17
o BBtoNuke 2.0.18
o BBtoNuke 2.0.19
o BBtoNuke 2.0.20
o BBtoNuke 2.0.21
o Nuke Sentinel Deinstall of 2.22
o Nuke Sentinel Install of 2.5
Any ideas what could cause the problem?
Thanks for the help!
spottedhog Captain
Joined: Apr 30, 2004
Posts: 566
Posted:
Sun Aug 06, 2006 4:37 am
Here is a suggested fix:
--Move it to the style.css of the theme you are using.
In the TR tag, put in:
Code:
<tr class="bgcolor">
Then in the theme's style.css file, put in:
Code:
tr.bgcolor {background-color:DEE3E7; color:black}
The "color:black" part of that is for the text color within that row. You could also use "color:#000000". To pass CSS validation, one must list BOTH background and text color when using either color property.
Regardless of which code may be overriding your inputs, from a web standard's point of view, this is the correct way to do it.
SMF and PHP Nuke integration is ready! Take a look at it by clicking on the link above.
Valdarez Nuke Soldier
Joined: Apr 25, 2005
Posts: 20
Posted:
Sun Aug 06, 2006 12:13 pm
That's definitely a work around spotteddog, thanks for the suggestion. Overtime, I don't think that will be a manageable approach however, unless all tables rows are modified, plus, it requires the person who is adding content to have acess to the .css file, which might, or might not be the case.
spottedhog Captain
Joined: Apr 30, 2004
Posts: 566
Posted:
Mon Aug 07, 2006 4:08 am
To be able to reply to your post, I needed to sleep on it so I would maybe be better prepared to properly respond. Welll.... that did not help as I am still pissed off....
Your reply digs at the core root of what is wrong with PHP Nuke. You see, the entire Nuke code is written VERY BADLY from a web standards viewpoint. I gave you the proper answer on what to do according the the world wide web standards.
You see, there are standards for how web pages should be written. These standards are set up by the World Wide Web Consortium. See them here: http://www.w3.org The web standard, and has been a standard for many years, is to put decorative properties in cascading style sheets and only have layout in the html file. Soooo, tag properties such as color, bgcolor, and align must be placed in the style.css file.
I did NOT give you a "work around" as you suggested. I gave you the only way to write the code according to the W3C. Any reply that does not tell you to place background colors in the style.css file is completely irresponsible.
It does not matter if you need only 1 or if you need 100 background colors for a table row, ALL must be placed into your style.css file. Whether everyone has access to the style.css file is irrelevant. And your statement about it not being a manageable approach is irrelevant. You can place what ever number of background colors needed into the style.css file and then others can only choose from the list available. Like it or not, this is how the standard is set up, and this is how standards compliant browsers such as Firefox are created to render proper html code.
Again, any other reply not strongly recommending placing background colors into the style.css file is completely irresponsible and perpetuates the horribly written code FB puts out in regards to following world wide web standards.
SMF and PHP Nuke integration is ready! Take a look at it by clicking on the link above.
Valdarez Nuke Soldier
Joined: Apr 25, 2005
Posts: 20
Posted:
Mon Aug 07, 2006 6:41 am
First, and foremost, I am by no means an expert on websites or HTML, however after referencing the HTML specificiation, it appears that while CSS is definitely promoted as the way for handling style information as you suggested, the bgcolor element is most definitely part of the HTML specification standard. Take a look at this url: http://www.w3.org/TR/html4/struct/tables.html#h-11.2.5
If you continue to read the HTMl sepecification regarding StyleSheets, they are fairly consistent in their use of the terms 'may' and 'could', I never found any terminiology along the lines of 'must' use. http://www.w3.org/TR/html4/present/styles.html#h-14.1
I'm curious why you believe CSS is the only way to write the code? Can you point me to the documentation so I can better understand your take on the specification?
The approach you mentioned simply does not work in my scenario for all of the admins at our website. I have guys that have the ability to add news items and the ability to modify content pages, but they do not have FTP access to the website so they can never make changes to the .css files.
Valdarez Nuke Soldier
Joined: Apr 25, 2005
Posts: 20
Posted:
Mon Aug 07, 2006 4:57 pm
As a quick fix, I tried the approach you suggested spottedhog, and guess what? It's stripping the class="bgcolor" fromt he TR element as well! So there is no way in the content pages to add coloring to your rows.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum