Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Fiddling with the glossary module I discovered that nodes with many terms time out (don't have many of those). I did some downgrading and it seems that 1.7 is the last version that didn't make "heavy" pages time out. Also, I don't have php multibyte and there are quite many foreign characters in the terms. The error is:
Fatal error: Maximum execution time of 30 seconds exceeded in /drupal/includes/unicode.inc on line 453
Comments
Comment #1
nancydruWell, you can go into your php settings (settings.php, php.ini, or .htaccess) and increase the maximum execution time.
IIRC, 1.7 didn't have any of the non-English support, so I can see that a node with a lot of "foreign" terms might have a problem. But that is also partly due to what Drupal has to do when you don't have multi-byte code support. That would be the first thing I would do: request that your host enable the multi-byte features.
Also make sure your cache_filter is working.
Comment #2
nancydruAlso, I don't think this is a bug - it's more like a support request.
Comment #3
nancydruWhen you've tried these things, reopen this issue.
Comment #4
jvlagsma commented@martig: It's worth trying if the recent performance improvement helps this problem.
Also, can you give an idea on how 'heavy' your pages are. For an examle node with the named problem, how many bytes is your node, how many comments, how many terms in the vocabulary that glossary uses and how many hits does that produce on your page?
Comment #5
nancydruhttp://drupal.org/node/236924 I'm trying to get this committed today and I suspect it will help considerably.
Comment #6
martig commentedOk, now I have the mbstring extension installed and there are no problems with speed, but there is another problem. I'll open a new issue for it.
Comment #7
nancydru