Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45561 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 89957 invoked from network); 11 Sep 2009 06:49:12 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 11 Sep 2009 06:49:12 -0000 Authentication-Results: pb1.pair.com header.from=larstorben@gmail.com; sender-id=pass; domainkeys=bad Authentication-Results: pb1.pair.com smtp.mail=larstorben@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.222.195 as permitted sender) DomainKey-Status: bad X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: larstorben@gmail.com X-Host-Fingerprint: 209.85.222.195 mail-pz0-f195.google.com Received: from [209.85.222.195] ([209.85.222.195:34034] helo=mail-pz0-f195.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9D/14-00376-6E2F9AA4 for ; Fri, 11 Sep 2009 02:49:10 -0400 Received: by pzk33 with SMTP id 33so685182pzk.24 for ; Thu, 10 Sep 2009 23:49:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=OZrfElDA1H1E2u2oNerQSj9+toTfsUAirdFE/k980qU=; b=TurBAUHvZvNnLkZlqOzTSImXbd7W4TUn824whj0p7LRLWV3yTVqg6o18sc1NiBuuLQ lAscvdnbo0IJWjNSC25nf1OPc+8HLyVnfkD4L3DZ4+kiCRY/dcgntjoBeMMgk7d+buQK 2ljFXuX5/qy2xzGbfVCyF4z8XGcU29wMIKeD0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ucrNzkkrOatriNasCEylIL1M4yixU3pzOvwAsegXT4ZpeEew7KM4bGXB/c2fDcTPiy hsFRPHKn53euPUg49eT0FHL2rNCGRTi3Cv4I2tLlb0Mix9UzLjJZ/puiOZjYkalvRYTG GioMMAT1xU/GShwVwsbvsZjqEUOGPYryKn4Dg= Received: by 10.115.101.10 with SMTP id d10mr4755445wam.61.1252651747574; Thu, 10 Sep 2009 23:49:07 -0700 (PDT) Received: from ?192.168.1.152? (S01060011d8ae1ca0.gv.shawcable.net [24.108.101.234]) by mx.google.com with ESMTPS id 20sm541253pzk.9.2009.09.10.23.49.05 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 10 Sep 2009 23:49:06 -0700 (PDT) Message-ID: <4AA9F2DE.4000609@gmail.com> Date: Thu, 10 Sep 2009 23:49:02 -0700 User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: jani.taskinen@iki.fi CC: Tony Marston , internals@lists.php.net References: <83.35.38554.204D7AA4@pb1.pair.com> <40100.4e3f9432.1252518200.nsm@avilys.eik.lt> <4A.C8.06945.E06B8AA4@pb1.pair.com> <1674.c316b4e9.1252580285.nsm@avilys.eik.lt> <2E.A1.42016.120F8AA4@pb1.pair.com> <4AA8F383.3040305@dmi.me.uk> <4AA92866.3010209@iki.fi> In-Reply-To: <4AA92866.3010209@iki.fi> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] mb_string.func_overload has secretly been changed from PERDIR to SYSTEM From: larstorben@gmail.com (Lars Torben Wilson) Jani Taskinen wrote: > On 09/10/2009 04:46 PM, Tony Marston wrote: >> You are missing the point. I'm not trying to set the encoding for any >> HTML >> output as that is handled differently. What I am concerned about is the >> func_overload option which, ever since PHP 4.2.0, we have been able to >> turn >> on or off using an htaccess directive on a PERDIR basis. Although neither >> the documentation nor the release notes have been changed the PERDIR >> option >> has disappeared and it is now set either on or off for the entire >> system and >> cannot be modified with any htaccess or ini_set directive. >> >> So if func_overload is turned on, how do I turn it off? If it is >> turned off >> how do I turn it on? >> >> Considering that phpMyAdmin does not like it to be turned on, this is >> not a >> trivial point. > > Simply doing a search in the bug system would have revealed the current > status of this: > > http://bugs.php.net/bug.php?id=49189&edit=1 > > The documentation team just hasn't got around changing the docs yet and > adding a note about it there. Feel free to provide a patch or forever be > silent. > > --Jani No need, fixed in the doc svn. Torben