Koozali.org: home of the SME Server

Legacy Forums => Suggestions => Topic started by: Harkonen on January 15, 2001, 07:56:23 PM

Title: PHP Nuke added to e-smith?
Post by: Harkonen on January 15, 2001, 07:56:23 PM

I see that you are using PHP-Nuke on your site and thought that this would be a nice feature to have available in e-smith. If I have not seen some documentation to that effect already, sorry in advance. I think that addition of this kind of software would make for a nice optional tool ...

Title: Re: PHP Nuke added to e-smith?
Post by: Tim Litwiller on January 20, 2001, 08:31:22 PM

I think there are to many questions that the user needs to answer to make installing PHP-Nuke part of the standard install.

Title: Re: PHP Nuke added to e-smith?
Post by: Gerald Jansen on February 16, 2001, 06:52:03 PM

Thanks for the reply. I checked out php.net and yes it appears to be quite straight forward. However, when I inserted some test code into an html document, residing in a virtual domain, it only displayed, didn't run. What must be done to activate the php engine on the e-smith server for a specific domain name. I have the feeling that some php modules must reside in the html folder in question. Any info you have would be appreciated. I am hoping to use php to avoid loading Front Page extensions.

TIA :-))

Title: Howto activate PHP (was PHP Nuke added to e-smith?)
Post by: Charlie Brady on February 16, 2001, 08:25:25 PM

Gerald Jansen wrote:
>
> Thanks for the reply. I checked out php.net and yes it
> appears to be quite straight forward. However, when I
> inserted some test code into an html document, residing in a
> virtual domain, it only displayed, didn't run. What must be
> done to activate the php engine on the e-smith server for a
> specific domain name. I have the feeling that some php
> modules must reside in the html folder in question.

Off topic for the wish list, but you need to name the file blah.php rather than blah.html.

> Any info
> you have would be appreciated. I am hoping to use php to
> avoid loading Front Page extensions.

That sounds like a very wise move.

Charlie