Quote:
A php page source is entirely different to standard HTML.
Web Designer hasn't been designed to create PHP scripted sites.
Yes I understand this fact.
I am not suggesting that XWD does or should create php pages.
Quote:
There is away around it, and that is to use the <? includes_once "";?> or <? required_once "";?> code,
This way it will include the PHP function you want to use, without altering the HTM/HTML output.
Simply just use the "Replace with HTML" in the Website properties - placeholder dialog box.
Yes I do this now.
Quote:
however, you do need to use the .php file extension on your pages, and to have the code or function on a seperate file eg: phpcode.php
Yes exactly! This is exactly why I am asking for the ability to change the file extension. With other web builders, I can choose an extension to match my scripts. The pages are generated in html only and scripts work fine.
Quote:
You can take any html page and change the extention to php and the file will display the same. The only difference is that the server will parse the file for any php. If nothing is found, just the html is displayed.
php and html mix very well in a file.
Yes. I agree. Have done this for years to run specific includes. Works well.One example: a secure php form script uses includes but will only work with the .php extension. The rest of the page is standard html. The htaccess file is set to read these files just fine. I have this script running on 4 websites, all written in html, each has a .php file extension to work with the includes.
Quote:
Some servers are set to parse all files with .htm or .html, looking for php scripts but obviously this is inefficient of only 1 page in 100 has any. So most servers will only parse for php if the suffix is .php.
It would be a help if you can specify the suffix in XWD.
Yes. It would!!
Quote:
however I did notice that I had to use a php editor to change the file extension from htm to php.
Exactly. XWD will not change the extension so every time it exports and publishes, it must be modified manually and uploaded manually to the site. This is truly redundant work. If you modify the page just once a week, over a year that is 52 edits to the .php extension and 52 manual uploads that could be simply avoided if the program allows assignment of file extension.
The problem is magnified further because at this time, XWD updates all page every time it publishes. So each time, it would send the filename.htm file to the web instead of a filename.php. Now there is manual effort to remove the .htm version of the page since it is not needed or wanted.
Manually editing the file extension is not difficult but add it up.
Time really adds up for something that could be easy for the user to specify using a simple drop-down box with choice of page extension: htm (default), asp, php, shtml.
The manual can simply state that all pages are written in html code. The choice of file extension is allowed for use of included scripts that require a specific file extension. Please consider this for the wish list. It would greatly extend the ability of XWD.