> > > Midgard doesn't use the DocumentRoot setting. Separate DocumentRoot
> > > settings for separate hosts have therefore allways worked as usual.
> > That`s just my bad english. I meant, that DocumentRoot now works for
> > Midgard VHosts.
>
> Just to get things clear: there's no such thing as a Midgard VHost.
> You can set MidgardEngine on per-vhost, but anything not handled
> by Midgard gets passed back to apache. As Midgard servers all
> content out of the database it doesn't use the DocumentRoot. The
> DocumentRoot (global or per-vhost) is something that apache will
> use when Midgard passes control back.
Stupid me, somehow i didn`t get the point :-)
> > Each VHost has it`s own DocRoot set, containing an image directory with
> > the images used for the styles, defined in Midgard Admin. And
> the strange
> > this is, that all images are present ! The next thing I did, was to
> > put all images in one DocRoot and use it for all Midgard hosts. The
> > result was the same. Only the admin site showes images. What
> could this be?
>
> If you try to access one of these missing images directly, what error
> is reported in the browser and the error_log?
Ok guys, this is truly idiotic. It was my fault. Since I`m coming from
NT i stumbled accross Unix and it`s access control. I just forgot to
allow Apache access to the docroot for two hosts, only the Admin Site
had the access rights set correct, so it was me, who had no Access to my
brain :-)))
After that one, if think i have stumbled across anything, a new user
could stumble. I fetched the latest manual from cvs and would start
with writing. Since i found out, how to go from source to a running
site, i would start with updating the install and config part for
current Midgard 1.2.4. That ok?
Daniel
--
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]
