Question Joomla legacy mode and Kunena

One of the most interesting side-effects of people using the K 1.6 configuration report is that is reveals, perhaps for the first time, the significant ongoing use of Legacy mode for new installations of Joomla!

I have asked myself this question, many times. Why do people enable the System - Legacy plugin? Perhaps they see a big red cross on the list of plugins and think "I'd better enable this so that I see pretty green ticks". It's a bit like clicking off the safety catch on a firearm. Maybe the plugin was disabled by default for a reason? Have people considered that possibility?

I can understand why people might have, once upon a time, needed Legacy mode. It was a stop-gap measure designed to facilitate the take-up of K 1.5 by a Joomla community that had a large investment in Joomla 1.0 software. However, as we all know, Joomla 1.5 has been around for over three years and three years in software evolutionary terms is a very long time ago. The temporary, stop-gap feature that was built when J! 1.5 was in its infancy is still there today in J! 1.5.22.

As we all know, "legacy mode" was never offered with any guarantees that it would solve all the compatibility issues that might happen when people tried to run J! 1.0 software on a J! 1.5 framework. The frameworks are different! Joomla 1.5 makes Joomla 1.0 obsolete ... and that's the important lesson. But I also want to add that, from my research, "legacy mode" does not come with any guarantees that it will not adversely impact on the normal operation of J! 1.5 either!

Because it's now past the time when "legacy mode" was once needed, Kunena is not tested to operate under "legacy mode" conditions.

For those that think that future versions of Joomla will always be backward-compatible with previous versions - that you can, for example, continue to run J! 1.5 software under J! 1.6 - you will be in for a rather rude awakening. Joomla 1.6 does not provide any "legacy mode". In fact, I have not seen any details yet about an official "extension migration" solution that allows J! 1.5 users to convert their templates/components/modules/extensions/languages across to J! 1.6.

So, next week, when J! 1.6 is to be officially launched, there is probably going to be a bit of disappointment and heart-ache about having to say farewell to old J! 1.5 favourites ... or the realisation that people will have to wait a bit longer before the extensions developers catch up by offering J! 1.6-compatible software. Kunena is in a lead position at the moment. K 1.6.2 will work with J! 1.6 and future versions of K 1.6 will operate on both J! 1.5 and J! 1.6 platforms.

However, getting back to this topic: people need to now take inventory of their website software assets and bring their software up to date if they plan to stay current with technological change. There's probably no harm in running "legacy mode" - if you don't want to upgrade any software - and that's a comforting thought. BUT ... for your own sake, don't build new websites now with outdated software or with products that you will not be able to maintain yourselves.

In summary: don't use "legacy mode"

Some time ago, i need to use legacy joomla plugin, but now i unistalled old component and i don't need too. (I use joomla 1.5.22 e kunena 1.6.3 that is an updatate from all old kunena versione!!!!).
The problem is that if I disable legacy plugin kunena stops work

I read this, but does not help me docs.kunena.org/index.php/Special:Search?search=legacy

Can help me?

Ps: In /media/kunena/attachments i have a legacy folder with some images... have i delete?

This is what I wrote a while ago:

There's a very easy way to find out if you have J! 1.0 legacy software running on a J! 1.5 website. It's not 100% foolproof but it's reliable enough for our purposes:

Go to Extensions » Install / Uninstall

You will see that 6 sub-functions you can choose from:

• Install
• Components
• Modules
• Plugins
• Languages
• Templates

Click, one by one, each of the items I've bolded above. Browse the listed items and look for any items that have a red X in the compatibility column. For example, see the following image (the red X is shown against the ObjectClarity Kunena Discussbot plugin):

If you find any items like these, disable them; better still, uninstall them. I would say that you missed one or two. See if what I have suggested makes a difference.

yes i know but does not solve! I have this problem only for kunena... If i disable legacy plugin, kunena disappeared... in the forum was write that kunena work better without this plugin. In my site, from older kunena version, i work with plugin on, but if i put off, kunena stops.. Very strange.

What "older" version of Kunena are you talking about? At this time our primary interest concerns K 1.6.x.

sozzled wrote: What "older" version of Kunena are you talking about? At this time our primary interest concerns K 1.6.x.

Yes, but i don't use a fresh installation of kunena. I used an old version (1.0) that had not any problem with legacy. I try to update with legacy and kunena works. But now, simple, i would remove legacy plugin.. and i can't without broke kunena...