Hi - I have a page with two php includes which no longer display properly. They were fine when I set them up, and I haven't changed anything. They don't display online - and also don't display on my local server (Apache). I have identical code on other sites which does display properly, both on my server and online. There's nothing wrong with the file paths as they display correctly on the DW display screen, and also on live display, so I'm completely baffled.
Can anyone shed any light?
Here's a sample page - http://www.lucidinsight.com/travelprev.shtml
The includes should both be displaying on the right side of the page (hence the two error messages)
Thanks!
Hi...contrary to all logic and expectations, shtml pages DO process php includes. I appreciate that this seems very strange but I have several examples on my sites, with identical code to that already posted, and they work. I have to use a .php file extension rather than .asp as this is required for the file to be read by an online CMS site - rather than change the page to a php file and have to amend the site navigation, I have gone with just changing the file extension. This works for every single one of my sites except this one, and I can't see why, hence this question...
SW
Is this hosted on the same servers that works? If I save a file as .shtml with php scripts, it will not process them on one of my servers. The other is classic asp so I can't test it there. But on the one the has php, the ssi do not get processed, but I don't get an error. I would create a simple SSI and use the <!--#include virtual="/assets/includes/testssi.shtml" --> on a test page and see if that works. Easy way to test what bregent said.
Jim
Hi Jim - that's definitely the explanation. The site is hosted on a different server to the others that work - it did work though until recently but I guess they've changed one of the settings. The include has to be php for the cms to work, so I've changed the code and the page is now a php page - annoying as I've had to update the menu and links, but at least now I understand why it happened.
SW
North America
Europe, Middle East and Africa
Asia Pacific