Solved Internal server error attempting to upgrade from K 2.0.3 -> K 3.0.5 on J! 2.5.9

Hi there,

I am trying to install pkg_kunena_v3.0.5_2014-03-09 .

The component is being loaded, then thinking for several seconds, and then I get 500 message of Internal Server Error.

Further more, after that, I get the same message whenever, I get to the J administrator.

I am using :

Joomla! Version Joomla! 2.5.9 Stable with PHP Version 5.3.28.

Can someone please advise?

Thanks!!

please enable kunena debug

backend- kunena -confguration -kunena debug

Then go to frontend, login as admin. Then go to kunena. you will see the error:

Please paste here the error

Hi,

Thank you for your reply.

The 500 page is shown during installation. Is your answer applicable to this situation?

Tnx

tamirzzz wrote: I am using ... Joomla! 2.5.9 Stable

While it is theoretically possible to install K 3.0.5 on J! 2.5.9, if you want my personal opinion, I would not use J! 2.5.9. Instead, I would update to J! 2.5.19 as the very minimum. To be honest with you, I do not build new websites these days with using J! 2.5; J! 3.2 is much more reliable but I understand that you may have special needs that can only be fulfilled using older Joomla extensions.

I think that you are telling us that you have not installed Kunena. If that is so, you will probably not be able to modify the Kunena configuration settings and, therefore, 810's suggestion to "enable Kunena debug mode" does not have any meaning.

I would suggest, instead, that you enable Joomla debug mode, attempt to install Kunena again, and tell us if there are any extra clues to help understand what it is that is causing the HTTP 500 Internal Server Error .

Hi there,

Let me clarify the issue:

I have an active site built on j.2.5.9 with Kunena 2.x installed.

I am in the process of migrating the entire site to J 3.2. Based on my experience, all 3rd party extensions should be of the same version in the source version (in this case j.2.5.9) to the dest version (in this case j3.2).

Since the only Kunena version that I can use on J.3.2 is Kunena 3.0, I had to first migrate my j2.5.9 site to Kunena 3.0 (from Kunena 2.0) and by doing this the error that sparked this discussion occured.

Any thoughts?

Thanks!!

tamirzzz wrote: Let me clarify the issue:

I have an active site built on J! 2.5.9 with Kunena 2.x installed.

Thank you for the clarification. As I recommended in my previous reply, I would strongly suggest that you immediately upgrade from J! 2.5.9 to J! 2.5.19.

It is true that you can only use K 3.0 on J! 3.2 but you can upgrade from K 2.0.x to K 3.0.5 on your old J! 2.5 site as long as your J! 2.5 site is not broken, sick, corrupted, ruined or defective in some other way. Without knowing exactly the situation that currently exists on your old J! 2.5.9 site I can only guess.

I understand what you are attempting to do. Your strategy is, overall, sound but I think that the basis from which you're trying to start is unsound. It is my guess that there is something wrong - defective, corrupted, broken or "diseased" - with your J! 2.5.9 website.

Is there something that is preventing you from upgrading from J! 2.5.9 to J! 2.5.19?

Is there something that is preventing you from enabling Joomla debug mode?