Question Call to undefined method JController::getInstance() in \...\components\com_users\users..php

You can download the full J! 1.5.22 from joomlacode.org/gf/project/joomla/frs/?ac...iew&release_id=13105

Now things gettin' a bit strange for me.
The .22 as well as the .23 version does NOT contain a com_users folder, but a com_user (without 's').
So, where does com_users come from?

Good question. I don't know the answer. I was just rephrasing what xillibit wrote. :S

You won't believe this:

I googled around a bit. The com_users folder (instead of com_user) is used in J! 1.6, but I have a 1.5 installation. I took over this website some month ago, and meanwhile I think, the former webmaster tried a 1.6 upgrade, was not successful and put it back to 1.5. Furthermore I found the joomla.xml in the main directory, which is part of a 1.6 not a 1.5 installation.

I deleted the com_users folder and the joomla.xml, I uninstalled and re-installed Kunena. Now I get a 404 error on user related actions. Yes, normal. If I hover over the links for user actions (register, forgot p/w etc.), I can see that they are linked to i.e. /component/users/?view=registration.
Not to i.e. /component/user/register like in the login module.

Finally, to me it looks like, that the Kunena installation 'thinks' it should install in a 1.6 envirionment and therefore installs the wrong links.
Remains the question: How does the Kuenena installation gets the J! version for the right installation?

Any thoughts?

Olli

PS: Local time 03.20AM

Ah, the dreaded "abortive-attempt-to-upgrade-Joomla-made-a-mess-of-my-website" syndrome. Yes, I've seen this happen quite a few times.

It's possible to unravel the mess and to put things right again, but it usually takes a couple of hours of work and it's not something that novice users should entertain lightly. This is, indeed, one of the big drawbacks of rushing into a Joomla 1.6 migration without having tested the water first. In fact, this is one of the main reasons why most of the people that I know have held off migrating to J! 1.6 until the dust has settled and the various problems that were identified in the early stages of J! 1.6 have been worked through ... and there's still work to be done in that area.

All very well and good for me to write something like "we told you so" but that doesn't really help, does it? Without pointing the finger at something/someone else and hiding behind the comfort of saying "this is not a Kunena problem", in effect this does not seem to be a Kunena problem. Although that may be a comforting thought to those people who are not in your situation, this doesn't really help you.

The problem can be resolved. I think it's probably something that requires a bit of work and it's probably something that you may want to give consideration to employing a specialist to work through the issues with you. There is, of course, the option of reverting to a backup of your website before all of these issues began to appear and to to things over again.

The question that you asked, "how does Kunena get the J! version for the right installation" is not really something that I think we need to concern ourselves with. The K 1.6.4 installer makes the appropriate allowances for what version of Joomla is installed and adjusts things to those environments. We've proven that the K! 1.6.4 installer operates quite successfully on a reliable J! 1.5.x installation as well as on a reliable J! 1.6.3 installation. However, if your J! 1.5.x installation was compromised by a botched attempt to migrate to J! 1.6.x ... well, that's a different issue. Your J! 1.5.x site is no longer reliable in that situation, is it?

Fortunately my site works fine is reliable.
I will have to talk with the former webmaster.
Thx for ur great support!