Since unified searches are done against an index for performance and scalability instead of against the whole content of the database as before, every new or changed content needs to be indexed. When someone imports a bunch of tracker items through the csv import feature, Tiki knows better than to index all at once, and it indexes 10 items and queues the rest for later indexing (10 at a time). There were 592 items in the queue!
When we edit a page and save it afterwards, there is a bug: Tiki forgets to be clever and presumably tries to index the new page content as well as the whole queue on unindexed data. So, it times out with the following message:
Fatal error: Maximum execution time of 90 seconds exceeded in /data/root_www/promusa.alsawiki.com/20140801_www.promusa.org/vendor/bombayworks/zendframework1/library/Zend/Search/Lucene/Search/QueryLexer.php on line 348
Raising Maximum execution time is no solution: it only blows after more time.
The page is actually saved
Going to the admin → Search → Index maintenance → reindex All
empties the queue and aftewards editing wiki pages is possible again.
To help developers solve the bug, we kindly request that you demonstrate your bug on a show2.tiki.org instance. To start, simply select a version and click on "Create show2.tiki.org instance". Once the instance is ready (in a minute or two), as indicated in the status window below, you can then access that instance, login (the initial admin username/password is "admin") and configure the Tiki to demonstrate your bug. Priority will be given to bugs that have been demonstrated on show2.tiki.org.
filename | created | hits | comment | version | filetype | ||
---|---|---|---|---|---|---|---|
No attachments for this item |