Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread Robert Cummings

On 11-02-16 09:45 AM, Daniel P. Brown wrote:

On Wed, Feb 16, 2011 at 09:41, David Hutto  wrote:

On Wed, Feb 16, 2011 at 9:41 AM, David Hutto  wrote:

Only those who live in glass houses, should hide their errors.




if that makes sense.


 Did you even bother to read the whole of what I said?  I wasn't
advocating it as a solution, I simply said it was a temporary fix
pending a real resolution.


Just plop a .htaccess file (or modify one if it already exists) into the 
typo3 root web folder. In it disable E_DEPRECATED warnings. Also, the OP 
appears to have introduced errors by renaming ereg to preg. Did he check 
the syntax for preg versus ereg? His delimiters are conflicting with the 
pattern or are non-existent.


Cheers,
Rob.
--
E-Mail Disclaimer: Information contained in this message and any
attached documents is considered confidential and legally protected.
This message is intended solely for the addressee(s). Disclosure,
copying, and distribution are prohibited unless authorized.

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread Richard Quadling
On 16 February 2011 14:34, Daniel P. Brown  wrote:
> On Wed, Feb 16, 2011 at 07:15, Richard Quadling  wrote:
>> On 16 February 2011 11:25, Andre Polykanine  wrote:
>>> Hello Fotoo,
>>>
>>>           >> error_reporting(0);
>>
>> Really?
>>
>> You consider shoving your head in the sand a REALISTIC option?
>
>    Well, at the least, it would shut the errors up in the meantime,
> pending an actual resolution.  However, the use of short_open_tags may
> completely defeat the intended purpose.
>
> --
> 
> Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
> (866-) 725-4321
> http://www.parasane.net/
>

Because some of the code has been edited, it is now broken. Hiding the
errors at that stage is really driving with your eyes closed.

If the changes are reverted, so that ereg is still used rather than
preg, and the deprecation notices suppressed, then that maybe the best
place to be for the short term.


-- 
Richard Quadling
Twitter : EE : Zend
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread Daniel P. Brown
On Wed, Feb 16, 2011 at 09:41, David Hutto  wrote:
> On Wed, Feb 16, 2011 at 9:41 AM, David Hutto  wrote:
>> Only those who live in glass houses, should hide their errors.
>>
>
>
> if that makes sense.

Did you even bother to read the whole of what I said?  I wasn't
advocating it as a solution, I simply said it was a temporary fix
pending a real resolution.

-- 

Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
(866-) 725-4321
http://www.parasane.net/

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread David Hutto
On Wed, Feb 16, 2011 at 9:41 AM, David Hutto  wrote:
> Only those who live in glass houses, should hide their errors.
>


if that makes sense.
-- 
According to theoretical physics, the division of spatial intervals as
the universe evolves gives rise to the fact that in another timeline,
your interdimensional counterpart received helpful advice from me...so
be eternally pleased for them.

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread David Hutto
Only those who live in glass houses, should hide their errors.

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread Daniel P. Brown
On Wed, Feb 16, 2011 at 09:37, David Hutto  wrote:
>
> What was the intended purpose again?

The hiding of errors.

-- 

Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
(866-) 725-4321
http://www.parasane.net/

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread David Hutto
On Wed, Feb 16, 2011 at 9:34 AM, Daniel P. Brown
 wrote:
> On Wed, Feb 16, 2011 at 07:15, Richard Quadling  wrote:
>> On 16 February 2011 11:25, Andre Polykanine  wrote:
>>> Hello Fotoo,
>>>
>>>           >> error_reporting(0);
>>
>> Really?
>>
>> You consider shoving your head in the sand a REALISTIC option?
>
>    Well, at the least, it would shut the errors up in the meantime,
> pending an actual resolution.  However, the use of short_open_tags may
> completely defeat the intended purpose.
>
> --
> 
> Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
> (866-) 725-4321
> http://www.parasane.net/
>
> --
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

What was the intended purpose again?

-- 
According to theoretical physics, the division of spatial intervals as
the universe evolves gives rise to the fact that in another timeline,
your interdimensional counterpart received helpful advice from me...so
be eternally pleased for them.

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread Daniel P. Brown
On Wed, Feb 16, 2011 at 07:15, Richard Quadling  wrote:
> On 16 February 2011 11:25, Andre Polykanine  wrote:
>> Hello Fotoo,
>>
>>           > error_reporting(0);
>
> Really?
>
> You consider shoving your head in the sand a REALISTIC option?

Well, at the least, it would shut the errors up in the meantime,
pending an actual resolution.  However, the use of short_open_tags may
completely defeat the intended purpose.

