Hi,
in my current hosting, I can't use SSI Include command like this:
<!--#include virtual="/inc/header.txt" -->

I think it's very weird. :rolleyes:
Because in some another hosting, the include method like that worked!

Anyone know why it's not work?:rolleyes: :rolleyes:

To eliminate the obvious, do they say they support SSI at all?

Yes, but only SSI code like this will work on their server:
<!--#include virtual="./inc/header.txt" --> and <!--#include virtual="../inc/header.txt" -->
(with . before slash)

I have many files using <!--#include virtual="/inc/header.txt" --> :(

Any idea to solve this problem?:rolleyes:

It's definitely all in the environment, when you declare a / before a folder, most systems look to the root directory of the machine and build from there.


I'm willing to bet that this would work on your current system:

<!--#include virtual="inc/header.txt" -->

I'm not sure there is an 'easy' way to fix this...

Originally posted by Orpheus1539

I'm willing to bet that this would work on your current system:

<!--#include virtual="inc/header.txt" -->

Yes, this one is work also, but as I told you before... I have many files with SSI code like this: <!--#include virtual="/inc/header.txt" -->
:(
Could anybody explain why they're different?
:rolleyes:

Originally posted by Orpheus1539

I'm not sure there is an 'easy' way to fix this...
:bawling: :bawling: :bawling:

The difference has to do with the way they have the document root configured in the server. For them

./ means the current user directory (where your files are)

/ means the servers root directory (which you don't have access to)

It looks like you will have to edit your files to change "/" to "./".

I think almost web hosting allowed using "/" path for SSI and PHP. CMIIW..
So, could you explain which one's better? Using "/" or "./"?:rolleyes:

How to tell my hosting to enable "/"?
They still with "./" :bawling:

I've no idea why they want to use "./" instead of "/"... :mad: