Kunena 7.0.2 Released

The Kunena team has announce the arrival of Kunena 7.0.2 [K 7.0.2] in stable which is now available for download as a native Joomla extension for J! 5.3.x/5.4.x/6.0.x. This version addresses most of the issues that were discovered in K 6.2 / K 6.3 / K 6.4 and issues discovered during the last development stages of K 7.0

Topics that are moved into this category are generally considered to be closed. Users may want to add additional information but these topics should not be resurrected in order to discuss new problems or unrelated matters.

Question 500 internal server error

More
14 years 9 months ago #96535 by larsn84
Hi

We have experienced a problem within the last 6 hours, and cant figure out what went wrong.

Unfortunately, we did not discover the problem, until long after its accurance, so we dont know what could be the cause.

Does anyone know what a 500 internal server error is?

BTW - we can show the index, if we type the URL, but cant access entry page or any sektions.

Here is the config report:

This message contains confidential information

Database collation check: The collation of your table fields are correct

Legacy mode: Enabled | Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 3000 seconds | Max execution memory: 128M | Max file upload: 200M

This message contains confidential information

Joomla default template details : rhuk_milkyway | author: Andy Miller | version: 1.0.2 | creationdate: 11/20/06

Kunena default template details : Blue Eagle (default) | author: Kunena Team | version: 1.6.4 | creationdate: 2011-05-07

Kunena version detailled: Installed version: 1.6.4 | Build: 4832 | Version name: Kerkrade | Kunena detailled configuration:

Warning: Spoiler!

Third-party components: CommunityBuilder 1.4 | UddeIm 2.3

Third-party SEF components: None

Plugins: System - Mootools Upgrade: Enabled | System - Mootools12: Disabled

Modules: Kunena Latest 1.6.4 | Kunena Search 1.6.4

Please Log in or Create an account to join the conversation.

More
14 years 9 months ago #96537 by larsn84
seems that it was BoWoB chat that was causing the problem, though deactived... is there away to have both functioning at the same time? can you tell that from the given information?

Please Log in or Create an account to join the conversation.

More
14 years 9 months ago - 14 years 9 months ago #96538 by sozzled

larsn84 wrote: Does anyone know what a 500 internal server error is?

In general terms, HTTP 500 Internal Server errors are bad things and they are not always easy to diagnose. When you use Joomla, an HTTP 500 error usually means that you are using a Joomla extension that does not meet Joomla's coding standards or an extension that is trying to leverage data in a way that the developer of that extension anticipated.

When it comes to Kunena, an HTTP 500 error usually means that you are using another extension (e.g. a module, plugin, template, component or language) that was not designed properly to work with Kunena. If you enable Joomla's debug mode (explained here, in K 1.6.4 HTTP 500 server error , you may get more detailed information than the rather unhelpful "Fatal Error was detected!" message.

There is also a good chance that you have an old J! 1.0 component, template, plugin, module or language on your system. Please read the important information about using legacy mode and try to eliminate outdated Joomla extensions from your system. Apart from this, I cannot see anything from your K 1.6 configuration report that indicates what, specifically, is causing this error.

In summary, enable debug mode (as I mentioned above) and let us know what you find.
Last edit: 14 years 9 months ago by sozzled.

Please Log in or Create an account to join the conversation.

More
14 years 9 months ago - 14 years 9 months ago #96577 by Elma
Replied by Elma on topic Re: 500 internal server error
Well,

I'm mindboggled...

I'm having a 500 internal server error to.

@sozzled; I didn't install modules or components. To be honest, I didn't change a thing. A few hours ago Kunena worked like a charm. And now it suddenly doesn't.

Any idea's on how to tackle this problem?

Cheerio
Elma

This message contains confidential information

Database collation check: The collation of your table fields are correct

Legacy mode: Disabled | Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Enabled |

This message contains confidential information
htaccess: Exists | PHP environment: Max execution time: 128 seconds | Max execution memory: 175M | Max file upload: 32M

This message contains confidential information

Joomla default template details : gk_coffe | author: GavickPro | version: 1.6 | creationdate: 1 March 2011

Kunena default template details : Example Template | author: Kunena Team | version: 1.6.4 | creationdate: 2011-05-07

Kunena version detailled: Installed version: 1.6.4 | Build: 4832 | Version name: Kerkrade | Kunena detailled configuration:

Warning: Spoiler!

Third-party components: None

Third-party SEF components: None

Plugins: System - Mootools Upgrade: Disabled | System - Mootools12: Disabled

Modules: Kunena Latest 1.6.4

Last edit: 14 years 9 months ago by sozzled. Reason: Reveal K 1.6 configuration report in message

Please Log in or Create an account to join the conversation.

More
14 years 9 months ago - 14 years 9 months ago #96601 by sozzled

Elma wrote: Any idea's on how to tackle this problem?

Yes. enable Joomla's debug mode (explained here, in K 1.6.4 HTTP 500 server error , you may get more detailed information than the rather unhelpful "Fatal Error was detected!" message.

Elma wrote: A few hours ago Kunena worked like a charm. And now it suddenly doesn't.

Do you mean none of Kunena works at all? The cause may be a database corruption (it happens) or it may be in response to some unexpected action on your part. For example, if you use the poll feature in Kunena and press the vote button without selecting a choice, that will give you a HTTP 500 error. It's important to know what are you did to obtain the HTTP 500 error as much as what's happening at the server end that generates the response.
Last edit: 14 years 9 months ago by sozzled.

Please Log in or Create an account to join the conversation.

Time to create page: 0.367 seconds