Question [Resolved] Discussion plugin in module

Hello,

I installed Kunena discussion plugin that work very nice.
Kunena discussion plugin provides the ability to "Allow Custom Topics", with that in any item you can add the {kunena_discuss:#} where the label # is ID of topic in which the article will be discussed.

My Idea: I need to add plug-in in module position, namely to add custom HTML module and easily type in {kunena_discuss:#} than he started Kunena plugin discussion as it does in every article, but it is not possible for me, module displays only the text "{kunena_discuss:#}" and does not start plugin.

So far I have tried installing the following things:
1. mod_plugin_module
2. Article As Module Module
Articles Anywhere
3. Art Plugin
4. I added the code in index.php:
With all this I had the same result: Module displays only the text "{kunena_discuss:#}" and does not start plugin

Does anyone have an idea how to solve this?

Thanks in advance
(Sorry for my bad english )

Currently the plugin only gets run when you're in com_contents component because of in Joomla 1.5 there's no way to tell if the content is coming from Joomla articles or something else.

BTW: You only need to add {kunena_discuss:#} to assign (or change) article into existing topic -- after you've displayed the article once, you can just remove the tag because of Kunena Discuss will store that information into a table.

But.. this is not a bad idea. We just need to tell KD that we really want to run it. Line 27 in the plugin prevents it from running if you're not in com_content or com_kunena..

Thank you for your response.
Of courese, we really want to run it, it's small change, but means a lot

Is it possible to change the line 27 manualy and enable running in other components or in all components and modules?
I need to display the plugin in component ZOO.

Line 27-36:

It is possible to remove that test, but be wary that there might be some side effects if you do this!

Here's what I can think of:
* Small performance decrease because of plugin does some work on every page
* Other components and modules may also trigger the event and even if there are good checks in it, there may be some unexpected side effects (hopefully not)

I tried to delete a number of ways but I failed, obviously I do not understand enough.
There will be no problem for me if there might be some side effects.
I will tested that for several days, and I'll let you know the results.
Can you help me edit kunenadiscuss.php?
You can contact me via email efektiv.b.c(at)gmail(dot)com.
It would be best to resolve here, that others see if they have the same problem.

Just remove this (not tested):

Line 27-29:

It Works!
They do not appear any error, everything works perfectly!
Thank you for your help. I hope that in the future this plugin will dont have lines 27-29.
If somebody have any question about this, post your question here.

Matias wrote: Just remove this (not tested):

Line 27-29:

Code:

// If plugin is not enabled in current scope, do not register it if (! $this->enabled ()) return null;

I made this change because I want to add 'Discussion plugin' to the ZOO platform and this change work perfectly, but, there was one problem:
Meta: keywords and description are loaded from the Kunena on the page that I made in zoo platform.
For each page in ZOO I made meta keywords and description but still ZOO show just meta data from Kunena in evry page where I have "Discussion plugin" inserted in ZOO page.
Here's how it looks with "Discussion plugin" iz ZOO page:

<meta name="keywords" content="Kunena post keywords" />
<meta name="description" content="images/stories/I-start-topic-with-picture.gif Text from post // Link from post (/link/link.html)..." />

Here's how it looks without "Discussion plugin" iz ZOO Pgae:

<meta name="keywords" content="ZOO keywords" />
<meta name="description" content="ZOO description" />

My concern are keywords and description because it look pretty bad in google.

I hope somehow this can be corrected, thanks for the help in advance. (I'm sorry for my English).

It's a bug. Thank you from reporting it.

No problem Is there any chance for correcting?