You know, I assumed it was the midgard engine that I couldn't turn off....
But the more I look at it, it looks like something that I'm doing in one of
my php scripts must be sending the midgardized PHP for a fit. I get an error
like this on a page that used to run under standard PHP, and I just assumed
it was the Midgard engine:
... parse error, expecting `MIDGARD_TMPLE' in
/home/concord/public_html/index.htm on line 10...
Since I can see no evidence of the M engine running here...I'm going to see
what it could be about my script that's giving me trouble. Even when I make
my script the DocmentRoot, I get the problem. So it's probably not what I
thought before.
-paul
Emiliano wrote:
> > I have Midgard working well on my one domain: adelie.net Here I get
> > HTML from my DocumentRoot..
> >
> > I am not rich in IP's so I configured a couple of hosts:
> > adelie.net:8000 and an admin site: adelie.net:8080 to work
> > with Midgard...going great so far...
> >
> > My problem is that other Apach VirtualHosts named:
> > somehost.adelie.net are being parsed by the Midgard engine and
> > of course this is very bad... (bad Midgard, bad. sit.... ;)
>
> I'd like to see the VHost definitions and the contents of the host table.
> This should most definately not be happening.
>
> Emile
>
> --
> This is The Midgard Project's mailing list. For more information,
> please visit the project's web site at http://www.midgard-project.org
>
> To unsubscribe the list, send an empty email message to address
> [EMAIL PROTECTED]
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
