Hi
When testing the pnRender & xanthia cache, i found a glitch i think.
pngetstatusmsg and nocache means the Smarty commands.
The point is when you enable pnrender caching. Thats on a 900 second cache.
The Smarty command pngetstatusmsg is for example in the News module template.
The bug can happen in this way:
- some pngetstatusmsg was generated elsewhere on my page from me but not shown
on that page (because that template don't had a pngetstatusmsg cmd or it redirects to homepage).
- the News module (or some other module) is showing the messages
- because the module is triggered first time is it cached
- because pngetstatusmsg is not marked as nocache our messages stay now 900 seconds
Conclusion: the pngetstatusmsg Smarty tag should ALWAYS enclosed by nocache or even better
trigger it by default.
I think this can be also a problem with authkey command from Smarty?
I am not 200& sure about this problem, so i don't have added it to the buglist ATM.
edited by: michtoen, Jan 14, 2008 - 06:37 PM
Watch
GitHub Core
Show your support for Zikula! Sign up at Github account and watch the Core project!
GitHub Modules
Forum Activity
- michiel responded to »password problem« 10:01 AM
- mazdev responded to »Hide "Register new account" and change template to 3 col« 07:50 AM
- mesteele101 created topic »Zikula 1.3.3 - Site Search 1.5.2 - Unable to turn off plug-ins« 07:48 AM
- mesteele101 responded to »ERR (3): E_USER_ERROR: Smarty error: [in pagesvar:pagesitem2en line XXX]…« 25. May
- mazdev responded to »Pages 2.5.0 and updating - Page not found« 25. May
- mesteele101 responded to »Zikula 1.3.3 - Selecting a category in Pages not working« 25. May
- mdee created topic »How to implement returnpage ?« 25. May
Zikula Blog
- Anatomy of Open Source Projects on Mar 07
- Continuous Review on Mar 01
- Not Invented Here on Feb 24
- How to Contribute Your Code at Github on Jan 13
- 10 Steps to Coding-Nirvana: Tips for Successful Module Writing on Nov 12
- Submitting Bug Report Tickets That Get Results on Aug 17
- Cozi Tricks #1: Syntax Highlighting on Aug 07
Login
pnrender, pngetstatusmsg and nocache problems
-
**unknown user**
- Rank: Freshman
- Registered: Mar 16, 2002
- Last visit: Jul 26, 2008
- Posts: 61
Posted: Jan 14, 2008 - 06:36 AM
-
**unknown user**
- Rank: Freshman
- Registered: Mar 16, 2002
- Last visit: Jul 26, 2008
- Posts: 61
Posted: Jan 14, 2008 - 06:39 AM
Another point to the cache:
I was setting the pnrender cache to 15 seconds and the xanthia cache for
the Wiki and the main page to 3 seconds.
That works pretty good when someone is hammering the site.
Using small cache times for caching on default seems me more
senseful as the big numbers, because they avoid when a bug like
above happens that this bug "stays" so a long time.
-
- Rank: Expert
- Registered: Nov 23, 2003
- Last visit: Dec 13, 2009
- Posts: 1487
Posted: Jan 15, 2008 - 12:46 AM
It's my belief that all modules authors should have pngetstatusmsg in their module templates... after all, they should be setting the messages and therefore deciding how the messages are displayed.
--
Under Construction! -
**unknown user**
- Rank: Freshman
- Registered: Mar 16, 2002
- Last visit: Jul 26, 2008
- Posts: 61
Posted: Jan 15, 2008 - 01:38 AM
Hm, that was not my point - the point is that in the current way a user can
run in a screen showing the wrong because cached status message, which is
not what the system should do. -
- Rank: Team Member
- Registered: Sep 06, 2006
- Last visit: May 09, 2010
- Posts: 2446
Posted: Jan 15, 2008 - 06:13 AM
Yep, Status messages, AuthKeys and more stuff can't to be cached...
That bug with Theme caching must be resolved
--
- Mateo T. -
Mis principios... son mis fines
- Moderated by:
- Support
