Closed (fixed)
Project:
Facebook Comments Social Plugin
Version:
7.x-1.0-beta2
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
11 Jul 2013 at 12:49 UTC
Updated:
31 Dec 2016 at 07:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
oriol masjuan commentedComment #2
gregglesComment #3
jerryimiolo commentedThank you for tackling the issue. The patch installed as expected but the block is still caching for me. If I turn off block caching in the configuration and view source on the page, the data-href in the fb-comments div is correct to the page. When I turn block caching back on and clear the caches, the data-href remains the same on every subsequent page I visit after the first.
Let me know if you need anymore information or if I can be of any help.
Comment #4
dietr_ch commentedThere are multiple issues at work here. The block indeed gets cached per role, so all pages showing comments will show the same thread. This can be fixed using
DRUPAL_CACHE_PER_PAGE. Above patch at #1 may not work because it specifies'DRUPAL_NO_CACHE'(a string instead of the constant).On the other hand does the block not verify whether the currently displayed node has comments enabled at all. Only the additional
facebook_commentsfield on a node takes this into account.I attached a new patch for the first issue (caching), caching the block per page. The second issue is in fact a separate bug for which a new issue has to be opened.
Dietrich
Comment #5
jerryimiolo commentedI can confirm that patch #4 works. Thanks Dietrich.
Comment #6
glass.dimly commentedHah. I can confirm this patch works... because I created an identical patch and then googled for this issue to upload it.
Comment #8
wmostrey commentedCommitted, thanks!