Question Problem with post menu--report to moderator covers up quote button

Hi,

Sorry about your issue.

I am not sure what you are expecting at this point in time. A fix from the template maker was provided. You dismissed it as not an option.

Your assessment that this has something todo with the report to moderator function is unfortunately incorrect.

It just so happens that both Kunena and RT have used the same css class name in our templates. You run them both on the same page, the RT class name wins and taks away all the formatting of that button.

Kate has provided a perfectly workable solution. In addition we all have learned from this as to be extra cautious what css class names to use. Unfortunately there will never be a guarantee that if we pick 'kquote' or 'knquote' for future releases, that not somebody else in some other template or component or module, does not pick that very same name for the same problem. There are no component specific name spaces available that can prevent that.

It is this css of ours:

that gets overridden by the site template. Unfortunately, Joomla first loads component and then the site css. If it was the other way around, you would not see this issue, as on those pages driven by Kunena, the correct css would be in place.

For Kunena 1.6 the templates are pretty much frozen, in order to not break all the third party templates that have already been published or are on their way. If we where to change that css class name - all 3rd party templates out there would have a broken quote button - and possibly other broken button too. Backward compatibility for a major code version is important.

I hope this puts some extra perspective to this topic.

Thanks fxstein for the input. I now fully understand the issue--an unfortunate collision in naming conventions. This is something I had to deal with many times when I was an ArcGIS/M$SQL DB admin.

I think that we all realize that this is not a "fix" but a compromise--one that is a tradeoff between removing this niggling little issue--or stripping core typographic functionality from a site that uses current RT templates. It is not an option for me--as it affects articles and any third party publication component that generates a J! content article as its foundation. Unfortunate.

So, if I decide to keep Kunena my members will just have to deal with figuring out for themselves what the button is supposed to accomplish until 2.0 and a new set of templates emerge! :lol:

... or you simple rename the RT class to something like 'jquote' and use that in your articles. I understand it is not perfect, but a possible solution.

That would work if I were the sole author of the articles--just as adding a third party plugin (remember these "mambots" from the good old J! 1.0.x days?) to commit quote typography through a code reference in the editor would work.

Eventually, this site and 5 similar ones located in other cities scattered across the southeastern US will have between 20-30 contributing authors and columnists for each of them. They need nothing more complicated that the JCE Editor that is provided them. And of course the functionality extends into !Joomla Magazine & MyBlog--which are also integral to the site.

P

Ok - I understand.

Just trying to present options.

I would love to simply rename that class on our side, but that would break dozens of templates out there, installed on 10s of thousands of web pages.

We will do that for 1.7 - maybe you would be willing to join in as an early tester. Would be a great way to provide your feedback and get your issues taken care of before the next major stable version goes out.

fxstein wrote: We will do that for 1.7 - maybe you would be willing to join in as an early tester. Would be a great way to provide your feedback and get your issues taken care of before the next major stable version goes out.

I would be honored! These days I always have a dev site running to try out new configurations. And I have been beta testing software since 1985--most of the time paying for the privilege...

Currently using the 1.6.1 dev build Matias linked me too. I will PM you on the only strangeness I have found to date.

P