On Wed, 2005-07-20 at 02:42, Rasmus Lerdorf wrote:
> Robert Cummings wrote:
> [-- snippity --]
> > You're only
> > relief is to tone down the error reporting level (Which will knock out
> > other notices during development but will be great for a production
> > server), or do as I did and install a
Robert Cummings wrote:
> On Tue, 2005-07-19 at 22:10, Jason Wong wrote:
>
>>On Wednesday 20 July 2005 07:32, Marc G. Fournier wrote:
>>
>>
>>>Which is? If its:
>>
>>Yep.
>>
>>
>>>; at function call time. This method is deprecated and is likely to be
>>>; unsupported in future versions of PHP/Zen
On Tue, 2005-07-19 at 22:10, Jason Wong wrote:
> On Wednesday 20 July 2005 07:32, Marc G. Fournier wrote:
>
> > Which is? If its:
>
> Yep.
>
> > ; at function call time. This method is deprecated and is likely to be
> > ; unsupported in future versions of PHP/Zend. The encouraged method of
>
On Wed, 20 Jul 2005, Jason Wong wrote:
On Wednesday 20 July 2005 07:32, Marc G. Fournier wrote:
Which is? If its:
Yep.
; at function call time. This method is deprecated and is likely to be
; unsupported in future versions of PHP/Zend. The encouraged method of
; specifying which argumen
On Wednesday 20 July 2005 07:32, Marc G. Fournier wrote:
> Which is? If its:
Yep.
> ; at function call time. This method is deprecated and is likely to be
> ; unsupported in future versions of PHP/Zend. The encouraged method of
> ; specifying which arguments should be passed by reference is i
yOn Wed, 20 Jul 2005, Jason Wong wrote:
On Tuesday 19 July 2005 23:17, Marc G. Fournier wrote:
Just upgraded to 4.4.0 ... several "legacy applications" that we have
installed now break with the above error message ... specifically,
older installs of Horde, but I've seen reports of other apps ..
On Tuesday 19 July 2005 23:17, Marc G. Fournier wrote:
> Just upgraded to 4.4.0 ... several "legacy applications" that we have
> installed now break with the above error message ... specifically,
> older installs of Horde, but I've seen reports of other apps ...
>
> Without reverting back to 4.3.11
Just upgraded to 4.4.0 ... several "legacy applications" that we have
installed now break with the above error message ... specifically, older
installs of Horde, but I've seen reports of other apps ...
Without reverting back to 4.3.11, is there a way I can temporarily fix
this while working
8 matches
Mail list logo