posted by elsewhere on Sun 13th May 2007 03:04
Conversations Not sure if it's just me, but in many of the current threads, I keep running into an error when viewing:

Fatal error: Maximum execution time of 30 seconds exceeded in /home/osnews/www4/includes/functions_fixtext.inc.php on line 60

I'll select the comments on a story, there will be a delay, and then a portion of the comments will print with that message at the bottom. Looks like it's server side so I assume it's not a problem with my browser, but then in this ajax/web2.0 world, who knows?

Using the legacy OSNews site shows no problems?

edit: WTF is with the full justification on this post???
Previous ConversationNext Conversation
Comments:
It's not just you
by RandomGuy on Sun 13th May 2007 08:37 UTC
RandomGuy
Member since:
2006-07-30

I am getting the same problems and only under v4.
I started to notice it with the "KDE 4.0-alpha1 Release" story but it seems to affect other articles with a high number of comments, too.

Reply Score: 1

When?
by Adam S on Sun 13th May 2007 16:50 UTC
Adam S
Member since:
2005-04-01

When did these errors start? I made a change on Friday to accommodate some behaviors that may have caused this.

Reply Score: 1

RE: When?
by RandomGuy on Mon 14th May 2007 15:45 in reply to "When?"
RandomGuy Member since:
2006-07-30

Hmm, could have been Friday, I'm not sure.
This bug is definitely not older than a week.
(At least I have never noticed it before)

Reply Score: 1

RE[2]: When?
by Adam S on Mon 14th May 2007 16:30 in reply to "RE: When?"
Adam S Member since:
2005-04-01

I've changed the way that things work in the comment display. I think the error is probably fixed.

Reply Score: 1

RE[3]: When?
by RandomGuy on Mon 14th May 2007 17:00 in reply to "RE[2]: When?"
RandomGuy Member since:
2006-07-30

Yep, everything works fine now.

Reply Score: 1

BTW
by Adam S on Sun 13th May 2007 16:53 UTC
Adam S
Member since:
2005-04-01

BTW - every post on OSNews EVER has been set to justify. I've changed it for v4 to test things out. But this has been the behavior since inception.

Reply Score: 1