Mr Washington,
eregi("^(https?:[\/]+[^\/]+)(.*$)", $mosConfig_live_site, $live_site_parts);
becomes
preg_match("/^(https?\:[\/]+[^\/]+)(.*$)/i", $mosConfig_live_site,
$live_site_parts);
and
( eregi( 'index.php\?', $row->link ) ) { if ( !eregi( 'Itemid=',
$row->link ) ) { $row->link .= '&Itemid='. $row->id; }}
becomes
( preg_match( '/index.php\?/i', $row->link ) ) { if ( !preg_match(
'/Itemid\=/i', $row->link ) ) { $row->link .= '&Itemid='. $row->id;
}}
Basically, preg functions use the Perl regular expressions engine
which are only slightly different from ereg, only more interesting ;-)
.
Some authorities discourage the practice of supressing errors.
I hope umesaidika buda.
--
ndungi
Hello Ndungi,
Thanks so much, only this came a little bit too late. After sitting down and reading for a bout 1 day, I discovered that the PHP people are MAD PEOPLE - I mean those guys at
php.net. If they are not mad, then
http://www.php.net/manual/en/migration53.incompatible.php tells something about them.
With php-5.3.3, they have rendered most CMSes simply unusable, until they are re-programmed. Something like Joomla-1.5.21 does not work with php-5.3.3. You have to go in and replace all those incompatible functions.
But their level of madness is understandable, and acceptable, since there is php-5.2.14, which is what I fell back to.