1. 

   wcamp
   

   offline

   Member

   Please help. I can't find the correct approach to take.

   On line 27 of this page . . .
   https://www.warrencampdesign.com/samuel/part1/week15.php
   . . .
   I call for a page menu titled "samuel-part1_menu.html," shown here: https://www.warrencampdesign.com/samuel/part1/samuel-part1_menu.html

   When I did a W3C test for the menu page, it told me that it needed a doctype, language, head, and title tags.

   I added all four and uploaded the menu.html file. I then checked my "week15.php" page for W3C validation and it declared a "stray doctype" on that page because the page already has a doctype at its top and now has one (apparently) in that "samual-part1_menu.html" page that I called for on line 27.

   What's needed to verify the actual page and the menu page?

   I need to understand the correct approach to take because I have more than two hundred files that have a "_menu.html" page called for, so I need to make it right in every case.

   Thanks, in advance.

   Warren

   Posted 1 month ago
2. 

   Gerry
   

   offline

   PVII Team

   The SSI page (menu) is only a partial fragment of the master page, you never check the ssi page separately. You would do the W3C check only for the full page, which of course includes the ssi markup, and handle any errors found.

   You most likley had it correct initially, restore the ssi page back to the way you had it and then check the master page which uses the ssi.

   Posted 1 month ago
3. 

   wcamp
   

   offline

   Member

   That's a BIG relief, Gerry. Thanks for your reassuring words. I've removed from the SSI file what W3C told me to add. I then checked my "week15.php" page and it validated.

   Incidentally, I W3C-tested the SSI file because I noticed in Dreamweaver's code view the "1" in "line number one" of the SSI file was color-highlighted. So when I hovered over the colored "1," DW told me "Doctype must be declared first." Because of that DW advisory, I added the doctype and related entries, then checked the file on W3C. Presumably, DW doesn't distinguish between SSI file types and others.

   Nevertheless, I've added a hidden comment atop that SSI file as a reminder: "<!-- Do not add a doctype and related entries to this/these SSI files. -->" Unfortunately, after adding that reminder, DW still colors the "1" and insists that I first declare a doctype.     ( ; - (

   Thanks for your guidance, Gerry. That's how we become educated.

   Posted 1 month ago
4. 

   Gerry
   

   offline

   PVII Team

   Yep, the DW code checker does not distinguish between ssi pages and regular page so ti will attempt to warn you for the doctype. Just ignore these warnings on the ssi page.

   Posted 1 month ago

RSS feed for this topic

Reply

You must log in to post.