>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 1/8/01, 5:35:54 PM, Christian Ledermann <[EMAIL PROTECTED]> 
wrote regarding [midgard-user] Midgard 1.4 installation problems:


> Yet another problem:
> when I call the asgard site via    127.0.0.1:8102/admin Netscape tries to 
download the File index.html of type
> application/x-httpd-php-midgard.

Hmmm... I am very curious about what you have done to install midgard 
here. midgard.conf as it comes with the distribution has
this:

        LoadModule midgard_module modules/mod_midgard.so
        AddModule mod_midgard.c

        LoadModule php3_module modules/libphp3.so
        AddModule mod_php3.c

        AddType application/x-httpd-php3 .php3
        AddType application/x-httpd-php-midgard .mgd

The last line specifies the mime-type you mentioned for files that are 
suffixed with .mgd. This is meant for filetemplates, an experimental feature.

If your installation instructions looked like this:

        This is the 1.4 something admin site and framed 
        admin site in filetemplates.
        In order to use these applications you must 
        do the following:

        ** Add these directives to your apache config:

        DirectoryIndex index.mgd
        AddType application/x-httpd-php-midgard .mgd
        MidgardTemplate phpelements.xml

        ** Create a non-prefixed host that requires 
        authentication that maps to a virtualhost that 
        offers the documentroot that you'll place this under.

        ** edit phpelements.xml in the root directory and 
        change the variable mgdroot to the installation 
        directory (search for CHANGE)

        ** Unpack the 1.4 images in the installation directory 
        of the admin site (framed admin has images included).

, then unless you help development by experimenting with this feature and 
providing us with feedback, this is not what you wanted. I think your 
best bet in that case would be to start from scratch. Please let us know 
if this was the case, then we will add some extra warnings to prevent 
anyone else going the wrong path.

If the above is not the case, then I don't really know what happened, and 
I'd like to have some extra information.

- Very brief, what steps did you take to install.
- Set 'LogLevel debug' in httpd.conf (By default is there is
  a line 'LogLevel warn', find it, change it and restart apache.
- Try to access asgard again and look in the errorlog for relevant
  messages. Post them here (not the full file, just the output of
  one request)
- check if the php module that gets loaded is actually midgard-php,
  and not by accident the php you had installed earlier (if at all
  possible.

Hope it helps, I am completely guessing at this one. I am very curious 
about this one, so please keep us posted.

Armand.




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to