Details
-
Improvement
-
Resolution: Unresolved
-
Medium
-
None
-
2011.10, 4.6.0beta1
-
None
Description
There are a few bugs open regarding the fact that when an object that is part of an ezflow block (manual or automatic) is edited, the corresponding frontpage is not updated.
The immediate solution would be trying to improve the ezflow cronjob to make it more sensible to changes in linked content.
But a better long term solution could be to treat the items that are displayed is blocks as related items, just like the items that are present in rich-text blocks are considered related items that use an "embedded" type of relationship.
After all, item in an ezflow block is embedded in it very much in the same way it is embedded in an rich text area.
So the proposal is:
. mark as "related" the objects that are present in an ezflow block, using either the "embedded" type or a new type of relationship
. make this relationship visible in the "relations" tab in the admin interface
. make sure this relationship plays well with view cache expiration
Attachments
Issue Links
- relates to
-
EZP-17324 Ezflow block and view cache : clear view cache when publishing current object
- Open
-
EZP-12908 eZFlow: workflow and queues: objects awaiting approval are displayed
- Closed
-
EZP-18852 Node swap does not update ezm_block table
- Closed
-
EZP-12620 Allow eZFlowOperations::update() to update a single homepage / single block
- Closed
-
EZP-14039 ezflow leaves ghost children in table ezm_block
- Closed