search with different layout and caching

Next topic

Author	Message
Heiner Wurbs	Friday 17 December 2004 3:42:39 am Hi all, I have a problem with search and caching. My main pagelayout.tpl requires a complete caching for a performant access. But now I have a problem with the search. The keys I can assign to the cache-blocks are not usefull for the search, because the uri of the search doesnt change, it is always "content/search": This doesnt work for search, but for any other content in pagelayout.tpl: {cache-block keys=array($uri_string)} {/cache-block} As a solution I created a new layout and a new pagelayout for the search, search_pagelayout.tpl without any cache blocks. This works fine, the search itself caches not anymore, except the google-navigator :( This is my new search template: /layout/set/searchlayout/content/search?SearchText=about+ez The google-navigator url for the next searchresult page is: /layout/set/searchlayout/content/search/(offset)/10?SearchText=about+ez But it shows always the same page, the first. By the way, if you solve one problem, there is always the next coming up; as a result of the changing of the layout, every link created with {$node.url_alias} is now switched to the searchlayout, which I didnt wanted. My (bad) solution is to eliminate the url_alias and use easy "/{$node.url_alias}". But this is obviously not recommended. Now the question: does anyone have some ideas? Heiner
Heiner Wurbs	Friday 17 December 2004 5:34:28 am Hi, I found a better solution which works fine: I removed the search layout, I'm using again ezurl and I using this specific Cache-Block keys: {cache-block keys=array($uri_string,$search_text,$view_parameters.offset)}

Author

Message

Friday 17 December 2004 3:42:39 am

Hi all,

I have a problem with search and caching. My main pagelayout.tpl requires a complete caching for a performant access. But now I have a problem with the search. The keys I can assign to the cache-blocks are not usefull for the search, because the uri of the search doesnt change, it is always "content/search":

This doesnt work for search, but for any other content in pagelayout.tpl:

{cache-block keys=array($uri_string)}
{/cache-block}

As a solution I created a new layout and a new pagelayout for the search, search_pagelayout.tpl without any cache blocks. This works fine, the search itself caches not anymore, except the google-navigator :(

This is my new search template:
/layout/set/searchlayout/content/search?SearchText=about+ez

The google-navigator url for the next searchresult page is:
/layout/set/searchlayout/content/search/(offset)/10?SearchText=about+ez

But it shows always the same page, the first.

By the way, if you solve one problem, there is always the next coming up; as a result of the changing of the layout, every link created with {$node.url_alias} is now switched to the searchlayout, which I didnt wanted. My (bad) solution is to eliminate the url_alias and use easy "/{$node.url_alias}". But this is obviously not recommended.

Now the question: does anyone have some ideas?

Heiner

Heiner Wurbs

Friday 17 December 2004 5:34:28 am

Hi,
I found a better solution which works fine:

I removed the search layout, I'm using again ezurl and I using this specific Cache-Block keys:

{cache-block keys=array($uri_string,$search_text,$view_parameters.offset)}

eZ debug

Timing:	Jan 19 2025 11:02:41
Script start
Timing:	Jan 19 2025 11:02:41
Module start 'layout'
Timing:	Jan 19 2025 11:02:41
Module start 'content'
Timing:	Jan 19 2025 11:02:42
Module end 'content'
Timing:	Jan 19 2025 11:02:42
Script end

Main resources:

Total runtime	0.8663 sec
Peak memory usage	4,096.0000 KB
Database Queries	52

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0051	589.2891	152.6406
Module start 'layout'	0.0052	0.0034	741.9297	39.4766
Module start 'content'	0.0086	0.8560	781.4063	429.4531
Module end 'content'	0.8646	0.0016	1,210.8594	8.1250
Script end	0.8662		1,218.9844

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.3492	16	0.0002
Check MTime	0.0012	0.1390	16	0.0001
Mysql Total
Database connection	0.0006	0.0740	1	0.0006
Mysqli_queries	0.8188	94.5160	52	0.0157
Looping result	0.0005	0.0537	50	0.0000
Template Total	0.8301	95.8	2	0.4150
Template load	0.0024	0.2746	2	0.0012
Template processing	0.8277	95.5400	2	0.4138
Template load and register function	0.0005	0.0600	1	0.0005
states
state_id_array	0.0009	0.1072	1	0.0009
state_identifier_array	0.0022	0.2507	2	0.0011
Override
Cache load	0.0020	0.2251	21	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0710	1	0.0006
Fetch class attribute name	0.0014	0.1618	2	0.0007
XML
Image XML parsing	0.0001	0.0122	1	0.0001
class_abstraction
Instantiating content class attribute	0.0000	0.0008	2	0.0000
General
dbfile	0.0016	0.1792	10	0.0002
String conversion	0.0000	0.0009	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
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 14 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs