www.DwFAQ.info wrote:

 

Run the workflow and you'll have all the selected file extensions that previously had .html extension now renamed to .php

I haven't tried that, but renaming the files outside Dreamweaver will result in all internal page links breaking. Unfortunately, Dreamweaver doesn't have a feature that batch processes file renaming.

www.DwFAQ.info wrote:

 

Just like with Automator relinking pages in DW is as easy as using find/replace. Open DW, go to find/replace, find .html and replace with .php and there ya go. That's what find/replace is used for isn't it - finding and replacing things

Sure, but if you use that sledgehammer approach, you'll convert every external link that ends in .html, too. It's not quite as straightforward as you seem to think.

You can also use a regular expression to avoid replacing unwanted extensions. It's actually a lot easier than you would think.

If it's so easy, perhaps you would like to provide boloco with the appropriate regular expression to identify external links. It's not impossible, but it would need to be very thoroughly tested before running it through 300 pages. Just telling someone to run Find and Replace on a large number of pages without thinking through the possible consequences is not very helpful.

Certainly, you can run html files on a dynamic site. There are two possible scenarios:

• The server is configured to treat .html files as .php files.
• The .html files don't contain any PHP code.

In the first scenario, the server automatically passes all files to the PHP engine. If you're on shared hosting, your hosting company is unlikely to agree to this, but you can certainly ask.

In the second scenario, you can convert your files to .php as and when you add PHP code to a file. The problem with this approach is that URLs bookmarked by others will break each time you change. When creating a PHP site, I always use .php file name extensions, even if the page isn't dynamic, because it allows me to add PHP code at any stage later on.