Dreamweaver as PHP editor

I'm just getting into PHP, and have found that as a PHP code editor, Dreamweaver works pretty well (with the extension I installed). My question is this, whenever I save a file with the .inc extension, which is a PHP include file, all of the color coding goes away, as does the PHP tab on the tool bar. Is there any way to make Dreamweaver see a .inc file as a PHP file? I looked on all the menus and in the preferences, but I couldn't find an obvious way to do this. Thanks!

Dreamweaver see a .inc file as a PHP file?

The problem is that DW uses the file extension to determine what kind of
code is on the page. .inc doesn't mean anything specific, so DW doesn't know
what type of code you are using.

That said, can't PHP include any file? Could you just name it include.php or
include.html depending on the contents?

-Darrel

http://www.macromedia.com/support/dr...add_ext_mx.htm


--
----------------------------
Massimo Foti
http://www.massimocorner.com
----------------------------

Susi_S webforumsuser wrote:

Is there any way to make Dreamweaver see a .inc file as a PHP file?

The easy way: Name your files *.inc.php. With this double extension you
know that the files are includes and any other program knows that the
files contain PHP-code.

Micha

On Mon, 01 Dec 2003 22:15:08 +0100, Michael Fesser <netizen (AT) gmx (DOT) net>
wrote:

The easy way: Name your files *.inc.php. With this double extension you
know that the files are includes and any other program knows that the
files contain PHP-code.

And any PHP code in the file will be executed before the content is
sent to a browser, thereby protecting any user name or passwords that
might be contained in the file.


Gary

Gary White wrote:

And any PHP code in the file will be executed before the content is
sent to a browser, thereby protecting any user name or passwords that
might be contained in the file.

True, but such situations can be avoided with storing the PHP-includes
and config-files outside the document root (making them not accessible
via HTTP). Even if the webserver is misconfigured and returns the files
unparsed only the include-statements in the pages will be returned, but
not the included files with the critical code.

Micha

On Mon, 01 Dec 2003 23:59:39 +0100, Michael Fesser <netizen (AT) gmx (DOT) net>
wrote:

True, but such situations can be avoided with storing the PHP-includes
and config-files outside the document root (making them not accessible
via HTTP). Even if the webserver is misconfigured and returns the files
unparsed only the include-statements in the pages will be returned, but
not the included files with the critical code.

True.


Gary