server side includes

Forum Moderators: phranque

Message Too Old, No Replies

server side includes

sabrawv

10:01 pm on Sep 16, 2004 (gmt 0)

i have developed a website using server side includes. when i view the source, i have multiple head and body tags, etc. will this present a problem? everything displays fine in the browsers, but i am wondering if the multiple tags will effect the search engines abiltiy to find info. i guess i could take the tags out on the included pages, but then i can't see the formatting in frontpage. any help on this appreciated. thanks.

moltar

10:51 pm on Sep 16, 2004 (gmt 0)

You have to take the out. This is the whole point of the SSI. You can include blocks of code that repeat from page to page. You will be left with the problem of not being able to see the pages in FP though. There is no solution.

pleeker

10:55 pm on Sep 16, 2004 (gmt 0)

The included file should not have all the <head> and <title> tags and elements, etc. Take 'em out and learn to edit without needing to see it in FrontPage.

bill

4:10 am on Sep 17, 2004 (gmt 0)

FrontPage Includes [webmasterworld.com] can only replace what's between the

<body></body>

tags. If you are looking to replace stuff in the

<head>

then you need to use real SSI.

You might want to develop the site in FP and then add the SSI last. If you really want to use the WYSIWYG aspect of FP then you may want to limit your use of SSI to the FP Include Page and leave the stuff between head tags alone.

sabrawv

1:30 pm on Sep 20, 2004 (gmt 0)

thanks to all. that was what i was afraid of. i don't have any trouble editing straight html. i just like to see immediate results. i guess i will keep them in until it's time to post, then remove them all. just curious, what is the issue as they seem to display ok in browsers with the multiple tags. is it a problem with the search engines?

Sanenet

1:54 pm on Sep 20, 2004 (gmt 0)

Problems with multiple HTML and HEAD start tags:

- Only the latest browsers support this, due to multiple error tolerance. Older / specific browsers (ie, text browsers, speaking browsers, crawlers) will get confused.

- Crawlers won't like it.

Remember, at the end of the day you are using the scripting commands to inform the browser what it needs to do. Incorrect code will slow the browser down, results in erroneous pages, crawlers won't bother to look too closely, etc.