Did not solve the problem :( It seems that even if every service has its own virtual host and every service has its own .htaccess file that apache does not recheck the settings and leave mbstring_func_overload at the last setting it reads out - at leas sometimes...
This would be a bug of apache - where should i post this?!? Michael Karrer schrieb: > It was a problem with apache and name based virtual hosts. > > sometimes it uses the overrides sometimes it wont... i think its a bug > in apache > > to make an sub domain and a virtual host entry for every service which > needs different php parameters did solve the problem. > > Patrick Schlaepfer schrieb: > >> So would be something like that. >> >> Add the following line in the .htaccess of the egroupware directory >> >> php_value mbstring.func_overload <value that egroupware needs> >> >> Never tried before, uninstalled egroupware... Could somebody pls >> verify, if it's working? >> >> php_value as it's not a Boolean value, Boolean value php_flag. >> >> >> >> -----Ursprüngliche Nachricht----- >> Von: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] Im Auftrag von Dmitry >> Dulepov [typo3] >> Gesendet: Mittwoch, 2. Januar 2008 12:27 >> An: [email protected] >> Betreff: Re: [TYPO3] egroupware + typo3 = PROBLEMS >> >> Hi! >> >> Patrick Schlaepfer wrote: >> >> >>> Tried to install typo3 and egroupware on the same server too. >>> The problem is located in the php part. >>> As far as I can remember it's in >>> >>> ; overload(replace) single byte functions by mbstring functions. >>> ; mail(), ereg(), etc are overloaded by mb_send_mail(), mb_ereg(), >>> ; etc. Possible values are 0,1,2,4 or combination of them. >>> ; For example, 7 for overload everything. >>> ; 0: No overload >>> ; 1: Overload mail() function >>> ; 2: Overload str*() functions >>> ; 4: Overload ereg*() functions >>> ;mbstring.func_overload = 0 >>> >>> where egroupware wants something else then typo3, and mixes up >>> the output of typo3. >>> >>> If you have control over the apache, you could start a second >>> apache on another part and using proxy_mod to forward the >>> egroupware things to that port. >>> >>> >> php_admin_flag should work in Apache configuration if PHP>=4.2.3 and even >> php_flag in .htaccess should do. >> >> >> > > _______________________________________________ > TYPO3-english mailing list > [email protected] > http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english > > _______________________________________________ TYPO3-english mailing list [email protected] http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
