To my knowledge, if you wish to use a Frontpage include, it must be created from the Frontpage client. The reasons for this are twofold:
1) Frontpage creates a checksum for each include that is generated at the time of creation.
2) Frontpage includes are not wholly dynamic, you cannot forinstance include CGI output very well with their includes. They are best suited for HTML alone. This is caused by the way Frontpage includes the item inline. When a document with an include is read, it is parsed by the server. The extension reads the include, and then, it detemines if it has been updated. If it has, it physically includes the information not only in the output, but it also changes the html on site. This can be evidenced by opening a saved FP document in either a 3rd party editor or FP Editor. Viewing the source, you will see the actual content bordered by the WEBBOT structure that FP uses for an include. This is generally a pain in cases of CGI output, because the FP parser will not always see that an update has occured or simply will not output anything at all.
FP also parses content based on what is between the BODY tags of a document, I have gotten unexpected results by including raw HTML without BODY tags, which is more common in standard SSI.
Hope this helps.
1) Frontpage creates a checksum for each include that is generated at the time of creation.
2) Frontpage includes are not wholly dynamic, you cannot forinstance include CGI output very well with their includes. They are best suited for HTML alone. This is caused by the way Frontpage includes the item inline. When a document with an include is read, it is parsed by the server. The extension reads the include, and then, it detemines if it has been updated. If it has, it physically includes the information not only in the output, but it also changes the html on site. This can be evidenced by opening a saved FP document in either a 3rd party editor or FP Editor. Viewing the source, you will see the actual content bordered by the WEBBOT structure that FP uses for an include. This is generally a pain in cases of CGI output, because the FP parser will not always see that an update has occured or simply will not output anything at all.
FP also parses content based on what is between the BODY tags of a document, I have gotten unexpected results by including raw HTML without BODY tags, which is more common in standard SSI.
Hope this helps.
