Go Back   vb.org Archive > vBulletin 3 Discussion > vB3 General Discussions
FAQ Community Calendar Today's Posts Search

Reply
 
Thread Tools Display Modes
  #1  
Old 05-14-2007, 11:02 PM
Dr. Bantham's Avatar
Dr. Bantham Dr. Bantham is offline
 
Join Date: Feb 2007
Posts: 164
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default Timeout with Large Content Posts

I have the need to post large documents as a post. I am having trouble with one particular document timing out when posting. This document is over 350,000 charachters in length. This is a full essay document which is being posted as an article in GARS, thereby allowing it to be presented with an extensive table of contents directory for online reading/navigation.

This is the error I received when first attempting to post this document:
Code:
Fatal error: Maximum execution time of 30 seconds exceeded in
home/xxxxxxx/public_html/includes/functions.php on line 1533
If I reduce the document size and wait patiently, everything works. If I add the following line to my .htaccess file, an earlier version of the document would sometimes upload:
Code:
php_value max_execution_time 300
Unfortunately, a recent increase in the document size pushed it past another threshold. Now it times out with a whitescreen, stating "finsihed" in the browser status bar and listing editpost.php in the address bar.

What can I do to remedy this situation? Though this size document will be a rarity, this is a very important literature release for the site and I can not give up.
Reply With Quote
  #2  
Old 05-15-2007, 05:24 AM
snakes1100 snakes1100 is offline
 
Join Date: Dec 2001
Location: Michigan
Posts: 3,733
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Well, u need to chk the apache log and see if its spitting out a error with the now bigger document, its probably doing the same thing as it was before, could also be a memory issue, chk ur logs.
Reply With Quote
  #3  
Old 05-15-2007, 09:44 AM
Dr. Bantham's Avatar
Dr. Bantham Dr. Bantham is offline
 
Join Date: Feb 2007
Posts: 164
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Quote:
Originally Posted by snakes1100 View Post
Well, u need to chk the apache log and see if its spitting out a error with the now bigger document, its probably doing the same thing as it was before, could also be a memory issue, chk ur logs.
How can I do this? I have my site on a server host and I could not find any links in cPanel to view this information. There was an Error Log, but nothing shows after a post dies.
Reply With Quote
  #4  
Old 05-15-2007, 02:46 PM
snakes1100 snakes1100 is offline
 
Join Date: Dec 2001
Location: Michigan
Posts: 3,733
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

If you dont have a dedicated server, i doubt the host will give you access as well, yo ucan try this though in the config.php at the top, after the <?php on line 2

Code:
ini_set('memory_limit', 32 * 1024 * 1024);
ini_set("max_execution_time", "600");
Reply With Quote
  #5  
Old 05-15-2007, 10:53 PM
Dr. Bantham's Avatar
Dr. Bantham Dr. Bantham is offline
 
Join Date: Feb 2007
Posts: 164
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Quote:
Originally Posted by snakes1100 View Post
If you dont have a dedicated server, i doubt the host will give you access as well, yo ucan try this though in the config.php at the top, after the <?php on line 2

Code:
ini_set('memory_limit', 32 * 1024 * 1024);
ini_set("max_execution_time", "600");
Thanks, but this does not seem to have an effect.
Reply With Quote
  #6  
Old 05-15-2007, 10:58 PM
snakes1100 snakes1100 is offline
 
Join Date: Dec 2001
Location: Michigan
Posts: 3,733
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Without log access, i doubt you will find the issue behind this.
Reply With Quote
  #7  
Old 05-15-2007, 11:10 PM
ssslippy ssslippy is offline
 
Join Date: Jan 2006
Posts: 877
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

The text is probally to long for the database. Try breaking it down to 100,000 per post.
Reply With Quote
  #8  
Old 05-15-2007, 11:46 PM
Dr. Bantham's Avatar
Dr. Bantham Dr. Bantham is offline
 
Join Date: Feb 2007
Posts: 164
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

Quote:
Originally Posted by ssslippy View Post
The text is probally to long for the database. Try breaking it down to 100,000 per post.
I suspected this, but increasing the field length to LONGTEXT does not help.

What if I created a short version of the post and tried to manually input the full version into the pagetext field using phpMyAdmin? Would the basic text including bbcode work? What would the statement syntax be? As I may not have another post of this size again, finding a technical workaround would make me happy.
Reply With Quote
  #9  
Old 05-19-2007, 06:47 PM
Dr. Bantham's Avatar
Dr. Bantham Dr. Bantham is offline
 
Join Date: Feb 2007
Posts: 164
Благодарил(а): 0 раз(а)
Поблагодарили: 0 раз(а) в 0 сообщениях
Default

I managed to work around this problem by using phpMyAdmin and pasting the content (complete with bbCode formatting) into the pagetext field for the post. It works fine, but I have to use the same method in making edits.
Reply With Quote
Reply


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 02:07 PM.


Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2024, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.04089 seconds
  • Memory Usage 2,240KB
  • Queries Executed 11 (?)
More Information
Template Usage:
  • (1)SHOWTHREAD
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (1)ad_showthread_beforeqr
  • (1)ad_showthread_firstpost
  • (1)ad_showthread_firstpost_sig
  • (1)ad_showthread_firstpost_start
  • (4)bbcode_code
  • (3)bbcode_quote
  • (1)footer
  • (1)forumjump
  • (1)forumrules
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (1)navbar
  • (3)navbar_link
  • (120)option
  • (9)post_thanks_box
  • (9)post_thanks_button
  • (1)post_thanks_javascript
  • (1)post_thanks_navbar_search
  • (9)post_thanks_postbit_info
  • (9)postbit
  • (9)postbit_onlinestatus
  • (9)postbit_wrapper
  • (1)spacer_close
  • (1)spacer_open
  • (1)tagbit_wrapper 

Phrase Groups Available:
  • global
  • inlinemod
  • postbit
  • posting
  • reputationlevel
  • showthread
Included Files:
  • ./showthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/functions_bigthree.php
  • ./includes/class_postbit.php
  • ./includes/class_bbcode.php
  • ./includes/functions_reputation.php
  • ./includes/functions_post_thanks.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • showthread_start
  • showthread_getinfo
  • forumjump
  • showthread_post_start
  • showthread_query_postids
  • showthread_query
  • bbcode_fetch_tags
  • bbcode_create
  • showthread_postbit_create
  • postbit_factory
  • postbit_display_start
  • post_thanks_function_post_thanks_off_start
  • post_thanks_function_post_thanks_off_end
  • post_thanks_function_fetch_thanks_start
  • post_thanks_function_fetch_thanks_end
  • post_thanks_function_thanked_already_start
  • post_thanks_function_thanked_already_end
  • fetch_musername
  • postbit_imicons
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • postbit_display_complete
  • post_thanks_function_can_thank_this_post_start
  • tag_fetchbit_complete
  • forumrules
  • navbits
  • navbits_complete
  • showthread_complete