Kunena 7.0.4 Released

The Kunena team has announce the arrival of Kunena 7.0.4 [K 7.0.4] in stable which is now available for download as a native Joomla extension for J! 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

The error code HTTP 500 Internal Server Error is a general-purpose message this indicates a general error in a web application. Please note that there is no general solution for this general error. You should first read HTTP 500 Internal Server Error before posting in this category.

Important Error 500 when displaying certain topics.

More
14 years 2 months ago - 14 years 2 months ago #119355 by ZeroKewl
Hi there.

I have recently updated to 1.7.2 - up until then everything was fine. Now, for certain topics in the forum, the users receive an Error 500. I know the reason is that the script has been stopped because it ran for too long (shared hosting).

Fortunately I was able to spot and fix one of the threads that caused the problem. It was a recently added topic (1 entry) that only contained little text and a youtube link. When opting the topic the error was raised. So I went into sqladmin and deleted the link from the message and - voila - the error was gone.

Then i replaced the "normal" link-url with the [ video type=youtube ] tag and the error disappeared.

Before this I dumped the entire database into my backup of the site BEFORE I upgraded to K1.7.2 and displayed the thread in its original version - and NO error.

So I hoped that the error 500 would appear for EVERY video that's posted with its video url, but unfortunately, that's not the case. I have some other threads in the forum with youtube URLs in the post where its displayed normally. !?!?!?

Therefore my assumption is: Parsing the message text - particularly video URLs - has become a lot more time consuming with the latest version of Kunena or there is an error in this part of the latest version. Maybe someone in the devteam can check if some part of the relevant code has changed and examine if it may cause timeout errors in shared environments.

Thanks for your hints and thougts.

Here's my config report:
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: Disabled |

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

This message contains confidential information

Joomla default template details : rt_omnicron_j15 | author: RocketTheme, LLC | version: 1.5.1 | creationdate: September 13, 2010

Kunena default template details : SOCIAL - Kunena 1.6 Template | author: TemplateKunena Team | version: 1.6.2 | creationdate: 2011-01-24

Kunena version detailled: Installed version: 1.7.1 | Build: 5162 | Version name: UnderUret | Kunena detailled configuration:

Warning: Spoiler!

Third-party components: Jomsocial 2.0.6

Third-party SEF components: None

Plugins: System - Mootools Upgrade: Enabled | System - Mootools12: Disabled | My Kunena Forum Menu 1.6.2 | My Kunena Forum Posts 1.6.0-RC1

Modules: Kunena Latest 1.7.1

Last edit: 14 years 2 months ago by ZeroKewl.

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

More
14 years 2 months ago - 14 years 2 months ago #119356 by ZeroKewl
OK. Studying my own configuration file I realized that I upgraded from 1.7.0 to 1.7.1 - and not to 1.7.2 as I thought (must have been 2 days befor the release to 1.7.2).

I also realized that some of the plugins and modules were prior to this date. So I updated everything to the latest and greatest. I also looked at the changelog.php in the new version and realized that some "fatal errors" have been fixed in 1.7.2

So far, the error is gone.

I should have been more thorough researching my own mess. :(

Thanks for being there! ;)

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: Disabled |

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

Kunena menu details:
Warning: Spoiler!

Joomla default template details : rt_omnicron_j15 | author: RocketTheme, LLC | version: 1.5.1 | creationdate: September 13, 2010

Kunena default template details : SOCIAL - Kunena 1.6 Template | author: TemplateKunena Team | version: 1.6.2 | creationdate: 2011-01-24

Kunena version detailled: Installed version: 1.7.2 | Build: 5215 | Version name: Omega | Kunena detailled configuration:

Warning: Spoiler!

Third-party components: Jomsocial 2.0.6

Third-party SEF components: None

Plugins: System - Mootools Upgrade: Enabled | System - Mootools12: Disabled | My Kunena Forum Menu 1.7.1 | My Kunena Forum Posts 1.7.1

Modules: Kunena Latest 1.7.2 | Kunena Stats 1.7.2

Last edit: 14 years 2 months ago by ZeroKewl.

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

More
14 years 2 months ago #119359 by sozzled
Good work and thank you for following through on your problems. I hope that this topic serves as a good example of the importance of including the configuration report when people ask questions on this forum. :)
The following user(s) said Thank You: ZeroKewl

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

More
14 years 2 months ago #119371 by ZeroKewl
:P :blush:
It's good to know that when I screw up I can serve as a good example
:silly: :laugh: :silly:

Thanks to all "creators" for your work for the entire community.

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

Time to create page: 0.263 seconds