Welcome, Guest. Please Login or Register.
November 28, 2024, 05:36:56 PM
Home Help Search Log in Register
News: SMF is the next generation in forum software, almost completely re-written from the ground up, make sure you don't fall for cheap imitations that suffer from feature bloat!

YaBB SE Community  |  English User Help  |  English Help  |  Fatal error: Maximum execution time of 30 seconds exceeded « previous next »
Pages: [1] Reply Ignore Print
Author Topic: Fatal error: Maximum execution time of 30 seconds exceeded  (Read 1468 times)
r199
Noobie
*
Posts: 9


I love YaBB SE!

Fatal error: Maximum execution time of 30 seconds exceeded
« on: October 10, 2003, 07:54:23 PM »
Reply with quote

YaBB SE Version: 1.5.4
PHP Version:
MySQL Version:
Server Platform: Unix, Linux, or BSD
Link to Forum:

Problem Description:

Has anyone seen this before?

Fatal error: Maximum execution time of 30 seconds exceeded in /yabbse/Sources/Subs.php on line 949

Any idea how to fix it or increase the time from 30 seconds? A user gets this when they try to read their new messages.
Logged
[Unknown]
Global Moderator
YaBB God
*****
Posts: 7830


ICQ - 179721867unknownbrackets@hotmail.com WWW
Re:Fatal error: Maximum execution time of 30 seconds exceeded
« Reply #1 on: October 11, 2003, 02:40:27 PM »
Reply with quote

You'll have to talk to your host to increase the execution time.  That's a PHP thing.

Hmm... they probably have never cleared out their old messages :P.  Luckily this was.. errm, improved in SMF - so it won't happen there... umm...

You could try deleting (manually, using phpMyAdmin..) some of their older, no longer wanted, messages.

-[Unknown]
Logged
Pages: [1] Reply Ignore Print 
YaBB SE Community  |  English User Help  |  English Help  |  Fatal error: Maximum execution time of 30 seconds exceeded « previous - next »
 


Powered by MySQL Powered by PHP YaBB SE Community | Powered by YaBB SE
© 2001-2003, YaBB SE Dev Team. All Rights Reserved.
SMF 2.1.4 © 2023, Simple Machines
Valid XHTML 1.0! Valid CSS

Page created in 0.046 seconds with 20 queries.