honda-kazuo
commented
3 years ago Occurrence procedure ①Install AEM6.5 ②SP6 installation (auhtor, publish) ③Install core component 2.13.2 ④Enable the publish flush agent ⑤cf-test-1.0.0.zip installation (author, publish) cf-test-1.0.0.zip ⑥Quick publish the CF below /content/dam we-retail/en/faqs/shipping-and-returns/shipping-methods ⑦Refer to the publish flash agent and check the flush status. There is no flush for pages using the core CF component. Flushing of pages using the following components is occurring.
- page-cf-core-extension(use:wcm/extension/components/ contentfragment/v1/contentfragment)
-
page-cf-foundation(use:dam/cfm/components/contentfragment)
The following page has not been flushed.
- page-cf-core(use:core/wcm/components/contentfragment/v1/contentfragment)
Yogiraj24
Feature Request
Is your feature request related to a problem? Please describe. When publishing a content fragment, there is no dispatcher flush for pages that reference the content fragment.
AEM 6.5.6 core component 2.13.2 content fragment component : core/wcm/components/contentfragment/v1/contentfragment
Describe the solution you'd like When the content fragment is published, the dispatcher flush of the page that references the content fragment is done. Like when using the following components.
Are there alternatives? The following content fragment components are used to depatcher flush the referenced page.
background＊ The user manages a large number of content fragments. There are many pages that reference content fragments. Users primarily edit and publish content fragments. Users rarely edit pages that reference content fragments. The page cache TTL is set long to improve cache efficiency.
Publishing a content fragment flushes the cache of pages that reference the content fragment, allowing users to skip the page publishing operation.