Site malfunction started several days ago. When attempting to open a comment form or archived post, one gets a series of error messages, most of which run:
Deprecated: Function ereg() is deprecated in /home/stylograph/domains/cronaca.com/public_html/blogport/php/mt.php
And then the line number.
Also a warning as follows:
Cannot modify header information - headers already sent by (output started at /home/stylograph/domains/cronaca.com/public_html/blogport/php/mt.php:203)
I've looked to see what old code I have that might have been deprecated, but haven't had any luck so far. Can anyone advise?
Many thanks
David
Reported on Movable Type 4.3
Hi David,
You should upgrade your movable type installation, or at least update a few source files and replace the deprecated functions with their correspondent.
This problem occurs when your server upgrades php for you to a newer version like say v5.3.
Upgrading your installation to v4.37 would fix the issue.
I am available for upgrading your installation if you need another pair of hands.
Kind Regards,
Mihai Bocsaru
----------------------------------
Daily Movable Type Consultant
Web Development
Movable Type Consulting
Six Apart Partner
http://www.pro-it-service.com/
----------------------------------
Movable Type Demo
http://www.movabletypedemo.org/
----------------------------------
Open Melody Demo
http://www.openmelodydemo.org/
Thanks for the response.
I had figured that a php upgrade set this all in motion. Unfortunately, I'm having a very hard time finding any specific information on deprecated functions in MT. Guess I'll have to dig into the default installation code on this.
By the way, the installation had already been upgraded to 4.37
Whoops -- found the problem. Upgrade had appeared to be successful, but a whole bunch of php folder files hadn't gotten uploaded.
I know for sure that upgrading properly would fix that problem.
Mihai is correct that upgrading to Movable Type 4.37 or the most recent releases of MT 5.0x or 5.1x will solve the problem.
This issue was actually resolved in Movable Type 4.35. See the Movable Type 5.04 and 4.35 Release Notes and the detailed analysis in FogBugz Case 103926 if you are interested in knowing more.