Author Topic: Time required to save an event excessive? (Read 4705 times)

redgar · January 27, 2010, 08:21:59 am

I was getting time outs when saving an event ( CiviCRM » CiviEvent Dashboard » Manage Events » Configure Event ). I've tried a timeout ranging from 30 seconds up to 180 seconds and still was getting the timeout. The time out does seem to happen more often if I have lots on the event description field.

The error I got most often was:

Fatal error: Maximum execution time of 120 seconds exceeded in XXX/administrator/components/com_civicrm/civicrm/packages/IDS/Monitor.php on line 412

It wasn't until I upped the timeout to 230 seconds that it would work. (I added "php_value max_execution_time 230" to the root .htaccess file).

Note that it does work, but having to wait this long is a problem for those who don't have the ability to up their timeout.

I'm running civicrm 3.0.2. The resulting page can be viewed at http://njlp.org/convention

I'm not aware of any performance problems with my server.

Donald Lobo · January 27, 2010, 08:36:59 am

can you try to setup the same event with the same description on our demo server and check the response time there

thanx

lobo

redgar · January 27, 2010, 09:21:35 am

I just tried it on the demo page and got the same error.

Fatal error: Maximum execution time of 30 seconds exceeded in /var/www/drupal-6.civicrm.org/svn/civicrm3.1/packages/IDS/Monitor.php on line 498

Since your timeout is set to 30 seconds I can't tell if it is as bad as on my system.

If you go to the convention link above you can see the text that I put on the page (the event summary is the first paragraph). The rest (up until the end of the speaker bios) was in the complete description field. I don't think the amount of text is excessive.

Donald Lobo · January 27, 2010, 10:24:26 am

we use PHPIDS for html validation (http://php-ids.org/). You might want to follow this issue on their forums with regard to the timeout issue. Not a whole lot we can do about it currently

lobo

redgar · January 27, 2010, 11:39:51 am

One possibility would be to give administrators the ability to turn off html validation? I'd assume for some that the time is so excessive that it is unusable.

Has anyone else had this problem? Does anyone else have lots of html text (comparable to the link above) and does not have this problem?

I could solve it for me by removing all the detail on the speakers and instead including links.

Donald Lobo · January 27, 2010, 12:14:04 pm

yes, would be great to expose to the admins what fields we validate / ignore. A patch to do so would be appreciated, ping us on IRC if you need help getting started.

not heard about this from any other folks. the description for that event is a bit long, IMO

lobo

lseibert · January 29, 2010, 02:01:17 pm

I am having the same issue. I upgraded to 3.1 thinking it would fix it but it did not. I have tons of events to add for a client. Please help.

Fatal error: Maximum execution time of 30 seconds exceeded in ..../..../administrator/components/com_civicrm/civicrm/packages/IDS/Monitor.php on line 496

redgar · January 30, 2010, 08:49:32 am

Either have your admin up the timeout value for php or if you can't do this you can create a text file in the root of your joomla installation named ".htaccess" and put the line:

php_value max_execution_time 60

in that file. Note you may already have a .htacces file. If so edit it, look to see the text php_value max_execution_time already exists, if so edit it, if not add the line to the file.

You can play with the max time. I had to set mine to 230 in order to get it to work. You also have to be patient when saving the page.

jeff porter · June 07, 2010, 08:55:05 am

For one event we created, we had to raise this to over 600 seconds. Its an old thread, but it appears that the PHP-IDS guys are pointing the finger back here:
http://forum.php-ids.org/comments.php?DiscussionID=174

Any ideas so we can get this issue resolved? It crops up all of the time.

Thanks

Jeff

Hershel · June 07, 2010, 09:56:45 am

As lobo mentioned, a patch to CiviCRM's core files would be required for this.

I could suggest a workaround, however, that I used for one site, albeit for other reasons. It would require a bit of technical knowledge, but it works.

I put an iframe in an event page description. I actually did it in the Footer Text of the Registration page, but it should work anywhere. I did it because that particular page required dynamic information, so the iframe loaded the latest data for display, but this "hack" would also work in your case, if you understand how to setup the rest...

HTH

Donald Lobo · June 07, 2010, 03:30:16 pm

in 3.2, we've made an exception for the 'description' field

You can make this change by:

1. editing CRM/Core/IDS.php

2. deleting: files/civicrm/en_US/ConfigAndLog/Config.IDS.ini (this will regenerate)

lobo

CiviCRM Community Forums (archive)

News:

Author Topic: Time required to save an event excessive? (Read 4705 times)

redgar

Time required to save an event excessive?

Donald Lobo

Re: Time required to save an event excessive?

redgar

Re: Time required to save an event excessive?

Donald Lobo

Re: Time required to save an event excessive?

redgar

Re: Time required to save an event excessive?

Donald Lobo

Re: Time required to save an event excessive?

lseibert

Re: Time required to save an event excessive?

redgar

Re: Time required to save an event excessive?

jeff porter

Re: Time required to save an event excessive?

Hershel

Re: Time required to save an event excessive?

Donald Lobo

Re: Time required to save an event excessive?