Issue Information
-
#000015
Issue Confirmations
-
Yes (0)No (0)
0
runsnippet does not work correctly in some caching situations
Posted by
mikef
on 12 August 2009 - 06:09 PM
This problem was not marked fixed in the previous bug tracker, and there's been no response to my query in the parsechunk report, so I assume its still not fixed.
Can the steps to reproduce be copied over to here from the prior tracker please, since I can't remember the exact situation?
Can the steps to reproduce be copied over to here from the prior tracker please, since I can't remember the exact situation?
Having accidentally found the old tracker site while searching for something else:
it definitely was not marked as fixed, and so should have been carried over.
Instructions to duplicate:
If you have runSnippet used in a snippet call that is forced non-cached ( [!xxx!] ), in a page that is itself set as non-cacheable (Status cacheable: no), the snippet called by runSnippet is not executed, though the xxx snippet is.
it definitely was not marked as fixed, and so should have been carried over.
Instructions to duplicate:
If you have runSnippet used in a snippet call that is forced non-cached ( [!xxx!] ), in a page that is itself set as non-cacheable (Status cacheable: no), the snippet called by runSnippet is not executed, though the xxx snippet is.
Updating status to: Fixed
Issue fixed in: 1.2
This issue will be resolved in the v1.2 release... Current development code does not display this problem due to changes in the parsing logic...
Issue fixed in: 1.2
This issue will be resolved in the v1.2 release... Current development code does not display this problem due to changes in the parsing logic...
0 user(s) are reading this issue
0 members, 0 guests, 0 anonymous users
