Zikula Community

• daddysupa
  
  

  • Rank: Softmore
  • Registered: Dec 23, 2003
  • Last visit: May 05, 2010
  • Posts: 351

  Posted: Mar 29, 2009 - 03:32 PM

  Since News module is now fully templated, I notice once I enable caching, if I login, the News modules still present the cached page, and not the page which may include ability to Edit and/or make Comments.
  
  To enable this feature i disable Theme Caching for News module.
  
  Any others have this issue?
  
  --
  
  Caribbean News
  Online Shopping from USA, Canada, UK, France, Germany
  On Facebook

  • 
  •  
• espaan
  
  

  • Rank: Developer
  • Registered: Aug 23, 2003
  • Last visit: May 31, 2010
  • Posts: 1428

  Posted: Mar 29, 2009 - 08:19 PM

  Can you also log a ticket in cozi/news for the observation? I haven't checked caching so much up until now.
  
  --
  campertoday.nl, Module development, Dutch Zikula Community

  • 
  •  
• nestormateo
  
  

  • Rank: Team Member
  • Registered: Sep 06, 2006
  • Last visit: May 09, 2010
  • Posts: 2446

  Posted: Mar 29, 2009 - 09:09 PM

  Theme caching is bugging ATM
  pnRender cache is the one to use ONLY.
  Try with pnRender cache enabled and tell us
  
  --
  - Mateo T. -
  Mis principios... son mis fines

  • 
  •  
• daddysupa
  
  

  • Rank: Softmore
  • Registered: Dec 23, 2003
  • Last visit: May 05, 2010
  • Posts: 351

  Posted: Mar 29, 2009 - 10:08 PM

  I have now disabled Xanthia/Theme caching completely for all modules as suggested by nestormateo. Maybe that would fix my bbcode/bbsmile not hooking to any module. In the past I just hooked to EZComments, and then hooked EZComments to other modules. Is that still the suggested method?
  
  On the first topic, do the core devs know about this suggestion to disable Theme caching since it's buggy? This might also be the cause of the false authkey expired when logging in at times, that I never see on my test site, since all caching is disabled. It looks like the Theme caching does not know when to clear cache under certain circumstances such as:
  
  1. Article/content edited
  2. User logged in
  
  I'll leave it off for now, but this will be a performance hit until it's corrected.
  
  Thanks and hope to see a fix soon.
  
  supa
  
  --
  
  Caribbean News
  Online Shopping from USA, Canada, UK, France, Germany
  On Facebook

  • 
  •  
• nestormateo
  
  

  • Rank: Team Member
  • Registered: Sep 06, 2006
  • Last visit: May 09, 2010
  • Posts: 2446

  Posted: Mar 30, 2009 - 10:05 AM

  Well, the problem with Theme caching is that doesn't respect the nocache tags, and for that reason the article is being cached with no edit buttons (guest view) and other issues like the AuthKeys. But that point was solved with inserts, that are not cached.
  
  This was announced in the release of Zikula 1.0 i guess, but i agree, a big red note is needed
  
  --
  - Mateo T. -
  Mis principios... son mis fines

  • 
  •  
• daddysupa
  
  

  • Rank: Softmore
  • Registered: Dec 23, 2003
  • Last visit: May 05, 2010
  • Posts: 351

  Posted: Apr 14, 2009 - 04:35 AM

  Hi,
  
  I reviewed the Trac for the Zikula core, and did not notice any open/closed/assigned tickets for this issue, which IMHO is a major issue in regards to performance on large sites.
  
  Would you be able to find out when a fix for pnRender/Theme caching will be released?
  
  thanks,
  
  supa
  
  --
  
  Caribbean News
  Online Shopping from USA, Canada, UK, France, Germany
  On Facebook

  • 
  •  
• lordevol
  
  

  • Rank: Softmore
  • Registered: Oct 17, 2008
  • Last visit: Oct 21, 2009
  • Posts: 163

  Posted: Apr 15, 2009 - 10:47 AM

  I disabled the theme cache and now profile 1.2's "viewmembers" works!
  So if the member list page is empty or generae an error, turn off your theme cache (pnrender cache is ok)
  
  
  
  edited by: lordevol, Apr 15, 2009 - 05:49 PM

  • 
  •  
• daddysupa
  
  

  • Rank: Softmore
  • Registered: Dec 23, 2003
  • Last visit: May 05, 2010
  • Posts: 351

  Posted: Apr 16, 2009 - 05:25 AM

  This is also affecting the Web Links 2.0 module. All links once cached show the same content.
  
  This is a major issue.
  
  --
  
  Caribbean News
  Online Shopping from USA, Canada, UK, France, Germany
  On Facebook

  • 
  •  
