New Features

Previous topic

eZ Find

Next topic

Author	Message
Peter Putzer	Friday 16 January 2009 1:01:24 am Hi! How soon can we expect eZFind to include support for configuring meta field searching? I.e. currently the "owner" field is searched, but I don't want that because it leads to a lot of false positives for some keywords and hasn't got any semantics on the frontend of our website. Furthermore, what about configuring the XHTML tag used for snipplet mark-up? Currently, "b" is used, which is not semantically meaningful ("strong" should be used instead). This is easy to patch in the PHP file, but a configuration via ezfind.ini would be much better. Are you interested in a patch for these things? I don't want to duplicate development already in progress, but if you aren't going there at the moment, I could produce the code. Accessible website starting from eZ publish 3.0 (currently: 4.1.0): http://pluspunkt.at
Nicolas Pastorino	Friday 20 February 2009 1:34:13 am Hello Peter, Would you mind filing a bug report for these 2 interesting points ? ( http://issues.ez.no/ > eZ Find ) Thanks in advance ! -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye

Author

Message

Peter Putzer

Friday 16 January 2009 1:01:24 am

Hi!

How soon can we expect eZFind to include support for configuring meta field searching? I.e. currently the "owner" field is searched, but I don't want that because it leads to a lot of false positives for some keywords and hasn't got any semantics on the frontend of our website.

Furthermore, what about configuring the XHTML tag used for snipplet mark-up? Currently, "b" is used, which is not semantically meaningful ("strong" should be used instead). This is easy to patch in the PHP file, but a configuration via ezfind.ini would be much better.

Are you interested in a patch for these things? I don't want to duplicate development already in progress, but if you aren't going there at the moment, I could produce the code.

Accessible website starting from eZ publish 3.0 (currently: 4.1.0): http://pluspunkt.at

Nicolas Pastorino

Friday 20 February 2009 1:34:13 am

Hello Peter,

Would you mind filing a bug report for these 2 interesting points ?
( http://issues.ez.no/ > eZ Find )

Thanks in advance !

--
Nicolas Pastorino
Director Community - eZ
Member of the Community Project Board

eZ Publish Community on twitter: http://twitter.com/ezcommunity

t : http://twitter.com/jeanvoye
G+ : http://plus.tl/jeanvoye

eZ debug

Timing:	Jan 18 2025 04:52:55
Script start
Timing:	Jan 18 2025 04:52:55
Module start 'layout'
Timing:	Jan 18 2025 04:52:55
Module start 'content'
Timing:	Jan 18 2025 04:52:55
Module end 'content'
Timing:	Jan 18 2025 04:52:55
Script end

Main resources:

Total runtime	0.0192 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0076	589.3438	152.6094
Module start 'layout'	0.0076	0.0028	741.9531	39.4141
Module start 'content'	0.0104	0.0053	781.3672	90.3672
Module end 'content'	0.0156	0.0032	871.7344	30.3047
Script end	0.0189		902.0391

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	17.1121	14	0.0002
Check MTime	0.0018	9.2270	14	0.0001
Mysql Total
Database connection	0.0012	6.0195	1	0.0012
Mysqli_queries	0.0033	17.3609	3	0.0011
Looping result	0.0000	0.0833	1	0.0000
Template Total	0.0028	14.7	1	0.0028
Template load	0.0017	8.7532	1	0.0017
Template processing	0.0011	5.9312	1	0.0011
Override
Cache load	0.0012	6.4586	1	0.0012
General
dbfile	0.0002	1.0211	8	0.0000
String conversion	0.0000	0.0572	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.0003 secs