Websites Done a lot since my last review - can I get another now

I like the ones on the wdp. Keep them. Clicking gives me something to do while I am reading.

 

So john based on the code from above

Here's my code which works. I dunno what the difference is?

<!--webbot bot="Include" U-Include="includes/sidebar.htm" TAG="BODY" -->

It looks like you are using Frontpage 2003? That would explain why the code wouldn't work and change to yours.

 

Yes, John I can see why you should change!
Even MS said after 2009 FP2003 will drop support for the over bloated, problematic software.
Expression Web is not just a new, renamed FrontPage. It is a professional tool. Gone is the bloated code for which FrontPage was often criticized. Gone are the "web-bots" that wrote code proprietary to Internet Explorer. Expression Web not only helps you by writing valid XHTML by default, it helps you learn by highlighting (in code view) errors. This makes Expression Web a great learning tool. Many of the old FrontPage components have been removed from Expression Web like the problem in this post you have had. You will be closer to the w3.org validation.
It's almost like having the best of both worlds. Software which writes code for you and the ability to write code with a editor. It even has templates for the many other languages out there and codes acordingly. The beta version 2 years ago was slow, but feature rich, with the ability to set it for beginner, intermediate, advance. The final version is fast and lean. For MS this was a welcome surprise as they have been talking cross platform for years and finally delivered. The only reason I am a fan of MS products, is they are used by many corp customers, who require you to be certified. Thanks to the fact MS products always break, I always get paid to fix them. How nice of MS to create this cash flow for me.
Dave

 

Shouldn't the <!--Include--> instructions Pezboy mentioned in this post still work with my website?
Answer - No
FP includes, ASP includes, and PHP Includes are all different. I presume your sever has FP extensions turned on or you are on a Win Server. You must publish your site, not FTP it, correct. In fact include pages will work to some extent if you FTP, in that they will appear on the final pages. However if you update an include page the change will only appear on a final page once it has been opened, saved and FTPed again. This pretty much takes away any advantage of using includes. There are a number of reasons why you might need to use includes other than the FrontPage ones. The most important is probably in the case of sites which will be on a server without extensions, but also quite often scripts will require you to include content on pages and this cannot be done with FP includes.
The most commonly used alternative is using Server Side Includes (SSI). Setting these up is just the same as if you were using FP includes with a few minor differences. Many of these differences will also apply to other types of include.

First though, lets take a look at the code required to include content using SSI. This is what the SSI include directive looks like:
<!--#include file="page.txt" -->
This will work only if the file to be included is in the same directory as the final page, so, given that will usually not be the case, the more commonly used directive is:
<!--#include virtual="/directory/page.txt" -->
In this case it is very important that you get the path to your file correct.
Files which use SSI includes need to be named with an extension that alerts the server to check for include directives before serving the page. The most commonly used one is .shtml, but .shtm is also used. Most servers will not parse .htm or .html files for SSI but they can be configured to do so. Generally speaking this is only practical if you have a dedicated server since configuring the server to parse .html files would cause all standard HTML files served to be first parsed (or checked) for SSI, a situation which would cause some strain on the server.

When an FP file is included using FP includes, FrontPage takes care of ensuring that the paths to any images or links which are in the included page remain valid when the file is included, no matter where in the directory structure the final file is located. This is not the case with SSI. So, for example, if you have a header include file in the 'includes' directory and you include it in a page in the main directory it will go in precisely as written. That means that all links and image paths in it will be incorrect.

Why upgrade you can the use asp net or php greater power more stream line code. Fast page load times and reload (no re- rendering of previous pages). wow i got long in the tooth.

Cleandeck is just another cash flow which is on auto pilot.
I program in c++ ansii and oops, plus a few other languages. Something I did long ago and started again 2 years ago. (my Microsoft cash cows) Corp America said I am too old to practice as an engineer, so for 5 years I own a shipping store (good for shipping Cleandeck) now Fedex, UPS and DHL want all the money for themselfs. It was time to move on. Programming knows no age at least yet. I just have to compete with 300,000 budding young short minded kids from Rebmond WA and India, so I sided with old farts like myself and it's proving profitable. Plus no overhead.