Question [SOLVED] Suddenly problems...

LOL I turned Legacy mode off for the fun of it and it didn't go well at all...

"direct access is not allowed"

SO I'm assuming it's a module doing that... but hard to tell at this point. I would LOVE to be on mootools 1.2x period that would mean probably doing away with most of my modules.. WHICH wouldn't really kill me, I could just look at them and rewrite them.

The message "direct access is not allowed" means that you have an extension (component, module, plugin, template or language) that was written for J! 1.0.x. Running J! 1.5 in"legacy mode" may provide some relief but, if you look at the Joomla website, you will find that even the Joomla project did not guarantee that it would always work. That's the whole point!

K 1.6 has not been tested for J 1.5 running in legacy mode simply because there are no guarantees that it works in all cases.

Because Joomla 1.0.x was officially retired, and the Joomla project withdrew support for J! 1.0 "extensions" on 22 July 2009, you're in a difficult situation.

One way you can probably track down which extension is the culprit: 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. If you find any items like these, disable them (better still, uninstall them). See if that makes a difference.

Ok I have turned Legacy mode off... Running totally native at this point.

NOW to figure out the java issues...

I will say that Community Builder login module is part of the problem. On my front page I have a menu that will not work once a user logs in... when logged out it works fine.. so there are a few issues there..

Good to hear that you've sorted out your legacy mode problems.

I've noticed that your forum URL links are not redirecting properly. If you are running a third-party SEF product I would advise you to consider disabling it and look at using Joomla Search Engine Optimization (SEO) . Let's deal with that problem next.

cowboysdude wrote:

NOW to figure out the java issues...

Well, there's Java and there's Javascript (and they are two very different things). As I wrote earlier, please use [Merged topic]The great Mootools/Javascript conflict discussion . Because you have several problems occurring simultaneously, I don't think it's wise to merge this topic with something else. There are different caused for all these problems that you're currently having. Let's keep the issues separate.

sozzled wrote: Good to hear that you've sorted out your legacy mode problems.

I've noticed that your forum URL links are not redirecting properly. If you are running a third-party SEF product I would advise you to consider disabling it and look at using Joomla Search Engine Optimization (SEO) . Let's deal with that problem next.

cowboysdude wrote:

NOW to figure out the java issues...

Well, there's Java and there's Javascript (and they are two very different things). As I wrote earlier, please use [Merged topic]The great Mootools/Javascript conflict discussion . Because you have several problems occurring simultaneously, I don't think it's wise to merge this topic with something else. There are different caused for all these problems that you're currently having. Let's keep the issues separate.

OK Step two down... 3rd party SEO off. I must say so far you are batting 100%!! WOW I turned on Joomla SEO and things sped right up.

Yes there is a difference.. Sorry.. using shortcuts... it's clearly a javascript issue. I turned on an old template and have no issues. Everything on the forums works correctly. However, I have the mootools update plugin running as I'm supposed but I cannot use megamenu when that's on, it doesn't work, BUT am here to figure out javascript conflict with the forum

Recently we've conducted some actual measurements of life with and without third-party SEO products and I think you'll find the results rather amazing. See K 1.6 sh404SEF stops Thank You, RSS feeds, PDF and message previews (msg #13 and following). No-one is saying that third-party SEO products are "bad news". We're just saying that they are "bad news" for web-based discussion forums.

The last issue of yours - the "megamenu" issue. Yes, this is also a well-known case-study of a Javascript conflict. One of the prime examples of where this "megamenu" issue arises is with Joomlart templates. Let me assure you that I have no problems with Joomlart templates. One of my favourite templates is good ol' relibable JA_Purity! It's unfortunate, though, that there are many Joomlart templates circulating "in the wild" that depend on special Javascript libraries that are incompatible with Mootools 1.2.4. From the sounds of things your Teline III v2 was one of those.

Unfortunately I also have some bad new. The JA_Purity_ii template is another one. The good news is that JA_Purity_ii probably works if you don't use the megamenu option.

**off-topic ***

I don't know if anyone else is likely to read these comments of mine but I would like to make a general observation, not directed at anyone specifically and certainly not at cowboysdude (who has willingly assisted in patiently working through some tough issues). Changing your site template is actually the easiest thing in the world to do (and it should be the first thing to look at when you have problems) but it's the one thing that most users resist almost to the death. People ask as "why aren't I seeing the BBcode toolbar" and we tell them that it's a Javascript conflict. People ask "where does this conflict come from" and we tell them that it's from another Joomla extension - most likely their site template - and they can prove this if they uninistall their site template and use rhuk_milkyway ... just to test the theory. Weeks later, they've gone back to K 1.5, they're moire frustrated than ever that we haven't "fixed" their problem and they finally decide to give our suggestion a try - they uninstall the template and, what do you know, that was the cause of the problem. Changing the template isn't always the solution, of course, but it's often very last thing that people try.

*** end off-topic ***

I'm pleased we've been able to tackle a surprising number of "sudden" problems. I suggest you look at the many useful suggestions in [Merged topic]The great Mootools/Javascript conflict discussion . Also look at these results for JA_Purity_ii