Search in eZ sucks

«

Previous topic

|

|

Next topic

»

Author	Message
Yngve Bergheim	Wednesday 12 October 2005 1:21:53 am I find myself doing eZ searches in google (site:ez.no loop), because the eZ search is horrible. Why not replace the default search with something better?
Xavier Dutoit	Wednesday 12 October 2005 2:38:23 am I do the same and don't see your problem of doing that. That's quite obvious than ez internal search engine isn't as good as google. Not a big scoop here ;) It does it not too badly for standard "content oriented websites". The dev related searches are usualy quite specific and don't work that well in the search engines on the websites (same applies to mysql.com and the al.). You can use an external search engine for ez publish. If you benchmark some of them (mngosearch, switch-e), I'd love to hear your feed-back about the one you find more pertinent. X+ http://www.sydesy.com
Yngve Bergheim	Wednesday 12 October 2005 3:30:04 am It seems like the eZ internal search engine is returning every hit on a search word, sorted by date. It doesn't get much worse then that, unless you don't have a search engine :-) I'll include Lucene http://lucene.apache.org/java/docs/ on my eZ site, but that is not the problem. I'm doing several site:ez.no-google-searches a day, but it is a hazel. Why not put a good search engine on ez.no and make it available for everyone? We can integrate MySQL fulltext search, http://dev.mysql.com/doc/mysql/en/fulltext-search.html - provides relevance sorting as well as key word highlighting.
Tomek Klaudel	Monday 17 October 2005 2:13:48 am > I'll include Lucene > http://lucene.apache.org/java/docs/ on my eZ > site, but that is not the problem. Can you describe you experiences with integration lucene and ezpublish? Do you use compassframework ( http://www.compassframework.org ) ? Greetings Tomek

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 31 2025 01:24:27
Script start
Timing:	Jan 31 2025 01:24:27
Module start 'layout'
Timing:	Jan 31 2025 01:24:27
Module start 'content'
Timing:	Jan 31 2025 01:24:27
Module end 'content'
Timing:	Jan 31 2025 01:24:27
Script end

Main resources:

Total runtime	0.0251 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0062	588.0313	151.1953
Module start 'layout'	0.0062	0.0040	739.2266	220.6563
Module start 'content'	0.0102	0.0135	959.8828	997.7734
Module end 'content'	0.0237	0.0014	1,957.6563	33.9922
Script end	0.0251		1,991.6484

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0029	11.5803	14	0.0002
Check MTime	0.0011	4.3731	14	0.0001
Mysql Total
Database connection	0.0010	3.9171	1	0.0010
Mysqli_queries	0.0023	9.3448	3	0.0008
Looping result	0.0000	0.1036	1	0.0000
Template Total	0.0009	3.8	1	0.0009
Template load	0.0007	2.7058	1	0.0007
Template processing	0.0003	1.0565	1	0.0003
Override
Cache load	0.0005	1.8602	1	0.0005
General
dbfile	0.0014	5.3945	8	0.0002
String conversion	0.0000	0.0846	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs