Disable caches

Author Message

David Santiso

Wednesday 02 March 2011 2:24:04 pm

Hi,

How can I disable some caches?

I want to users view the content added by other users instantly.

Gaetano Giunta

Thursday 03 March 2011 1:06:00 am

Your question is too generic to have a proper answer.

The cache you might want to disable is the "view cache" (look for "viewcaching" in ini files).

But that is considered very very very much a bad idea on production web sites, as it basically kills performances and scalability.

By default you should not have such problems as you describe, ie. eZP shows new content as soon as it is added. If you have introduced dependencies between unrelated content via templates, you should look into the smart view cache...

Principal Consultant International Business
Member of the Community Project Board

Damien Pobel

Thursday 03 March 2011 4:34:56 am

Hi,

In addition to what Gaetano writes, you should have a look at http://doc.ez.no/eZ-Publish/Technical-manual/4.x/Features/View-caching

Cheers

Damien
Planet eZ Publish.fr : http://www.planet-ezpublish.fr
Certification : http://auth.ez.no/certification/verify/372448
Publications about eZ Publish : http://pwet.fr/tags/keywords/weblog/ez_publish

David Santiso

Thursday 03 March 2011 10:45:14 am

Yes, I agree, but I'm building a site is that users continually add content to show to others.

I saw that if I add content, does not appear until the caches clean.

Sebastiaan van der Vliet

Monday 07 March 2011 5:09:53 am

my solution is: ... Wrong

{section show=$MinGroup:item.data_map|contains('link')}
will not work because we need to test against the keys of data_map, not the values. Back to the drawing board.

Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.

Sebastiaan van der Vliet

Monday 07 March 2011 5:17:17 am

No, that function is essentially missing. Once your object is published, you cannot unpublish it (via the user interface).
In ez2, there was such an option (but ez2 had NO versioning).

You may try these options, when you wand to hide a published article:
- Delete it (will be in trash... but probably not editable)
- Move it to some place, when the "common user" cannot see it
- Assign a section to it, that the "common user" cannot read (you need a "admin section" for this, but i found this very handy).

We are using the second option, which you can use to (re-)move complete folder structures "out of the the visitors view" quickly.

NOTE: When you move an object by changing its main location, it might get a news section id (it will get the section ID of the new parent node). But when you move a complete tree, this only applies to the main object (usually a folder), not the child node (node assignment is not recursive, when you move nodes).
This might be important, when your read permission are only based on sections.

Certified eZ publish developer with over 9 years of eZ publish experience. Available for challenging eZ publish projects as a technical consultant, project manager, trouble shooter or strategic advisor.

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

Main resources:

Total runtime0.8995 sec
Peak memory usage4,096.0000 KB
Database Queries71

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0052 588.9063152.6094
Module start 'layout' 0.00520.0067 741.515639.4141
Module start 'content' 0.01190.8850 780.9297662.4063
Module end 'content' 0.89690.0025 1,443.335916.2031
Script end 0.8994  1,459.5391 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00410.4612160.0003
Check MTime0.00140.1561160.0001
Mysql Total
Database connection0.00090.104210.0009
Mysqli_queries0.818590.9995710.0115
Looping result0.00080.0858690.0000
Template Total0.848694.320.4243
Template load0.00250.281120.0013
Template processing0.846094.054820.4230
Template load and register function0.00020.023710.0002
states
state_id_array0.00170.190910.0017
state_identifier_array0.00200.216820.0010
Override
Cache load0.00190.2168370.0001
Sytem overhead
Fetch class attribute can translate value0.00080.089640.0002
Fetch class attribute name0.00110.120590.0001
XML
Image XML parsing0.00200.219740.0005
class_abstraction
Instantiating content class attribute0.00000.0023100.0000
General
dbfile0.00770.8595290.0003
String conversion0.00000.001240.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1node/view/full.tplfull/forum_topic.tplextension/sevenx/design/simple/override/templates/full/forum_topic.tplEdit templateOverride template
6content/datatype/view/ezxmltext.tpl<No override>extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tplEdit templateOverride template
10content/datatype/view/ezxmltags/paragraph.tpl<No override>extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tplEdit templateOverride template
4content/datatype/view/ezimage.tpl<No override>extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tplEdit templateOverride template
1content/datatype/view/ezxmltags/link.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/link.tplEdit templateOverride template
4content/datatype/view/ezxmltags/line.tpl<No override>design/standard/templates/content/datatype/view/ezxmltags/line.tplEdit templateOverride template
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 27
 Number of unique templates used: 7

Time used to render debug report: 0.0002 secs