Question [Resolved] 500 error after upgrade attempt

LOL, thanks for the tip.

I don't know if that will work or not. Sounds like you have a corrupted jos_kunena_configuration table that was caused by MySQL (could have occurred during your first attempt to upgrade) - would be nice to know the version of MySQL that you're using. It's possible to fix this. Let's hear how you go.

Could very well be my Mysql and PHP setup. Well it went ok after that so its all good. At least from what I can see. Thanks.

Here is the info if you like. I am using the IUS repos on CentOS 5.6 for PHP and MySQL.

PHP Built On Linux example.com 2.6.18-238.19.1.el5 #1 SMP Fri Jul 15 07:31:24 EDT 2011 x86_64
Database Version 5.1.58-ius
Database Collation utf8_general_ci
PHP Version 5.3.6
Web Server Apache
WebServer to PHP Interface cgi-fcgi

A day or so ago I updated our joomla from 1.6.5 to 1.7.0 :blink:

We are running kunena 1.6.4

Will upgrading to the 1.6.5 Kunena component over the top of the old incompatible component, which has carried through with the Joomla upgrade and is currently not working in the Joomla 1.7, going make Kunena work again with the integrity of the old forums data maintained and working.

If it is not 100% known if this will work, could we please be informed of any potential risks where there may be some uncertainty or success stories?

Reading through forum posts here, it appears it will be ok to proceed this way.

An answer to a similar question re j1.7 - "My suggestion is for you to uninstall Kunena from your system and then reinstall Kunena. You will not lose any forum messages or you configuration. If this does not work, please let us know."

This post suggests we should uninstall Kunena 1.6.4 from our Joomla 1.7 upgrade, which should keep the data and configuration intact, then install Kunena 1.6.5 on the new Joomla 1.7 upgrade, which should pick up and reinstate the data and configuration of the previous Kunena 1.6.4 installation, which was working on the Joomla 1.6.5.

when uninstalling the 1.6.4 version should we remove both the 'Kunena Forum' component and also 'System - Kunena Forum' in the extensions list.

thanks for any help with this
cheers
michael

G'day, Michael, and welcome to Kunena.

It's kind of a different question you're asking in your case. First of all, let's look at the subject of this topic (which relates to the great bugbear that many website owners encounter at one time or another), namely a HTTP 500 Internal Server Error. The HTTP 500 Internal Server Error has a long and well-documented pedigree that goes all the way back to when the first internet websites were built. Basically, the HTTP 500 error says "you have a really, really bad error here; I don't know what it is; I don't know why you wrote the software the way you did but I haven't a blessed clue what you've done and I'm just going to curl up my toes and die here and you go figure!" (That's a bit of a paraphrase of a more technical explanation , but it amounts to the same thing).

Fortunately, Joomla helps experienced web application developers with this generic "who-knows-what-you've-done" error by providing you with "debug mode". It doesn't always help, but that's what you've got.

Coming back to your specific issue, we have not had time to test what happens to those people who were using J! 1.6.5 and K 1.6.4, went ahead before K 1.6.5 was ready and updated their site to J! 1.7.0 and who are now in the position of wanting to install K 1.6.5.

But this isn't the situation in ryvix's case: ryvix is using J! 1.5.23.

So now we're in the situation here of possibly dealing with two, unrelated circumstances.

To help us understand more about this issue, gypsykitchen, can you tell us if you are having HTTP 500 errors now?

I feel that ryvix's case is a one-off (I could be wrong; I have been wrong before many times). We do not recommend uninistalling Kunena when there is no reason to do that but, by the same token, there is no major consequence done if you do uninstall Kunena and then reinistall it after that.

Generally-speaking (and this is an almighty big generalisation) HTTP 500 errors are caused by Kunena in extremely rare circumstances.

gypsykitchen wrote: If it is not 100% known if this will work, could we please be informed of any potential risks where there may be some uncertainty or success stories?

That's a very good question. I can only tell you that, in the past 6 hours when K 1.6.5 was built, it has been tested on a few websites and there were no show-stopping issues found. It is used here on this website. I've installed it myself. It would be good to hear of a few other success stories in addition to the ones I have alluded to. If we were not comfortable with this release - given the pressure that we've been under in recent days - we would not have released it.

Thanks sozzled
we will delete k 1.6.4 with extention manager and install k 1.6.5 and report the results here.

but ... after acting so rashly in updating to j1.7 ... i am being encoraged to take all precautions...
so with extention manager> manage> i take out both kunena files?

gypsykitchen wrote: when uninstalling the 1.6.4 version should we remove both the 'Kunena Forum' component and also 'System - Kunena Forum' in the extensions list.

again much thanks