Some Answers to Emile and Philipp:

> Huh? Has anyone else seen this? It should be sufficient to set the
> extension_path in php.ini.

I've tested again some varieties and I always get "PHP Fatal error:  
Cannot get midgard module descriptor in Unknown on line 0" from the php 
preparser. 

As you said, the "normal" way to operate midgard is completely from the 
db - without php code in the doc root. Here are the files again:
in usr/lib/apache: mod_midgard.so, midgard.so
in usr/lib/php/extensions: midgard-root.php

/etc/httpd/httpd.conf refers to /etc/httpd/midgard-data.conf.
midgard-conf contains:

## Uncomment these if you want to use filetemplates
# MidgardTemplate phpelements.xml
# AddType application/x-httpd-php-midgard .mgd

## Uncomment this for PHP3,
## MidgardRootFile "/usr/lib/php/extensions/midgard-root.php3"
## or this for PHP4
MidgardRootFile "/usr/lib/php/extensions/midgard-root.php

php.ini contains:

extension_dir   =       /usr/lib/apache
; MIDGARD
extension = midgard.so

This should direct php/apache to midgard.so, eh?. When I restart apache 
all ist fine, at least during the loading process for httpd. I can also 
connect with the browser to any html files. But any time I connect to 
.php files, I get 

[23-Apr-2001 14:52:15] PHP Fatal error:  Cannot get midgard module 
descriptor in Unknown on line 0

For ANY .php or .php3 file! Consequently, the php connect fails. 
Meanwhile,  I already have in httpd.conf:

---------------------------
    #
    # And for PHP 4.x, use:
    #
    <IfDefine PHP4>
   AddType application/x-httpd-php .php .php3 .phtml .php4
   AddType application/x-httpd-php-source .phps
    </IfDefine>
---------------------------

If I IN-activate the "extension = midgard.so" entry from php.ini, all 
my OTHER .php projects are functional again and there is no "Fatal 
error" in the php parser log.

> Or rather, be fixed. Either in Midgard, or, as it looks to me in this
> case, in PHP. PHP extension loading should not, in general, require
> changes to you dynamic loader setup. It never did for me.

I have NO problem with my php setup itself. it works fine, as long as I 
dont add "extension = midgard.so" into php.ini

> Midgard serves its content from the database so this directory
> doesn't need to exist.

OK, consequently I get no reply at all when entering 
http://locutus.netzwissen.de:80/admin/. But that's clear as long as the 
"midgard.so" is not loaded correctly. We should first work on this 
problem.

> Probably because you haven't uncommented the MidgardTemplate calls et
> al. T\You don't need this for general midgard access BTW.

OK, let us proceed with a standard setup and without filetemplates. I 
would prefer getting everything from the DB.

> While you are right the install needs to be simpler yet, it has made
> great strides since 1.2 (trust me on this). But why would you loose
> two days of your time, and not consult the mailinglist?

You're right and I do believe its getting better. That's one reason for 
these talks here... I only wanted to say that the install descriptions 
still have some way to go ;-) 

BTW:  If the midgard connects to he midgard DB, where can I adjust the 
connect data (login user, PW). Normally, I would have expected this to 
be part of the midgard-root.php. I defined it during install but where 
can I change this afterwards?

-- 
-------------------------------------------------------
Thomas M. ROTHER - "netzwissen" - D-73728 Esslingen
F.R. Germany/EU
 - http://www.netzwissen.de (Updated!)
Public PGP Key available from http://www.keyserver.net
-------------------------------------------------------



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

Reply via email to