mythus wrote: I was having trouble with Kunena Login Module - it kept complaining of outdated or whatever info in the fields. Sad. I really liked that log-in module and I hope ya'll get around to releasing one for kunena 4.
The
Kunena Login module is unrelated to the preview problem. For what it's worth, the
Kunena Login module has not been properly maintained for several years; some people love it and some people hate it. That's just the way it is. If it works that's good; if it doesn't work then
c'est la vie.
mythus wrote: I decided to uninstall any kunena thing that was version 3, refreshed cache, did global check in, cleared caches in joomla and firefox... still preview is broken. Yet it works here?
The message preview problem has very little to do with site caching, browser caching, Kunena templates (e.g.
Crypsis vs
Blue Eagle as
suggested by one of the developers earlier
), versions of Joomla (this website currently uses J! 2.5.28) or whether it is a full moon outside tonight.
The cause of the problem is simple: Javascript. The message preview feature requires
AJAX
. Once people get their head around this requirement then it's fairly easy to explain what has to be done next.
The Kunena message preview works on some websites and it does not work on other websites. That's a fact (and, by the way, I have never had a problem with the message preview feature on any of my websites where I use
Kunena).
There are usually two causes why the message preview feature does not work:
1) The webhost does not support JSON; or
2) You have another extension that interferes with the Javascript function, required by
Kunena, to generate the message preview feature.
How do you approach this problem? It all depends, really, on how important it is for you to resolve the problem. For some people it is "absolutely essential" to resolve this problem—as you say, some people aren't savvy with BBcode—ut the unmistakable truth is this issue has been with
Kunena for as long as I can remember it (certainly from around the time of K 2.0). The reality is that people want the problem "solved" and they're not prepared to invest their time (or money) into the solution.
I have good news and bad news. The good news is that this problem can be fixed; I mean this problem—that affects everyone in different ways—can be fixed in different ways for different people. The bad news is that it costs a little bit to fix the problem. It takes time to identify the cause of the problem: is it a hosting issue or is it a conflict with another extension used on your website? If you have the time (and you do not want outside help) then, at least, you have identified one of those costs ... time!
It would take me forever to explain
everything that people can do to resolve the problem. I do not have "forever"; for me time means money and I do not have an inexhaustible reserve of either.
There is professional assistance available to help with these kinds of problems (if people want them solved quickly). If people do not want to pay for external help then they will have to accept that their problems will not be solved quickly. Even with professional help, it can still take hours to work through the problem. There you have it: good news and bad news.