Kirsty, Am I correct in thinking that you are creating HTML pages using the reports rather that Internet>create webpages? If so I have not yet taken a look at those. If you confirm I will do so.
Ron Ferguson http://www.fergys.co.uk/ GOONS #5307 "Kirsty M. Haining" <khain...@comcast.net> wrote: ><!-- /* Font Definitions */ @font-face {font-family:Wingdings; >panose-1:5 0 0 0 0 0 0 0 0 0;} @font-face {font-family:"Cambria Math"; > panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; >panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, >li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; >font-size:12.0pt; font-family:"Times New Roman","serif";} a:link, >span.MsoHyperlink {mso-style-priority:99; color:blue; >text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed >{mso-style-priority:99; color:purple; text-decoration:underline;} >p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph >{mso-style-priority:34; margin-top:0in; margin-right:0in; > margin-bottom:0in; margin-left:.5in; margin-bottom:.0001pt; >font-size:12.0pt; font-family:"Times New Roman","serif";} >span.EmailStyle17 {mso-style-type:personal-reply; >font-family:"Calibri","sans-serif"; color:#1F497D;} .MsoChpDefault >{mso-style-type:export-only;} @page WordSection1 {size:8.5in 11.0in; > margin:1.0in 1.0in 1.0in 1.0in;} div.WordSection1 {page:WordSection1;} >--> > >Hi, all — > > > >I’ve been doing some testing on generating web pages from Legacy version 8 >(version 8.0.0.414), and I’ve been seeing all kinds of buggy output. Can >someone confirm that these are genuine bugs, and not just something funky with >the way I’ve been doing my report settings? Thanks. > > > >Here are the issues I’m seeing: > > > >(1) In Individual-Style Website pages — > > * AKAs are all run together without commas to separate them >(and without an "and" before the last AKA in the list) > > * Deceased spouses of living individuals which were set to >display as "deceased" still show up with full name and details > > * Unable to change wording options for any notes, events, etc. > > * For many couples, events print on one spouse, with notes >attached and event pictures, but on the other spouse the events only show up >in the event note portion, and so attached images do not display. > > * Alternate name for a deceased child is showing up in name >list (even though privacy says to show only “Deceased”). (This may be a >problem in other styles of web pages, too.) > > * On the name list, when alternate names are included, it >appears that the main preferred name for a female is then omitted from the >name list. (This may be a problem in other styles of web pages, too.) > > * If the option to “include the main name from each page as >the page's title” (Project tab) is checked, then that individuals’ name >displays at the top of the page EVEN WHEN privacy options say to set that >person’s name to Living or Deceased (as the case may be). > > > >(2) In Family-Style Website pages — > > * Unable to change wording options for any notes, events, etc. > > * Adds "Title Suffix" to the title of all family-report pages >(even though that was left blank on the project tab) > > * On the family page for a living spouse with a deceased >spouse (when privacy options are set to replace names with “Living” or >“Deceased”), it still gives the full name of deceased spouse in the title of >family group page, and then when it gets to the deceased spouse in the body of >the page it says this spouse is "Living." For children of this couple, the >deceased spouse shows up with full name. > > * Deceased child shows up with all info, even though the >option was set to change that to simply "Deceased." > > > >(3) In Ancestor-Style Website pages — > > * Deceased spouse shows up in report, even if privacy said to >change name to Deceased. (Shows up as “Deceased” on the living spouse’s >information, but then shows up with all information on details when it is the >deceased’s turn to be listed in the report.) > > > >(4) In Descendant-Style Website pages — > > * When privacy was set to change the name of living >individuals to “Living” and to have deceased spouses and children of living >individuals set to “Deceased” — in one instance, the second living child in >the list (who happened to have two deceased spouses and a 3rd living spouse) >had both deceased spouses show up in the descendant report as if they were the >children of the living spouse. Not only did all details on the deceased >spouses show up, but they showed up in incorrect relationship with the living >spouse. Deceased children were also not hidden as they should have been >(according to privacy options). > > > >cheers, > >Kirsty Haining > >Seattle, Washington > >J > > > > > > > > > >Legacy User Group guidelines: >http://www.LegacyFamilyTree.com/Etiquette.asp >Archived messages after Nov. 21 2009: >http://www.mail-archive.com/legacyusergroup@legacyusers.com/ >Archived messages from old mail server - before Nov. 21 2009: >http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >Online technical support: http://www.LegacyFamilyTree.com/Help.asp >Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on >our blog (http://news.LegacyFamilyTree.com). >To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
