Bug #27131
closedPublishing a page does not delete cache_treelist entry
0%
Description
Publishing a page does not delete any cache_treelist entries. Here's what I traced:
tx_Workspaces_ExtDirect_ActionHandler.sendToNextStageExecute()
t3lib_TCEmain.process_cmdmap()
tx_cms_treelistCacheUpdate.processCmdmap_postProcess()
I think the problem ist, that the new workspace module uses process_cmdmap, which tx_cms_treelistCacheUpdate only hooks into for deleted pages. So the version-command is totally ignored.
Don't know, whether this is a Workspace or Core bug...
Regards, Tom
Updated by Thomas Trethan over 13 years ago
Temporarily fixed it by modifying processCmdmap_postProcess():
if ($table 'pages' && ($command 'delete' || ($command 'version' && $commandValue['action'] 'swap'))) {
Updated by Michael Klapper over 13 years ago
- Status changed from New to Needs Feedback
Hi Tom,
how can i reproduce this?
Cheers
Mick
Updated by Michael Klapper over 13 years ago
- Status changed from Needs Feedback to Accepted
I only see that issue if an page is deleted in workspace, after puplish the page tree should update the tree.
Updated by Thomas Trethan over 13 years ago
strange that it doesn't happen to you
I don't know what to tell you how to reproduce it, it simply happens with my installation
maybe any other circumstances cause this problem
I did a lot of debugging to come to the conclusion as mentioned in the description, but maybe the real reason is somewhere else?
could you tell me at which position in the source code the tree list cache should be updated on publishing a page in a workspace?
then I could check what why this particular code is not executed in my setup
Updated by Jose Antonio Guerra almost 12 years ago
This is a duplicate of #37952
Updated by Michael Stucki almost 11 years ago
- Category changed from Bugs to Workspaces
Updated by Michael Stucki almost 11 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Updated by Bart Dubelaar over 9 years ago
- Status changed from Accepted to Resolved
Applied in changeset 84982f4260d030220ced7373341a528fae0842ce.
Updated by Riccardo De Contardi about 7 years ago
- Status changed from Resolved to Closed