I think you miss understand. I made a universal binary build of Apache2.2.4. It works. This is the only file we have compiled.
WiTango comes with plugins or modules for different servers (Apache 1, Apache 2, and Webstar). Apache doesn't use plugins it used modules they end in ".so". To enable a module you can copy it to Apache's modules folder or in a conf file tell it where it is. PHP5 works this way the .conf file tells apache to use a php5_module.so found in the /usr/local/php5 directory. Witango has two types of downloads of Witango server for the Mac. A PPC build and an Intel build. I don't know why they didn't do a universal binary build. the PPC build witango made comes with a module for Apache 2.0.5x. It is called mod_witango55_apache2.so. Because I tested this on Intel I tried the Intel build which doesn't work with 2.0.5x but 2.2.x and is called mod_witango55_apache22.so. So PPC witango only works with version 2.0.5x of Apache, and Intel witango only works with version 2.2.4 of Apache. Mark's PHP is built to run with Apache 2.2.4. Our options are the following: 1. Build Apache 2.0.53 universal or PPC (I did this last night) and build PHP to run with that version of Apache. 2. Run PHP and forgo Witango with Apache 2.2.4 3. Run Witango and for go PHP with Apache 2.0.5x Love you, John --- Stephen Arnold <[EMAIL PROTECTED]> wrote: > Support > It appears that the build you did on the > mod_witango55_apache22.so is for > Intel machines only, not a universal build or a PPC > build. > > Do you have one available? > Stephen > > The above was in reply to your inquiry, quoted as > follows: > > >Norm, > >First thing to do is check what version of the http > server you > >actually have. Use the following command: > > > >httpd -version > > > > > >It should be something like this: > > > >Server version: Apache/2.2.4 > >Server built: January 17 2007 22:04:53 > > > > > >The module was built using Apache 2.2.3 which is > the version of > >apache we recommend you use. We cannot predict how > earlier versions > >will work with the mod_witango55_apache22.so > module. > > > >The error is coming from the plug-in so the apache > server appears to > >be loading the witango module. Do not rename the > module. Make sure > >that the stanza is named exactly the same as the > module you are > >loading. The clients.ini file should look like > this: > > > >[Witango Client Definitions] > >mod_witango55_apache22.so= > > > >[mod_witango55_apache22.so] > >ERROR_HTML=/usr/local/WitangoServer/5.5/MiscFiles/clienterror.html > >REGISTER_EXTNS=tcf;taf;thtml;tml;wws > >REPORTCLIENTERROR=TRUE > >SENDFULLHEADER=false > >WITANGO_SERVER=127.0.0.1,18155 > > > > > >This is what should be in the httpd.conf file: > > > ># The following lines load the Witango 5.5 module > for Apache 2 to > >enable communication with the Witango Application > Server > >LoadModule WitangoModule > modules/mod_witango55_apache22.so > >WitangoModule mod_witango55_apache22.so > >AddType application/witango-application-file taf > tml thtml tcf wws > > > > > >If all else fails reset the permissions on the > WitangoServer > >directory so that it is wide open. We do not > recommend leaving it > >like this in a production or publically accessible > system but it will > >make it easier to troubleshoot. > > > >chmod -R /usr/local/WitangoServer > > > > > >Regards > > > >Witango Support > > > >On 05/07/2007, at 1:49 AM, [EMAIL PROTECTED] > wrote: > > > >> Hi, > >> > >> Has anyone actually got witango server 5.5 > working on Linux? > >> I have apache2 running nicely. > >> I downloaded the witango server 5.5 working for > Linux files and > >> tried to > >> get the plug-in going but it fails. > >> Only the mod_witango55_apache22.so will actually > load in apache2, > >> however when you come try to display > >> a .taf file in a web browser you get error > >> > >> Client/Plug-in Error > >> Error Code: 601 > >> > >> Unable to initialize the client's environment. > >> > >> An error occurred while parsing the config file > >> > /usr/local/WitangoServer/5.5/configuration/clients.ini > for client > >> mod_witango55_apache22.so. Check the file format > is correct and the > >> owner of the http process has file permissions to > read the file. > >> > >> which I believe means that apache2 has a problem > with interpreting the > >> clients.ini file. > >> > >> I have gone so as to give the file 777 > permissions and make it > >> owned by > >> www-data, I´ve also deleted the file completely, > nothing makes a > >> difference. Apache always looks in the same place > ie > >> /usr/local/WitangoServer/5.5/configuration but I > have no evidence that > >> it actually ever opens the clients.ini file. > >> > >> BTW, I using ubuntu > >> > >> thanks > >> Norm > >> > ______________________________________________________________________ > >> __ > >> TO UNSUBSCRIBE: Go to > http://www.witango.com/developer/maillist.taf > >________________________________________________________________________ > >TO UNSUBSCRIBE: Go to > http://www.witango.com/developer/maillist.taf > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to > http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
