start standard table : why is 1 extra added in beginning? start standard table : why is 1 extra added in beginning?
 

News:

CPG Release 1.6.27
change DB IP storage fields to accommodate IPv6 addresses
remove use of E_STRICT (PHP 8.4 deprecated)
update README to reflect new website
align code with new .com CPG website
correct deprecation in captcha

Main Menu

start standard table : why is 1 extra added in beginning?

Started by duntuk, October 26, 2003, 07:05:23 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

duntuk

this isn't that big of a deal... just kinda bugs me since i prefer strict/valid html...

at the beginning of {GALLERY} output...

this is sample html output i noticed on most themes on the *home* page ...

note the REPEATED/UNECESSARY
<!-- Start standard table -->
<table align="center" width="100%" cellspacing="1" cellpadding="0" class="maintable">



<!-- Start standard table -->
<table align="center" width="100%" cellspacing="1" cellpadding="0" class="maintable">

<!-- Start standard table -->
<table align="center" width="100%" cellspacing="1" cellpadding="0" class="maintable">


<tr>
<td class="tableh1" width="80%"><b>Category</b></td>
<td class="tableh1" width="10%" align="center"><b>Albums</b></td>
<td class="tableh1" width="10%" align="center"><b>Pictures</b></td>
</tr>

...




also noticed this bug on sub pages:

<!-- Start standard table -->
<table align="center" width="100%" cellspacing="1" cellpadding="0" class="maintable">
</table>
<!-- End standard table -->


anyone know a way of preventing this...?

..thanks in advance..

Zarsky

Yes....at some point we need to clean up the HTML compliance of Coppermine.  It will be a bear to get it 100% compliant, but once we all have a good feel for the code, I am sure this will be done.  For now I suggest just dealing with the problems, unless they are breaking specific browsers.  In that case we will do our best to fix it.
Read the Online DOCs, FAQ, and SEARCH the board BEFORE posting questions for help.

duntuk

yup... that's what we've been doin'... just tweaked the template a little bit... but like you said, if it's not broken in the browser then it's not all bad... :)