What a great thread with some excellent resources! I agree 100% with Word and Excel adding a lot of 'garbage.' Thanks everyone - these messages are keepers! Joy
You just told hundreds of people your password. Write to the Help Desk and ask for a new one. On Sun, Feb 17, 2013 at 1:50 PM, Paul Zantzinger <zantzinger@aol.com> wrote: > Regarding my site---http://www.rootsweb.ancestry.com/~gasmd/ > > Please tell me my users name and password. > > P
Regarding my site---http://www.rootsweb.ancestry.com/~gasmd/ Please tell me my users name and password. Paul Zantzinger it used to be user---gasmd password--- xytJr9E8 but they do not seem to work.
At 09:18 AM 2/16/2013, you wrote: >Did you upload it to public_html ? > >Since BasicGreen works, I'm wondering if they just forgot to add the >XHMTL version to the WWW server. It does work. I had made a mistake in the file itself. So just upload it to the correct folder and it should validate fine. Will cahnge the post to reflect that. pat G.
At 08:53 AM 2/16/2013, Patricia Geary wrote: >Nope does not appear to work at least not on this site >http://www.rootsweb.ancestry.com/~vamscdar/index.htm Did you upload it to public_html ? Since BasicGreen works, I'm wondering if they just forgot to add the XHMTL version to the WWW server. Pat A.
At 08:43 AM 2/16/2013, you wrote: >Out of curiosity, has anyone with a site on one of the other servers >- not freepages - tried loading the file to whatever directory they >publish to and check if it causes the pages to validate? Nope does not appear to work at least not on this site http://www.rootsweb.ancestry.com/~vamscdar/index.htm Will wait and see if I get an answer for RW. pat
At 12:19 AM 2/16/2013, you wrote: >Patricia, > >What a kludgey solution! But it works. Where is this documented?? > >However, Donna's case involves the non-freepages www.rootsweb >section - there is no misc_html there. So what are the steps for >those types of pages? ============== Out of curiosity, has anyone with a site on one of the other servers - not freepages - tried loading the file to whatever directory they publish to and check if it causes the pages to validate? pat
At 12:19 AM 2/16/2013, you wrote: >What a kludgey solution! But it works. Where is this documented?? > >However, Donna's case involves the non-freepages www.rootsweb >section - there is no misc_html there. So what are the steps for >those types of pages? Hmmmm, not sure about the www.rootsweb server solution or if there is one. I first wrote this http://www.genealogy-computer-tips.com/xhtml-doctype/ in 2008 which was probably when I moved to using the XHTML doctype. My pages validated on my computer but not when I uploaded them to the Rootsweb servers. When I questioned it, I was given this solution. I really don't know if it is documented anywhere or not. In searching, all I can find is the discussion that took place on Freepages in 2008. Will see if it is possible and if so how. Sorry, guess it did not register that her site was not part of FreePages. pat
Patricia, What a kludgey solution! But it works. Where is this documented?? However, Donna's case involves the non-freepages www.rootsweb section - there is no misc_html there. So what are the steps for those types of pages? John On Feb 14, 2013, at 08:54, Patricia Geary wrote: > At 09:45 AM 2/14/2013, Donna Cooper wrote: >> >> The errors are caused by the(proper) use of DOCTYPE XHTML and >> ancestry's use of regular HTML syntax in their inserted header code. > ====================== > > Tthere is a "fix."To change the banner code so that it will validate > if you are using the XHTML doctype create a file named > "banner_select" containing only the text: > > XHTMLNeutral > > and nothing else. The file should be a plain text file and the file > name must not include a file extension, i.e. do NOT name it > banner_select.txt or banner_select.html > > Upload the file to your misc_html directory. > > Example: > http://freepages.genealogy.rootsweb.ancestry.com/~gearyfamily/ uses > the XHTML doctype and validates. > > http://freepages.misc.rootsweb.ancestry.com/~gearyfamily/banner_select > which allows the XHTML code to validate.
Wll the first try got pretty mangled so will try again and see if it does better. Image require an alt tag in order for them to validate. You Have <code> <img src="EagleRockSchool-Pre1958-b.jpg" width="546" height="345" /></code> should be <code> <img src="EagleRockSchool-Pre1958-b.jpg" width="546" height="345" alt="description of picture"/> </code> The description should be short. More reading http://www.w3schools.com/tags/att_img_alt.asp pat Pat Geary Working With Rootsweb FreePages Accounts EBook (free) http://freepages.genealogy.rootsweb.ancestry.com/~gearyfamily/rootsweb-freepages-ebook.html
At 03:52 PM 2/14/2013, you wrote: >I am having difficulty getting image links to >validate on my photo pages.  The search >wrapper doesn't validate, but I understand why >on that. But, please take a look at the photo >links that I have posted on this page. I don't >know how to change the code so that I can leave >the photos open and to get the page to >validate - I am talking about my work, >excluding the Roots wrapper. I asked about that >problem earlier and now know the problem with >the wrapper.  Please take a look at this page >and see what I mean - > >http://www.rootsweb.ancestry.com/~mobarry/School-Book/Eagle-Rock/EagleRockSchool-1956-57.htm >I hope some of you who are familiar with the >photo problem will know what to do. ========== Image require an alt tag in order for them to validate. You Have <img src="<view-source:http://www.rootsweb.ancestry.com/~mobarry/School-Book/Eagle-Rock/view-source:http://www.rootsweb.ancestry.com/%7Emobarry/School-Book/Eagle-Rock/EagleRockSchool-Pre1958-b.jpg>EagleRockSchool-Pre1958-b.jpg" width="546" height="345" /> should be <img src="<view-source:http://www.rootsweb.ancestry.com/~mobarry/School-Book/Eagle-Rock/view-source:http://www.rootsweb.ancestry.com/%7Emobarry/School-Book/Eagle-Rock/EagleRockSchool-Pre1958-b.jpg>EagleRockSchool-Pre1958-b.jpg" width="546" height="345" alt="description of picture"/> The description should be short. More reading http://www.w3schools.com/tags/att_img_alt.asp pat Pat Geary Working With Rootsweb FreePages Accounts EBook (free) http://freepages.genealogy.rootsweb.ancestry.com/~gearyfamily/rootsweb-freepages-ebook.html
The use of the term "proper" use, in the opinion of others is..... um a word I can't use. -----Original Message----- From: Donna Cooper <donnac58@yahoo.com> To: Roots Help <rootsweb-help@rootsweb.com> Sent: Thu, Feb 14, 2013 6:47 am Subject: [ROOTSWEB-HELP] Search Wrapper One user confirmed what I thought, so I have written to the help desk to see if they will fix the problem. The errors are caused by the(proper) use of DOCTYPE XHTML and ancestry's use of regular HTML syntax in their inserted header code. XHTML requires that all tags have their corresponding end tags or that the self-closing tag syntax be used when necessary for void tags (e.g. <br />). The errors are from these 5 lines - they all need to be self-closing (ending in " />"): Donna Cooper ------------------------------- To unsubscribe from the list, please send an email to ROOTSWEB-HELP-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message
I am having difficulty getting image links to validate on my photo pages. The search wrapper doesn't validate, but I understand why on that. But, please take a look at the photo links that I have posted on this page. I don't know how to change the code so that I can leave the photos open and to get the page to validate - I am talking about my work, excluding the Roots wrapper. I asked about that problem earlier and now know the problem with the wrapper. Please take a look at this page and see what I mean - http://www.rootsweb.ancestry.com/~mobarry/School-Book/Eagle-Rock/EagleRockSchool-1956-57.htm I hope some of you who are familiar with the photo problem will know what to do. Donna --------------------------------- 1. Line 84, Column 89: required attribute "alt" not specified …mage"><img src="EagleRockSchool-Pre1958-b.jpg" width="546" height="345" /></td> ✉ The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element. Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>. 2. Line 88, Column 89: required attribute "alt" not specified …mage"><img src="EagleRockSchool-Pre1958-a.jpg" width="546" height="345" /></td> ✉ The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element. Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.
At 09:45 AM 2/14/2013, you wrote: >One user confirmed what I thought, so I have written to the help >desk to see if they will fix the problem. > >The errors are caused by the(proper) use of DOCTYPE XHTML and >ancestry's use of regular HTML syntax in their inserted header code. > >XHTML requires that all tags have their corresponding end tags or >that the self-closing tag syntax be used when necessary for void >tags (e.g. <br />). > >The errors are from these 5 lines - they all need to be self-closing >(ending in " />"): ====================== Tthere is a "fix."To change the banner code so that it will validate if you are using the XHTML doctype create a file named "banner_select" containing only the text: XHTMLNeutral and nothing else. The file should be a plain text file and the file name must not include a file extension, i.e. do NOT name it banner_select.txt or banner_select.html Upload the file to your misc_html directory. Example: http://freepages.genealogy.rootsweb.ancestry.com/~gearyfamily/ uses the XHTML doctype and validates. http://freepages.misc.rootsweb.ancestry.com/~gearyfamily/banner_select which allows the XHTML code to validate. Simple!
At 09:10 PM 2/13/2013, Donna Cooper wrote: >Why is it that the search wrapper won't validate? SOLUTION: http://www.genealogy-computer-tips.com/xhtml-doctype/ Uses the XHTML doctype and validates. pat Pat Geary Working With Rootsweb FreePages Accounts EBook (free) http://freepages.genealogy.rootsweb.ancestry.com/~gearyfamily/rootsweb-freepages-ebook.html
One user confirmed what I thought, so I have written to the help desk to see if they will fix the problem. The errors are caused by the(proper) use of DOCTYPE XHTML and ancestry's use of regular HTML syntax in their inserted header code. XHTML requires that all tags have their corresponding end tags or that the self-closing tag syntax be used when necessary for void tags (e.g. <br />). The errors are from these 5 lines - they all need to be self-closing (ending in " />"): Donna Cooper
Donna, Those errors are caused by your (proper) use of DOCTYPE XHTML and ancestry's use of regular HTML syntax in their inserted header code. XHTML requires that all tags have their corresponding end tags or that the self-closing tag syntax be used when necessary for void tags (e.g. <br />). The errors are from these 5 lines - they all need to be self-closing (ending in " />"): <link rel="stylesheet" type="text/css" href="http://images.rootsweb.com/css/h/t.css"> <input type="hidden" name="gss" value="rootsweb"> <input id="FirstSearchBox" name="gsfn" type="text" size="16" value="First Name" style="color:#999999;" onblur="searchOnBlur1()" onfocus="searchOnFocus1()"> <input id="LastSearchBox" name="gsln" type="text" size="16" value="Last Name" style="color:#999999;" onblur="searchOnBlur2()" onfocus="searchOnFocus2()"> <input id="SubmitButton" type="submit" value="Search" style="color:#ffffff; background: #afbc22;"> The rootsweb http servers have been modified to add programming to examine the start of each page and insert their <link> tag in the header and their other code at the beginning of the body. That programming could be modified to add a check for an XHTML doctype, and if found, to use the self-closing syntax for the above 5 tags. You could send this request to the help desk, and hope that it's read by someone who, like you, recognizes the usefulness of code validation to ensure that any rendering problems are not being caused by coding problems. John Van Essen On Feb 13, 2013, at 20:10, Donna Cooper wrote: > Why is it that the search wrapper won't validate? > > Here is what I get for this page - > > http://www.rootsweb.ancestry.com/~mobarry/School-Book/a-index.htm > > > -------------------------------- > > > Validation Output: 5 Errors > 1. Line 8, Column 87: end tag for "link" omitted, but OMITTAG NO was specified > …rel="stylesheet" type="text/css" href="http://images.rootsweb.com/css/h/t.css"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 2. Line 8, Column 2: start tag was here > <link rel="stylesheet" type="text/css" href="http://images.rootsweb.com/css/h/… > 3. Line 56, Column 58: end tag for "input" omitted, but OMITTAG NO was specified > <input type="hidden" name="gss" value="rootsweb"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 4. Line 56, Column 9: start tag was here > <input type="hidden" name="gss" value="rootsweb"> > 5. Line 57, Column 164: end tag for "input" omitted, but OMITTAG NO was specified > …me" style="color:#999999;" onblur="searchOnBlur1()" onfocus="searchOnFocus1()"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 6. Line 57, Column 9: start tag was here > <input id="FirstSearchBox" name="gsfn" type="text" size="16" value="Fir… > 7. Line 58, Column 162: end tag for "input" omitted, but OMITTAG NO was specified > …me" style="color:#999999;" onblur="searchOnBlur2()" onfocus="searchOnFocus2()"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 8. Line 58, Column 9: start tag was here > <input id="LastSearchBox" name="gsln" type="text" size="16" value="Last… > 9. Line 59, Column 107: end tag for "input" omitted, but OMITTAG NO was specified > …tton" type="submit" value="Search" style="color:#ffffff; background: #afbc22;"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 10. Line 59, Column 9: start tag was here > <input id="SubmitButton" type="submit" value="Search" style="color:#fff…
Are you validating thru W3C or what? Gloria On Feb 13, 2013, at 8:10 PM, Donna Cooper wrote: > Why is it that the search wrapper won't validate? > > Here is what I get for this page - > > http://www.rootsweb.ancestry.com/~mobarry/School-Book/a-index.htm > > > -------------------------------- > > > Validation Output: 5 Errors > 1. Line 8, Column 87: end tag for "link" omitted, but OMITTAG NO was specified > …rel="stylesheet" type="text/css" href="http://images.rootsweb.com/css/h/t.css"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 2. Line 8, Column 2: start tag was here > <link rel="stylesheet" type="text/css" href="http://images.rootsweb.com/css/h/… > 3. Line 56, Column 58: end tag for "input" omitted, but OMITTAG NO was specified > <input type="hidden" name="gss" value="rootsweb"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 4. Line 56, Column 9: start tag was here > <input type="hidden" name="gss" value="rootsweb"> > 5. Line 57, Column 164: end tag for "input" omitted, but OMITTAG NO was specified > …me" style="color:#999999;" onblur="searchOnBlur1()" onfocus="searchOnFocus1()"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 6. Line 57, Column 9: start tag was here > <input id="FirstSearchBox" name="gsfn" type="text" size="16" value="Fir… > 7. Line 58, Column 162: end tag for "input" omitted, but OMITTAG NO was specified > …me" style="color:#999999;" onblur="searchOnBlur2()" onfocus="searchOnFocus2()"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 8. Line 58, Column 9: start tag was here > <input id="LastSearchBox" name="gsln" type="text" size="16" value="Last… > 9. Line 59, Column 107: end tag for "input" omitted, but OMITTAG NO was specified > …tton" type="submit" value="Search" style="color:#ffffff; background: #afbc22;"> > ✉ > You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". > 10. Line 59, Column 9: start tag was here > <input id="SubmitButton" type="submit" value="Search" style="color:#fff… > > ------------------------------- > To unsubscribe from the list, please send an email to ROOTSWEB-HELP-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message
Why do you want it to validate? -----Original Message----- From: Donna Cooper <donnac58@yahoo.com> To: Roots Help <rootsweb-help@rootsweb.com> Sent: Wed, Feb 13, 2013 6:14 pm Subject: [ROOTSWEB-HELP] Roots Search Wrapper Why is it that the search wrapper won't validate? Here is what I get for this page - http://www.rootsweb.ancestry.com/~mobarry/School-Book/a-index.htm -------------------------------- Validation Output: 5 Errors 1. Line 8, Column 87: end tag for "link" omitted, but OMITTAG NO was specified …rel="stylesheet" type="text/css" href="http://images.rootsweb.com/css/h/t.css"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 2. Line 8, Column 2: start tag was here <link rel="stylesheet" type="text/css" href="http://images.rootsweb.com/css/h/… 3. Line 56, Column 58: end tag for "input" omitted, but OMITTAG NO was specified <input type="hidden" name="gss" value="rootsweb"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 4. Line 56, Column 9: start tag was here <input type="hidden" name="gss" value="rootsweb"> 5. Line 57, Column 164: end tag for "input" omitted, but OMITTAG NO was specified …me" style="color:#999999;" onblur="searchOnBlur1()" onfocus="searchOnFocus1()"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 6. Line 57, Column 9: start tag was here <input id="FirstSearchBox" name="gsfn" type="text" size="16" value="Fir… 7. Line 58, Column 162: end tag for "input" omitted, but OMITTAG NO was specified …me" style="color:#999999;" onblur="searchOnBlur2()" onfocus="searchOnFocus2()"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 8. Line 58, Column 9: start tag was here <input id="LastSearchBox" name="gsln" type="text" size="16" value="Last… 9. Line 59, Column 107: end tag for "input" omitted, but OMITTAG NO was specified …tton" type="submit" value="Search" style="color:#ffffff; background: #afbc22;"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 10. Line 59, Column 9: start tag was here <input id="SubmitButton" type="submit" value="Search" style="color:#fff… ------------------------------- To unsubscribe from the list, please send an email to ROOTSWEB-HELP-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message
Why is it that the search wrapper won't validate? Here is what I get for this page - http://www.rootsweb.ancestry.com/~mobarry/School-Book/a-index.htm -------------------------------- Validation Output: 5 Errors 1. Line 8, Column 87: end tag for "link" omitted, but OMITTAG NO was specified …rel="stylesheet" type="text/css" href="http://images.rootsweb.com/css/h/t.css"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 2. Line 8, Column 2: start tag was here <link rel="stylesheet" type="text/css" href="http://images.rootsweb.com/css/h/… 3. Line 56, Column 58: end tag for "input" omitted, but OMITTAG NO was specified <input type="hidden" name="gss" value="rootsweb"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 4. Line 56, Column 9: start tag was here <input type="hidden" name="gss" value="rootsweb"> 5. Line 57, Column 164: end tag for "input" omitted, but OMITTAG NO was specified …me" style="color:#999999;" onblur="searchOnBlur1()" onfocus="searchOnFocus1()"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 6. Line 57, Column 9: start tag was here <input id="FirstSearchBox" name="gsfn" type="text" size="16" value="Fir… 7. Line 58, Column 162: end tag for "input" omitted, but OMITTAG NO was specified …me" style="color:#999999;" onblur="searchOnBlur2()" onfocus="searchOnFocus2()"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 8. Line 58, Column 9: start tag was here <input id="LastSearchBox" name="gsln" type="text" size="16" value="Last… 9. Line 59, Column 107: end tag for "input" omitted, but OMITTAG NO was specified …tton" type="submit" value="Search" style="color:#ffffff; background: #afbc22;"> ✉ You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">". 10. Line 59, Column 9: start tag was here <input id="SubmitButton" type="submit" value="Search" style="color:#fff…