Deprecated: Function ereg() is deprecated in /home/xxxxx/public_html/admin/file_manager.php on line 29

[dreams]

hi

Please Help when i go into admin and then go to file manger i get this error massage at the top

 

Deprecated: Function ereg() is deprecated in /home/pussycat/public_html/admin/file_manager.php on line 29

 

what do need to change

 

Many thanks

[Guest]

@@dreams

 

You can use THIS contribution to update to correct most of the deprecated errors. However, your site should NOT HAVE a file_manager.php file. Read THIS thread on how to secure your website. Having a file manager is a HUGE security issue.

 

 

 

Chris

[dreams]

Hi

Thank you all sorted

Many Thanks

[[email protected]]

i installed this months ago... when PHP 5.3 compatibility became a problem for OSC 2.2RC2... and, up until today, i had never seen another error like this.

 

today, i get the following PHP error:

 

Deprecated: Function ereg() is deprecated in /home/hybridel/public_html/index.php on line 231

 

i check, and, sure enough, at line 231, there is an (!ereg('^[1-8][ad]$', $HTTP_GET_VARS['sort']))

 

i seem to vaguely recall that there is some other modifications i have to make to the stuff inside the parentheses in order to make them readable to the new "preg_match()", but i don't remember what they are...

 

and, apparently, the contribution above does not have instructions for what to do with *catalog*/index.php

[MrPhil]

Are you sure your host didn't do a site restore and roll you back to an earlier version? Or that you haven't been hacked? I should think that catalog/index.php would be the very first thing fixed in such a patch.

 

(!ereg('^[1-8][ad]$', $HTTP_GET_VARS['sort']))

becomes

(!preg_match('/^[1-8][ad]$/', $HTTP_GET_VARS['sort']))

[[email protected]]

no, my site didn't do a site restore (that i know of), and no, i haven't been hacked...

 

and even if my host provider did do a site restore, it would have been fixed along with all the other places where ereg() was replaced with preg_match() because, as i said, i applied the contribution months ago, on 120922...

 

however, the error only showed up once -- unlike when i was originally presented with this problem, where it showed up many, many times -- and pasting in the code you suggested fixed the error.

 

it was buried pretty deep in index.php, and there was only one of them, so my impression is that it may have been overlooked in the contribution mentioned above, or something like that, because it absolutely was not mentioned in the version of the contribution that i downloaded...

 

thanks for the fix! :)