Solved Upgrading from 2.0.4 with automatic updates

This site is on a WAMP/MAMP/XAMPP server, yes or no?

The site I'm working on now is. The live site suffered the same problems so I'm working on the backup on a WAMP server until we can solve it.

We have a general policy in relation to Support for PC-hosted websites (e.g. WAMP, XAMPP)

Without your current Kunena configuration report it makes it difficult to assess the current situation. In general terms, the best advice I can offer is to restore your site to the state it was in before you attempted to upgrade from K 2.0.4 to K 3.0.2 using the automatic upgrade method and then attempt the upgrade using the "Install by URL" method as described in the Wiki article K 2.0 Upgrade Guide .

This may or may not work in every case - although I have not any problems myself when I have used it on several dozen occasions on several different websites.

It may be that the hosting platform (whether it is locally hosted or hosted commercially) is not properly equipped to run the upgrade process. But, without knowing a lot more about the environment, it's next-to-impossible to give you better advice that what I have already written.

We've restored and retried multiple times on both the live site and the wamp server. What information do you need?

The original question was about the problems that people have had using the "automatic update" feature of Joomla to upgrade Kunena from K 2.0.4 to K 3.0.x and we are aware that there are problems with this method. We are also aware that, after attempting to use the "automatic update" method, this subsequently may cause problems using the recommended upgrade method as described in K 3.0 Upgrade Guide .

I have looked at this topic many times and I've spent several hours trying to give information (based on intuition and educated guesswork) because, at the end of the day, everyone's website is different, everyone may be using a different version of Joomla or they have their site hosted with an unusual or unique mix of other ingredients (e.g. MySQL, PHP version, or Apache (or some other webhosting platform) and that's just the beginning.

There are three usual ways that people can upgrade a Joomla extension using the Joomla Extension Manager

1. Upload Package File
2. Install from Directory
3. Install from URL

These are not the only ways, of course, but any other method really requires advanced knowledge of how Joomla works.

The first method is reliable to the extent that some webhosting platforms often time-out and the installation fails to complete. The second method is almost guaranteed to work (but, of the three approaches, it's the most time-consuming for someone to use and it's not recommended for complete novices). The third method is the easiest (and the quickest) but, even then, if the Joomla site is already compromised in some way, that method, too, is not a sure thing.

Sometimes the Joomla "assets" table gets itself into a knot and it requires a bit of massaging to work around situations when the Extension Manager is unable to install a Joomla extension. Believe me, when I've had to dig deep into the internals of Joomla, this is not a pleasant task. It's just "one of those things" about Joomla that's not 100% reliable, unfortunately.

rodfarrell wrote:

What information do you need?

As I wrote earlier, in the absence of detailed technical information about the specific environment, my advice is largely educated guesswork. It is always difficult to start the analysis of a problem when one has little information about the problem context. It's like looking for a needle in a haystack without any real knowledge of what the haystack looks like, where (in a general sense) the haystack is located, or what is the physical composition of the needle. "Haystack" metaphors aside, it always helps if we can see the configuration report. In your case, because your site has some kind of unknown HTTP 500 Internal Server Error after you've performed the Kunena upgrade (and your whole site becomes inoperative), the configuration report of your live site running K 2.0.4 may be a good starting point.

I tried to follow your suggestions but i still have the attached error, anybody can help me?