For anyone attempting to build php 4.3.10 (seeing as it fixes some security bugs). You might have problems with php-4.3.10/Zend/zend_strtod.c (at least, I did on my 10.2 system).
Line 131 seems to be the problem. Removing the "|| defined(__ppc__)" so that that define doesn't happen on my Mac OS X machine seemed to fix it.
I had this identical problem. Editing that line solved it.
Thank you very much. It might have been days -- certainly *many* more hours -- before I solved the problem if not for your post on the topic.
... and that's _exactly_ why I posted it.
I'm glad it helped.
Hi there,
Found your blog via a google search on PHP 4.3.10 and MT 2.661, which I see you're still running, like me.
Overnight my hosting provider upgraded to PHP 4.3.10, and since then my MT comments have been broken: see http://babbage.tv/dblog/2004/december/comments. I was wondering whether the following might help me, if you're willing to reveal the deep secrets of your blog: is the 4.3.10 installation you've done on OS X on the same box you're powering this blog from (indicating that 4.3.10 may not be the problem for me, perhaps) or is this blog hosted elsewhere?
Any ideas anyone else has about my problem of course most appreciated!
MT 2.6 doesn't use PHP for comments, so it shouldn't be causing a problem.
And yes, my php 4.3.10 install is on the same machine as my MT 2.661 install.
Ah, well, at least we've eliminated that option.
It's even more strange now, as I've discovered the error appears to be restricted to our home IP address. Strange.
Thanks for your assistance!
What error?
MT has a built-in rate-limiter for comments that's based on origin IP, so if you're trying to post very frequently, you can get an error message.
Hi Daniel,
Thanks for your interest in following this up.
I eventually tracked through a series of leads to find this solution:
http://philringnalda.com/blog/2004/02/throttling_easterners.php
Turned out the problem was due to throttling being over-applied because we host two blogs on our MT installation, one in a timezone 13 hours ahead of the other... the result is that posting a comment on one of the blogs prevents you posting on the other till the timezones catch up, 13 hours later... the entry above contained the fix, which has worked well!
Again, thanks for your interest and willingness to help, and Merry Christmas!