It's in the trunk docs. It used to contain an error, but is corrected now.

Zend_Locale::$compatibilityMode = false;

/C


On Tue, Oct 21, 2008 at 1:12 PM, Bart McLeod <[EMAIL PROTECTED]> wrote:

>  Hi Thomas,
>
> I also get the error and I noticed that the reference guide does not know
> about compatibilityMode.
>
> Where is the migration chapter?
>
> I think I use Zend_Locale implicitly, because the problems appear in the
> translator, but I still get about sixty warnings scattered around my forms.
>
> Not happy about it, as you can imagine.
>
> On which component should we *simply *set compatibilityMode to false, and
> is this a static call, or should we be looking for a translator object or
> the like to set it on?
>
> Regards,
>
> Bart McLeod
>
> Thomas Weidner schreef:
>
> With r12003 there was also a new migration chapter added which would have
> answered your questions.
>
> According to the manual you can simply set compatibilityMode to false which
> supresses the warning but will activate the new API behaviour.
>
> When you use Zend_Locale only implicit there will be no problems.
> Otherwise you will have to migrate your scripts according to the migration
> chapter in the manual.
>
> Greetings
> Thomas Weidner, I18N Team Leader, Zend Framework
> http://www.thomasweidner.com
>
> ----- Original Message ----- From: "Pieter Kokx" <[EMAIL PROTECTED]><[EMAIL 
> PROTECTED]>
> To: "'Zend Framework General'" 
> <[email protected]><[email protected]>
> Sent: Saturday, October 18, 2008 12:21 PM
> Subject: [fw-general] Zend_Locale compatibility mode
>
>
> Hi,
>
> Since r12003 there is an compatibility mode added to Zend_Locale, which
> gives a warning. But I am not using Zend_Locale directly, only by
> Zend_Date and Zend_Translate. So, I don't know how to fix this problems
> with Zend_Date and Zend_Translate. Should these classes be updated so
> Zend_Locale will work again without the warning? Or is it something that
> I should fix myself?
>
> --
> Regards,
>
> Pieter Kokx
> MaakSite.net
> PHP Developer
>
>
>
>

Reply via email to