Question Kunena vs Rockettheme

Hi!
Problem with RT Template and KUNENA



Can you tell what is causing this conflict? It might be worthwhile to Kunena prompt support is improved in future releases?

Henning from RT support:

You have to understand the issue.
The build tile-spans feature is loading a j-script.
This j-script is stripping ALL HTML inside h1/h2/h3 tags and adds a span around the first word.
Kunena buttons are inside h2 tags. So it's stripping code.
Only solution that makes sense: Disable That feature.
In the last templates starting from Voxel we stopped using that feature.
WE are in very close contact with one of the lead developers of Kunena.
There is nothing that needs to be reported.
Just don't use that feature.

Henning from RT support:

When you turn of build font titles the styling of the first word of the module-tiltes goes away ... that is correct. You need to do that when you work with Kunena.

How ever you can enable/disable this option for single menu-items by creating template styles and assigning them to menu items. You do that in the template manager. Duplicate the master style, do you changes and assign it to menu-items. You can assign it in the assignment tabs in the template settings or in the menu-item.

This way you can disable that feature just Kunena menu-items.
— Henning

It acts as a temporary solution until new versions or other solutions.

Regards!

MarioMari wrote: Can you tell what is causing this conflict?

This issue is has been discussed several [hundred] times before on the forum in at least these three places:

• [Merged topic]The great Mootools/Javascript conflict discussion
• If you are having problems with Kunena, please read this first ; and
• Before you post your question, read this first

However many times we have tried to explain what's behind the problem, in the specific case of Rockettheme templates, this is Rockettheme's answer:

Henning from RT support:

The build tile-spans feature is loading a j-script. This j-script is stripping ALL HTML inside h1/h2/h3 tags and adds a span around the first word. Kunena buttons are inside h2 tags. So it's stripping code.

MarioMari wrote: It might be worthwhile to Kunena prompt support is improved in future releases?

"Build Title Spans" is not a Kunena feature. For people who use Rockettheme templates and want to use Kunena, this is Rockettheme's advice:

Henning from RT support:

Only solution that makes sense: Disable [the "Build Title Spans"] feature. In the last templates starting from Voxel we stopped using that feature. We are in very close contact with one of the lead developers of Kunena. There is nothing that needs to be reported. Just don't use that feature.

There's your answer.

As sozzled stated, this is easily fixed. I am certain that this has also been answered at least 10 times already on Kunena.org.

Even RocketTheme is no longer adding their "Build Title-Spans" feature to their Joomla templates.

If you cannot see the Edit button and you are using RocketTheme, then turn "Build Title-Spans" OFF.

Hi! Hi have the same problem with the same template Rochetheme

Jiminimonka wrote: If you cannot see the Edit button and you are using RocketTheme, then turn "Build Title-Spans" OFF.

Than just switch "Build Title-Spans" to off. You can find that option in the backend, templates, edit your rockettheme template.

What, specifically, is the "same problem" you appear to be having with the "same" (???) Rockettheme template? If people have the same problem then they should read the whole topic and use the same solutions that others have recommended.

This discussion titled "Rockettheme vs Kunena" was about why there seems to be conflict between Rockettheme templates and Kunena. One of the significant sources of that conflict was acknowledged, by Rockettheme template people in MarioMari's message earlier. I think we all understand what is the source of the problem and how to resolve it. I believe this topic can now be closed.

For people wanting advice on what to do in their particular circumstances, please read msg #1 of Before you post your question, read this first . The answer lies there. Thank you.