コミュニティアチーブメントバーを展開する。

Submissions are now open for the 2026 Adobe Experience Maker Awards.

Mark Solution

この会話は、活動がないためロックされています。新しい投稿を作成してください。

解決済み

Social comments | comments are cached at dispatcher

Avatar

Level 1

Hi,

I am using OOTB comment component on my page. This works fine but in dispatcher comments are cached as a part of page. So when a new comment is added, this does not appear on the page(After page reload) unless the cache is cleared at dispatcher. I see in OSGi there is setting for communities flush agent but it seems not working by default. Is there any setting to invalidate cache one a new comment is added?

Thanks.

1 受け入れられたソリューション

Avatar

正解者
Level 9

jaspians000 wrote...

Hi,

I am using OOTB comment component on my page. This works fine but in dispatcher comments are cached as a part of page. So when a new comment is added, this does not appear on the page(After page reload) unless the cache is cleared at dispatcher. I see in OSGi there is setting for communities flush agent but it seems not working by default. Is there any setting to invalidate cache one a new comment is added?

Thanks.

 

See Configuring Dispatcher for Communities.

But, essentially, it simply says to contact Customer Care so you get the best information for your particular deployment and site design.

- JK

元の投稿で解決策を見る

2 返信

Avatar

正解者
Level 9

jaspians000 wrote...

Hi,

I am using OOTB comment component on my page. This works fine but in dispatcher comments are cached as a part of page. So when a new comment is added, this does not appear on the page(After page reload) unless the cache is cleared at dispatcher. I see in OSGi there is setting for communities flush agent but it seems not working by default. Is there any setting to invalidate cache one a new comment is added?

Thanks.

 

See Configuring Dispatcher for Communities.

But, essentially, it simply says to contact Customer Care so you get the best information for your particular deployment and site design.

- JK

Avatar

Level 2

Bump! Anyone have a hint or a fix for this?