Well, folks, to advise...
I just finished editing a long Legacy-outputted pedigree webpage, which was
outputted without including any generated headers and footers. It was of
one of my key individuals including 5 generations of family. It's among my
longest webpages, so there's lots of code glitches generated which get in
one's way in trying to customize to the standard format for my website.
I applied my theme, plus my usual top and borders, without any real problem
(except for the pain). Then of course upon adding a [dummy left border 120
pixels wide], the whole page disintegrated once again, which was the main
reason for starting this thread.
I never could manage to find all the html bits causing the multiple
problems, and so the project became a virtual rewrite. The page now
displays as we have every right to expect, and appearance is virtually
identical to that from the standard Legacy output. Webpage size increased
from 31k to 34k, which makes no sense to me, but...!
Everything fits within within two clean new tables. I kept all the existing
linking code intact. The top table contains the "go up" arrows and nested
sub-tables for parents and grandparents. The 2nd table contains the nested
sub-tables for the individual's image on the left and the "Family Links"
table on the right, so there are 8 nested tables; point being that all the
other table-nesting seems completely unnecessary. Perhaps some of the
Legacy-produced maze is necessary for the programmers to have a specific
place for data to land, but I doubt it.
I uploaded this small website to a space I have at tripod.com; the revamped
page URL is:
http://members.tripod.com/zelltree/010.htm
Any of the links to individuals run to Legacy output which has not been
revamped, so the problems are readily apparent, all caused by code glitches
which become a problem when a left border is activated.
I know it's a holiday here in the US, but perhaps after the Legacy folks get
back from their break, I would hope Support will contact me and take a look
at the original file and the rewritten file, then get the programmers to fix
these problems. I'm no programmer, but seems to me there can't be all that
much to do.
It would be most helpful if others at LUG would also voice a request that
Legacy fix their html code for pedigree webpages.
thanks so much
RonKZ
Legacy User Group Etiquette guidelines can be found at:
http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at:
http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit:
http://www.legacyfamilytree.com/LegacyLists.asp
