Discussion box showing up even with ~~DISCUSSION:off~~ about plugin-discussion

[pyu]

I have a similar problem but not with the Blog plugin. It happens whenever I include pages with a DISCUSSION command with the Include plugin. The page that calls the include will show the discussion section even when DISCUSSION:off is specified whenever the cache is purged (and sometimes on its own). It seems to be pulling the DISCUSSION command from the included pages. The Blog plugin makes use of Include to show the posts, so it seems to me like it's the same issue. When I used the Blog plugin in the past with Linkback, the same thing happened.

I looked into the Include source code and there is logic in there to skip DISCUSSION and LINKBACK commands when including, but the behaviour here seems to be related to caching.

Here is a really clumsy workaround that seems to work for me: Remove all DISCUSSION commands from all your pages and set Discussion to be automatically shown for all pages. Then, use DISCUSSION:off in pages that should not have the discussion. This way, there are no DISCUSSION commands for the Include plugin to pull in.

[twingate-zz]

Same problem here. Occurred after updating to DW Anteater. Stray discussion appearing on the page where {{blog}} is used. Same problemboth on IIS and Apache.

[FiSHYsolutions]

same problem here (using 2009-12-25 Lemming with blog-plugin). but i think, this problem is a new problem. IMHO i used an older version of this plugin without this bug.

[lupo49]

Could someone post markup code of the page where this issue occurs?

[FiSHYsolutions]

nope. decided yesterday to remove the discussion-function.

[lupo49]

The blog requires the include plugin, so I guess your descriptions are related to one bug.

[lupo49]

The problem is that DISCUSSION:off syntax on the blog page is is handled before the DISCUSSION:on syntax of the included page is handled. Therefore the discussion box is shown even when it disabled by the syntax.

[michitux]

I hope I've fixed this now in the include plugin and in the blogtng plugin which caused the same problem (although most probably blogtng and discussion aren't used at the same time that often, I've just had them both in my local test installation). Please try upgrading the include plugin and test if the issue has been solved.

[Klap-in]

This can be considered as fixed?