• Simon
  
  

  • Rank: Legend
  • Registered: Dec 11, 2002
  • Last visit: Oct 21, 2009
  • Posts: 11674

  Posted: Apr 16, 2009 - 05:42 AM

  Quote

  ll links once cached show the same content.
  
  This is a major issue.
  

  
  
  I believe that's a flaw in web links (from what I remember many years ago). The theme cache is once-per URL, but certain areas of web links use POST forms to display data rather than GETs. In this instance the URL is the same, therefore there is no way for the theme cache to distinguish between different content items, and you get shown the same page.
  
  As for the other Theme caching issues, I'll simply say this:
  Theme caching is not ever going to be reliable because of the way it works. It's not suitable for even slightly dynamic modules - it's fine if you want to Theme-cache the Pages module, but using it for anything accepting user input, anything using permissions in templates, anything that changes semi-regularly is a mistake. It's a mistake because Theme caching by design bypasses any caching mechanisms present in the modules, and only module authors know how it is safe to cache their content. By caching the whole page, you lose that vital flexibility.
  
  --
  itbegins.co.uk - Zikula Consulting
  
  birtwistle.me.uk - Personal Blog
  
  
  Please read the Support Guide

  • 
  •  
• ntward
  
  

  • Rank: Registered User
  • Registered: Jan 28, 2007
  • Last visit: Apr 16, 2009
  • Posts: 43

  Posted: Apr 16, 2009 - 06:35 AM

  Hi,
  
  Perhaps I should start a new thread, but I have noticed that pages which include a pager are not cached. Is this a known issue?
  
  The call to pnRender at the end of the pager plugin turns caching off:
  

  Code

  $pnr = pnRender::getInstance('pnRender', false);

  
  Is it possible that it prevents caching for the whole page (even though that page call was under a different instance)?
  
  
  
  edited by: ntward, Apr 16, 2009 - 06:41 PM

  • 
  •  
• daddysupa
  
  

  • Rank: Softmore
  • Registered: Dec 23, 2003
  • Last visit: May 05, 2010
  • Posts: 351

  Posted: Apr 16, 2009 - 07:18 AM

  Simon

  Quote

  ll links once cached show the same content.
  
  This is a major issue.
  

  
  
  I believe that's a flaw in web links (from what I remember many years ago). The theme cache is once-per URL, but certain areas of web links use POST forms to display data rather than GETs. In this instance the URL is the same, therefore there is no way for the theme cache to distinguish between different content items, and you get shown the same page.
  
  As for the other Theme caching issues, I'll simply say this:
  Theme caching is not ever going to be reliable because of the way it works. It's not suitable for even slightly dynamic modules - it's fine if you want to Theme-cache the Pages module, but using it for anything accepting user input, anything using permissions in templates, anything that changes semi-regularly is a mistake. It's a mistake because Theme caching by design bypasses any caching mechanisms present in the modules, and only module authors know how it is safe to cache their content. By caching the whole page, you lose that vital flexibility.

  
  
  Hi Simon,
  
  Thanks for the update, however, this was not an issue in PN .764. Earlier in this post it was suggested that the Theme caching simply does not obey the nocache directive. In 764 I also used Web Link, although I agree it was not templated back then, so that might also be an issue. In any event, there are a couple theme templates that I use with dynamic nocache calls which puts me in a position where i cannot stop the caching as yet, until I move these calls to the module templates (use pnRender) instead.
  
  It is weird for a PN/ZK team to allow ZK to reach version 1.1.1 without addressing this. As stated earlier I do not even see a ticket assigned to resolving this issue. I also suggested making a sticky in the forums about this, since a lot of users issue might just revolve around this. The Wiki still talks about enabling both pnRender & Theme caching...maybe that needs revising also?
  
  Thanks again.
  
  Cheers,
  
  supa
  
  --
  
  Caribbean News
  Online Shopping from USA, Canada, UK, France, Germany
  On Facebook

  • 
  •  
• Simon
  
  

  • Rank: Legend
  • Registered: Dec 11, 2002
  • Last visit: Oct 21, 2009
  • Posts: 11674

  Posted: Apr 16, 2009 - 08:52 PM

  The behaviour of web links has changed since .76x, which is why you won't experience the problem.
  
  As for addressing it, it's a 'feature' of the way full page caching works, and it can't be fixed, because it works as intended by the Smarty developers. The idea is that it's super-aggressive caching to be used very rarely and not in all situations. In contrast, pnRender caching should be usable in all situations.
  
  --
  itbegins.co.uk - Zikula Consulting
  
  birtwistle.me.uk - Personal Blog
  
  
  Please read the Support Guide

  • 
  •  
•  
•  

Users on-line

• 0 users

This list is based on users active over the last 60 minutes.