-- 

Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
(866-) 725-4321
http://www.parasane.net/

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread Richard Quadling
On 16 February 2011 11:25, Andre Polykanine  wrote:
> Hello Fotoo,
>
>            error_reporting(0);

Really?

You consider shoving your head in the sand a REALISTIC option?


-- 
Richard Quadling
Twitter : EE : Zend
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php



Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread Andre Polykanine
Hello Fotoo,

   http://oire.org/menelion (mostly in Russian)
Twitter: http://twitter.com/m_elensule
Facebook: http://facebook.com/menelion

 Original message 
From: fo...@gmx.de 
To: php-general@lists.php.net
Date created: , 11:12:13 AM
Subject: [PHP] errors after upgrade vom 5.2.10 to 5.3.0  howto solve or hide?


  Hi everyone!


after upgrading vomn php 5.2.10 to 5.3.0 I get a lot of errors. I changed 
already in some files ereg_replace() to  preg_replace(), but it generates more 
errors as you can see.

The typo3 installation ins still working. 

So - how can I prevent php from printing out this errors on the beginning at 
the website?

display_errors = Off   in  php.ini


Any Ideas?
Greetz.





Warning: preg_replace() [function.preg-replace]: Delimiter must not be 
alphanumeric or backslash in /typo3_src-3.8.1/t3lib/class.t3lib_page.php on 
line 436

Warning: preg_replace() [function.preg-replace]: Delimiter must not be 
alphanumeric or backslash in /typo3_src-3.8.1/t3lib/class.t3lib_page.php on 
line 438

Warning: preg_replace() [function.preg-replace]: Delimiter must not be 
alphanumeric or backslash in /typo3_src-3.8.1/t3lib/class.t3lib_page.php on 
line 441

Deprecated: Function ereg_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_matchcondition.php on line 527

Deprecated: Function ereg_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_matchcondition.php on line 527

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 801

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 809

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 801

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 809

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 801

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 809

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/typo3/sysext/cms/tslib/class.tslib_content.php on line 2748

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/typo3/sysext/cms/tslib/class.tslib_content.php on line 2752

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 801

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 809

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_stdgraphic.php on line 2097

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_stdgraphic.php on line 2164

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 801

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 809

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_stdgraphic.php on line 2097

Deprecated: Function ereg() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_stdgraphic.php on line 2164

Deprecated: Function spliti() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_parsehtml.php on line 227

Deprecated: Function eregi_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1583

Deprecated: Function eregi_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1585

Deprecated: Function split() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1598

Deprecated: Function ereg_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1558

Deprecated: Function eregi_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1583

Deprecated: Function eregi_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1585

Deprecated: Function split() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1598

Deprecated: Function ereg_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1558

Deprecated: Function eregi_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1583

Deprecated: Function eregi_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1585

Deprecated: Function split() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1598

Deprecated: Function split() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1598

Deprecated: Function ereg_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1558

Deprecated: Function ereg_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1558

Deprecated: Function eregi_replace() is deprecated in 
/typo3_src-3.8.1/t3lib/class.t3lib_div.php on line 1583

Deprecated: Function eregi_replace() is deprecated in 
/typo3_src-3.8.1

Re: [PHP] errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

2011-02-16 Thread Richard Quadling
On 16 February 2011 09:12,   wrote:
> Hi everyone!

Hi.

Please read the changelog http://docs.php.net/ChangeLog-5.php#5.3.0
and do a search for ereg. You'll notice that it has been deprecated.

As such, old code that relies on this feature may no longer work as
expected and/or give a warning - just like you are seeing.

Your main choices at this stage are :

1 - Upgrade Typo3 to a compatible version for the version of PHP you
are using. Looking at the latest version
(https://svn.typo3.org/TYPO3v4/Core/tags/TYPO3_4-5-0/t3lib/class.t3lib_page.php)
no longer uses ereg_*(), but preg_*().
2 - Downgrade your PHP version back to the lowest version that is
compatible with your installation of Typo3.
3 - Do a LOT of hacking and hope for the best.

Personally, I'd revert the upgrade of PHP and then create a separate
vhost or site to install/configure/test/upgrade the data from the old
version to the new one.

Also, any plugins/extensions/mods that may have been applied may also
need to be upgraded accordingly.

Regards,

Richard.

P.S. The PHP mailing lists is probably not the best place to come for
support on Typo3. I've never used Typo3 or installed it. But, in this
instance, GWMF.


-- 
Richard Quadling
Twitter : EE : Zend
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php