How does "Search" work in the admin interface?

Author Message

Chuck Knight

Monday 12 January 2004 3:20:14 pm

Scenario
eZp 3.3 - Use Admin interface - Setup section, Template list (screen divided in two halves).

Problems:
* Every page after the first (there are 37 pages of templates) displays the same half page of "Common templates" shown in the first page PLUS a different half page of "Other". That is quite strange, because it makes paging through all the other templates at least twice as hard... Is that the intended behavior (a corner cut to save having to deal with the special case of the first page versus all the others) or do I have a bug in my install?

* I Search for a template by "template_name.tpl", leaving the front-end qualifiers out, because I don't know where that template is. The search doesn't find it, but I find it by inspection (after 33 pages of paging down :( ). Again, is there anything broken, or will the search ONLY find a fully qualified name (that is, with directory path in front)?

Thanks for any help
Cheers
ck

James Packham

Tuesday 13 January 2004 5:04:23 am

Hi again Chuck,

>> or do I have a bug in my install?

Nope this is pretty much how it's supposed to look :) I know it's bloody annoying, but for some reason this is the way it's done.

>> or will the search ONLY find a fully qualified name (that is, with directory path in front)

I don't think the file names are a searchable field I'm afraid, so it won't be found. Again pretty annoying, but this is the way it is.

Suggestion:

If you can't find the template you need on the first page or 2 just use an editor, such as Kate or vi (or notepad if using Windows) to copy and paste code from one file to another and edit etc. Editors also have several advantages over the web based admin interface anyway.

~James~

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 07:38:05
Script start
Timing: Jan 31 2025 07:38:05
Module start 'layout'
Timing: Jan 31 2025 07:38:05
Module start 'content'
Timing: Jan 31 2025 07:38:05
Module end 'content'
Timing: Jan 31 2025 07:38:05
Script end

Main resources:

Total runtime0.0219 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0114 588.2656151.2266
Module start 'layout' 0.01140.0026 739.492236.6797
Module start 'content' 0.01390.0063 776.171990.1875
Module end 'content' 0.02030.0016 866.359429.9922
Script end 0.0219  896.3516 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002913.3860140.0002
Check MTime0.00115.0240140.0001
Mysql Total
Database connection0.00094.073410.0009
Mysqli_queries0.005424.790430.0018
Looping result0.00000.064210.0000
Template Total0.00125.310.0012
Template load0.00093.997210.0009
Template processing0.00031.309610.0003
Override
Cache load0.00062.732210.0006
General
dbfile0.00115.062180.0001
String conversion0.00000.035940.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs