Preview defaults to Notepad for .shtml documents
Moderator: kfury77
Forum rules
Please try to follow these guidelines. This will help to receive faster and more accurate response.
Please try to follow these guidelines. This will help to receive faster and more accurate response.
- Check the Support section of the corresponding product first. Chances are you will find your answer there;
- Do not create new topics for already reported problems. Add your comments to the existing topics instead;
- Create separate topic for each problem request. Do NOT post a number of non-related problem reports in a single topic;
- Give your topic a meaningful title. Titles such as "A question," "Bug report" and "Help!" provide others no clue what your message is about;
- Include the version number of the software you are using;
- This is not an official customer support helpdesk. If you need a prompt and official response, please contact our support team directly instead. It may take a while until you receive a reply in the forum;
Preview defaults to Notepad for .shtml documents
The hosting company my primary website had been on for 10 years recently went out of business. The website hadn't been updated in almost 7 years, so I've been franticly re-writing it's 30 or so pages.
I used SSI for menus, copywright notice, etc., on the old website.
An .htaccess file that I think was in the root directory contained two lines that made it un-necessary to use the .shtml extension:
AddHandler server-parsed .html
Options +Includes
On the new server, SSI doesn't work without the .shtml extension. What's worse is WeBuilder defaults to notepad for .shtml documents.
Help
I used SSI for menus, copywright notice, etc., on the old website.
An .htaccess file that I think was in the root directory contained two lines that made it un-necessary to use the .shtml extension:
AddHandler server-parsed .html
Options +Includes
On the new server, SSI doesn't work without the .shtml extension. What's worse is WeBuilder defaults to notepad for .shtml documents.
Help
IE or Firefox has never had a problem displaying .shtml pages on the internet, just internally stored documents. Regardless of why it happened, that problem is now solved.
Because this is an existing website with search engine traffic I don't want to loose, I'm really concerned about what will happen when a search engine tries to take someone to a .shtml page it expects to have a .html extension. The windows server the website is on now doesn't seem to be able to parse .shtml to .html.
I may have to find a replacement language to link the menus and copyright notice for SSI on about 30 pages on my website.
Because this is an existing website with search engine traffic I don't want to loose, I'm really concerned about what will happen when a search engine tries to take someone to a .shtml page it expects to have a .html extension. The windows server the website is on now doesn't seem to be able to parse .shtml to .html.
I may have to find a replacement language to link the menus and copyright notice for SSI on about 30 pages on my website.
- syrupcore
- Top Contributor
- Posts: 917
- Joined: Thu Jul 21, 2005 12:58 am
- Location: Portland, Oregon, usa
- Contact:
rick, php includes couldn't be easier and you are not confined to apache. IIS might be able to deal with ssi but I don't think so - not natively anyway.
ps. The reason your browser can't display local .shtml files is because .shtml requires a web server. there are ways around it, but that's the general idea. the same will be true of your local php files - they need to be served up by a webserver for your browser to understand them. Webuilder comes with a server for this reason.
Code: Select all
<?php include("header.php") ?>
your content
<?php include('menu.php") ?>
more content
<?php include("footer.php") ?>