The Kunena team has announce the arrival of Kunena 7.0.4 [K 7.0.4] in stable which is now available for download as a native Joomla extension for J! 5.4.x/6.0.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 and issues discovered during the last development stages of K 7.0
This category contains miscellaneous, uncategorised user contributions, (templates, modules, plugins and hacks) relating to older versions of Kunena that are no longer supported.
This category may also contain a few topics relating to K 1.6 that may have been moved here possibly by mistake.
The topics in this category are for historical interest only. Owing to the structural differences between K 1.6 and K 1.7, these ideas in these topics will not work with later versions and, for that reason, the topics are locked.
Question
[Merged topic] KunenaDiscuss plugin for K 1.5.x
Unfortunately the way this plugin works is it listens for the afterContentDisplay trigger, this trigger occurs after the article, after the page breaks, and after the article navigation. The only way I can think of that you might get this to work is if you could create a custom trigger that sets off through the compilation of the article or for those using the page break plugin instead of tabs, it might work if you can get a custom trigger to set off in the no more pages block. In either case you would have to edit the Discuss Plugin to use your custom trigger instead of the one it usually uses.
I don't see a common solution that can be included with the discuss bot that would work for everyone though ...
Unfortunately the way this plugin works is it listens for the afterContentDisplay trigger, this trigger occurs after the article, after the page breaks, and after the article navigation. The only way I can think of that you might get this to work is if you could create a custom trigger that sets off through the compilation of the article or for those using the page break plugin instead of tabs, it might work if you can get a custom trigger to set off in the no more pages block. In either case you would have to edit the Discuss Plugin to use your custom trigger instead of the one it usually uses.
I don't see a common solution that can be included with the discuss bot that would work for everyone though ...
~cXc~
thanks for the reply.
That is understandable. Usually I only have seen something that closes right after the syntax for instance {mosmap..} or either {tab}{/tabs}.
Anyway is there any hint where should I start looking for customizing trigger instead of {mos_fb_discuss}?
ps: For text editing like "Quick Post" or "This thread discusses the content article", should I look into language/component/plugin folders?
I added a trigger that fires in the header of articles by editing com_content/views/default/article.php but there is no way to add a trigger inside the article by editing that file.
As for changing the {mos_fb_discuss} trigger goes I wouldn't recommend it because you would need to make the change everytime you have to upgrade and I have no idea what all changing it would require myself.
*ROOT*\administrator\language\en-GB\en-GB.plg_content_kunenadiscuss.ini is the language file to edit for English, adjust accordingly for other languages.
Hi, I lost connection beetwen article page and forum when moving article from one category to other. For example , I create new article , with discuss plugin - I create new forum topic directly from article side. Next, put some posts on forum and everything works fine. I see from article page those posts and I can move from article directly to forum topic connected with article. But after editing article and changing "Publishing --> Category" I lost all direct connection form article to forum. Link - "Discuss this item on the forums. (0 posts)" - shows me 0 post , and create new forum topic after clicking on it.
