Trying to access several nodes (book pages that have been on the site almost since inception some years ago), I got a PHP timeout in the search module on line 1221. Checked the database and everything seemed fine. The site is 99% indexed with somewhere in the region of 4500 nodes.
Then tried switching off the Search module, and the nodes are displayed fine.
Switched on the Search module again and everything seems ok again.
But this is rather disconcerting. Why does Drupal go through the Search module when it is just accessing a book page for reading? And is there anything I can do to stop it happening? Will upping the 30 second PHP execution limit help?

Comments

joel_guesclin’s picture

joel_guesclin commented

I have just had to do the same thing on another article. This seems to happen only with articles that have been on the site pretty much since the beginning. Could it be that clicking on the article causes it to be loaded in cache?
Could it be anything to do with the fact that I am also using Google CSE search?
Is there no support for Search in core? I'm a bit surprised nobody has picked this up.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Status: Active » Closed (cannot reproduce)

I looked into this very old issue today... this is an old issue and the error must have been from the search_excerpt() function. This is not normally called during a node display, but only during search results. I'm assuming that there was a custom or contrib module present that was doing something on the page display. In any case, I'm hoping that this very old issue has been resolved on the sites in question and I'm just going to close it.

joel_guesclin’s picture

joel_guesclin commented

Strangely, the problem resolved itself after moving the site to another server. No idea why though.