How to setup Frames?

«

Previous topic

|

|

Next topic

»

Author	Message
andreas spahr	Tuesday 09 September 2003 2:30:19 am I need to create a frameset with a navigation, head and contentframe. I know, it is not recommended by eZ to use frames, and I avoid it too, but, as its going, I have to. But I have no idea how to. Can someone help me? Thanks!
Bjørn Kaarstein	Tuesday 09 September 2003 4:15:06 am I think you will have to create sections for navigation, head and content frame, and give all sections a pagelayout.tpl to control the layout of each frame. I've been thinking about making a site with frames, but it haven't come to that yet. (Haven't been forced) I'd be grateful if you'd post how you solve it if you decide to go for frames. Regards Bjørn
Paul Forsyth	Tuesday 09 September 2003 4:35:20 am We recently built a set that required the use of an iframe. Essentially the iframe (or frame) loads in its own space so you need to careful to ensure each frame has the right url for the task. There are a couple of tricky bits. Communicating between each frame so that ez knows what is going on is pretty much impossible without using some kind of cookie/javascript combination. At least thats the approach we took for our problem. The other thing to consider is ez will eat a lot of resources displaying your pages, one httpd resource for each frame you create: ez can only return one page at a time. Paul
Lazaro Ferreira	Thursday 22 January 2004 11:19:54 am Hi, Have you managed to develop your site with frames, sucessfully ? Lazaro F. Lazaro http://www.mzbusiness.com
Felix Laate	Thursday 22 January 2004 12:34:58 pm One solution is to make one subdomain, say www.yourdomain.com, for the frameset. And one, say publish.yourdomain.com, for ezpublish. Then you point the frames to the objects you need in ezpublish. When I need a menu in e.g. a top-frame, I simply make a fakeobject with no content, make a special "gives-me-the-menu"-template for that node. Felix Publlic Relations Manager Greater Stavanger www.greaterstavanger.com

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 18 2025 22:37:02
Script start
Timing:	Jan 18 2025 22:37:02
Module start 'layout'
Timing:	Jan 18 2025 22:37:02
Module start 'content'
Timing:	Jan 18 2025 22:37:02
Module end 'content'
Timing:	Jan 18 2025 22:37:02
Script end

Main resources:

Total runtime	0.0144 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.0047	589.0391	152.6250
Module start 'layout'	0.0047	0.0027	741.6641	39.4297
Module start 'content'	0.0074	0.0049	781.0938	93.2891
Module end 'content'	0.0123	0.0021	874.3828	34.3047
Script end	0.0143		908.6875

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0024	17.0062	14	0.0002
Check MTime	0.0011	7.4297	14	0.0001
Mysql Total
Database connection	0.0006	4.3287	1	0.0006
Mysqli_queries	0.0022	15.6507	3	0.0007
Looping result	0.0000	0.1128	1	0.0000
Template Total	0.0017	11.5	1	0.0017
Template load	0.0009	6.2351	1	0.0009
Template processing	0.0008	5.2462	1	0.0008
Override
Cache load	0.0006	4.4316	1	0.0006
General
dbfile	0.0002	1.6774	8	0.0000
String conversion	0.0000	0.0564	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