Forums / Setup & design / Right menu / node list flexibility

Right menu / node list flexibility

Author Message

laurent le cadet

Thursday 07 April 2005 2:30:14 am

Hi,

I'm trying to build a node list section dependent.

I read this thread ( http://www.ez.no/content/view/full/54577 ) but I don't really understand how to perform that.

In admin you can choose a node list in the right menu toolbar and choose which node to fetch but I can't imagine to go on using this functionnality if the node list is section dependent...

The thread is talking about a switch.
Should we use this method in the node_list.tpl (and how) or hard coded the pagelayout ?

In fact I would like very much to show contextual additional info with the same flexibility than on ez.no right hand menu.

Any help will be appraciate.

Laurent.

Bård Farstad

Wednesday 20 April 2005 1:06:44 am

Hi Laurent,

if you want to have the right hand content context oriented like here on ez.no then you should alter your content model. Here on ez.no we use a class called information page which has the following attributes:
* Title
* Body
* Right info

The right info is simply an XML text field which is displayed to the right, if enabled. We have a checkbox in the class to enable/disable this feature.

This is a simple and flexible solution to this.

--bård

Documentation: http://ez.no/doc

laurent le cadet

Wednesday 20 April 2005 2:33:13 am

Hi Bård,

I nearly did the same by adding a XML field call infos to the standard article.
I tryed to place this...

{section show=$node.object.data_map.infos.content.is_empty|not}
<div class="infos">
{attribute_view_gui attribute=$node.object.data_map.infos}
</div>
{/section}

directly under

{tool_bar name=right view=full}

in the pagelayout. Everything is ok BUT I have to clear the cahe each time I want to see the content ;)

Should I try to make it your way (checkbox or something else) or do you have another syntaxe for the cache problem ?

Laurent.

Bård Farstad

Wednesday 20 April 2005 2:45:22 am

Laurent,

regarding cache: we have this right information in the view (article/folder) template directly. Then the cache is handled like normal objects.

If you place this in the pagelayout then you should cache it with cache-block. But remember to make the node ID part of the cache key. Cache blocks are purged on publishing by default.

--bård

Documentation: http://ez.no/doc

laurent le cadet

Wednesday 20 April 2005 3:32:44 am

you mean :

{cache-block}
{section show=$node.object.data_map.infos.content.is_empty|not}
<div class="infos">
{attribute_view_gui attribute=$node.object.data_map.infos}
</div>
{/section}
{/cache-block}

Could you help me for the node ID and cache key ?

I read that I haven't to specify any Key because it's comon for all case, but it doesn't seems to work that way...

Bård Farstad

Wednesday 20 April 2005 4:03:56 am

Laurent,

You can supply keys as parameters to the cache block. E.g:

{cache-block keys=$node_id} 
... 
{/cache-block}

This is only needed if you have the code placed in pagelayout. If you are using a view template, then caching is already handled by eZ publish.

Information about the cache blocks can also be found here:
http://www.ez.no/ez_publish/documentation/development/kernel/cache_block_optimization

--bård

Documentation: http://ez.no/doc

laurent le cadet

Wednesday 20 April 2005 6:25:20 am

Hi again,

This is ok but persistent. If I print a new article with content in it's "infos" xml field, there still the previous content on right hand :(

Laurent

eZ debug

Timing: Jan 31 2025 04:22:43
Script start
Timing: Jan 31 2025 04:22:43
Module start 'content'
Timing: Jan 31 2025 04:22:43
Module end 'content'
Timing: Jan 31 2025 04:22:43
Script end

Main resources:

Total runtime0.1628 sec
Peak memory usage2,048.0000 KB
Database Queries141

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0048 587.9531180.8281
Module start 'content' 0.00480.0055 768.7813102.0078
Module end 'content' 0.01020.1524 870.7891530.5781
Script end 0.1627  1,401.3672 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00301.8253200.0001
Check MTime0.00120.7638200.0001
Mysql Total
Database connection0.00070.453310.0007
Mysqli_queries0.123776.00221410.0009
Looping result0.00110.65191390.0000
Template Total0.152193.510.1521
Template load0.00080.490210.0008
Template processing0.151392.962110.1513
Override
Cache load0.00060.341610.0006
Sytem overhead
Fetch class attribute can translate value0.00050.335610.0005
XML
Image XML parsing0.00020.126610.0002
General
dbfile0.00503.0434200.0002
String conversion0.00000.002530.0000
Note: percentages do not add up to 100% because some accumulators overlap

CSS/JS files loaded with "ezjscPacker" during request:

CacheTypePacklevelSourceFiles
CSS0extension/community/design/community/stylesheets/ext/jquery.autocomplete.css
extension/community_design/design/suncana/stylesheets/scrollbars.css
extension/community_design/design/suncana/stylesheets/tabs.css
extension/community_design/design/suncana/stylesheets/roadmap.css
extension/community_design/design/suncana/stylesheets/content.css
extension/community_design/design/suncana/stylesheets/star-rating.css
extension/community_design/design/suncana/stylesheets/syntax_and_custom_tags.css
extension/community_design/design/suncana/stylesheets/buttons.css
extension/community_design/design/suncana/stylesheets/tweetbox.css
extension/community_design/design/suncana/stylesheets/jquery.fancybox-1.3.4.css
extension/bcsmoothgallery/design/standard/stylesheets/magnific-popup.css
extension/sevenx/design/simple/stylesheets/star_rating.css
extension/sevenx/design/simple/stylesheets/libs/fontawesome/css/all.min.css
extension/sevenx/design/simple/stylesheets/main.v02.css
extension/sevenx/design/simple/stylesheets/main.v02.res.css
JS0extension/ezjscore/design/standard/lib/yui/3.17.2/build/yui/yui-min.js
extension/ezjscore/design/standard/javascript/jquery-3.7.0.min.js
extension/community_design/design/suncana/javascript/jquery.ui.core.min.js
extension/community_design/design/suncana/javascript/jquery.ui.widget.min.js
extension/community_design/design/suncana/javascript/jquery.easing.1.3.js
extension/community_design/design/suncana/javascript/jquery.ui.tabs.js
extension/community_design/design/suncana/javascript/jquery.hoverIntent.min.js
extension/community_design/design/suncana/javascript/jquery.popmenu.js
extension/community_design/design/suncana/javascript/jScrollPane.js
extension/community_design/design/suncana/javascript/jquery.mousewheel.js
extension/community_design/design/suncana/javascript/jquery.cycle.all.js
extension/sevenx/design/simple/javascript/jquery.scrollTo.js
extension/community_design/design/suncana/javascript/jquery.cookie.js
extension/community_design/design/suncana/javascript/ezstarrating_jquery.js
extension/community_design/design/suncana/javascript/jquery.initboxes.js
extension/community_design/design/suncana/javascript/app.js
extension/community_design/design/suncana/javascript/twitterwidget.js
extension/community_design/design/suncana/javascript/community.js
extension/community_design/design/suncana/javascript/roadmap.js
extension/community_design/design/suncana/javascript/ez.js
extension/community_design/design/suncana/javascript/ezshareevents.js
extension/sevenx/design/simple/javascript/main.js

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1pagelayout.tpl<No override>extension/sevenx/design/simple/templates/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