Kunena 6.2.5 & module Kunena Latest 6.0.7 released

The Kunena team has announce the arrival of Kunena 6.2.5 [K 6.2.5] which is now available for download as a native Joomla extension for J! 4.3.x/4.4.x/5.0.x. This version addresses most of the issues that were discovered in K 6.1 / K 6.2 and issues discovered during the last development stages of K 6.2

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.

If you are having problems then, for your own benefit, it would save us all a lot of time if you would kindly post your configuration report when you ask for help from this forum. If you do not post your configuration report we will not ask you for it but you will probably not get your problem solved, either.

Solved 500 after moving migrated site

More
10 years 9 months ago - 10 years 9 months ago #1 by Frank A
Hi

I migrated my site and added Kunena on a test site. Test subdomain and live site are on the same VPS. Kunena fully operational.

After relocating to live, Kunena gives an 500 error in the frontend.

When I log in to backend and go to Kunena component, I get a

JFolder::create: Could not create directory

error at the top of every option.

I have not found any other problems with the Joomla site after the move. (I did have permission problems when using Akkeba to handle the move from test to live - so did a manual move.)

This message contains confidential information

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

Joomla! SEF: Disabled | Joomla! SEF rewrite: Disabled | FTP layer: Disabled |

This message contains confidential information
htaccess: Missing | PHP environment: Max execution time: 60 seconds | Max execution memory: 128M | Max file upload: 10M

Kunena menu details:

Warning: Spoiler!

Joomla default template details : beez5 | author: Angie Radtke | version: 2.5.0 | creationdate: Unknown

Kunena default template details : Blue Eagle 2.0 | author: Kunena Team | version: 3.0.0 | creationdate: 2013-05-15

Kunena version detailed: Kunena 3.0.0 | 2013-05-15 [ Wanga ]
| Kunena detailed configuration:

Warning: Spoiler!
| Kunena integration settings:
Warning: Spoiler!
| Joomla! detailed language files installed:
Warning: Spoiler!

Third-party components: None

Third-party SEF components: None

Plugins: None

Modules: None

Last edit: 10 years 9 months ago by Frank A.

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

More
10 years 9 months ago #2 by xillibit
Hello,

you can check that to see the error behind the error 500 : www.kunena.org/docs/HTTP_500_Internal_Server_Error

I don't provide support by PM, because this can be useful for someone else.

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

More
10 years 9 months ago #3 by Frank A
Thank you for replying.

No result from that as 500 error comes up before any debug op.
However, trying to turn on joomla debug, gave a cannot write configuration... so with the Could not create a directory error mentioned above - and I just discovered akeeba cannot write, so not just Kunena issue. It looks like somehow the config for this domain is not correct. Odd as all the other 7 sites on the same vps are ok and one other runs kunena, plus as I said this install worked in a test subdomain.

Server issues are not my best knowledge area. But at least got some data to work with now.

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

More
10 years 9 months ago #4 by Frank A
OK, ran php info on 2 sites and found the problem straight away... Server api was Apache 2 handler and needed to be Fast CGI.

I thought I had checked that plesk gotcha... obviously not :blush:

Which has solved the back end issue, but not the 500 in front end... thinks clear browser cache and joomla cache... no change :unsure:

joomla debug now shows infinite loop... saw that mentioned somewhere

Joomla! Debug Console
Errors

JFolder::create: Infinite loop detected
Call stack
# Function Location
1 JSite->dispatch() JROOT/index.php:42
2 JComponentHelper::renderComponent() JROOT/includes/application.php:197
3 JComponentHelper::executeComponent() JROOT/libraries/joomla/application/component/helper.php:351
4 require_once() JROOT/libraries/joomla/application/component/helper.php:383
5 JController->execute() JROOT/components/com_kunena/kunena.php:76
6 KunenaControllerHome->display() JROOT/libraries/joomla/application/component/controller.php:761
7 JController->execute() JROOT/components/com_kunena/controllers/home.php:65
8 KunenaController->display() JROOT/libraries/joomla/application/component/controller.php:761
9 JLog::add() JROOT/libraries/kunena/controller.php:153
10 JLog->addLogEntry() JROOT/libraries/joomla/log/log.php:171
11 JLoggerFormattedText->addEntry() JROOT/libraries/joomla/log/log.php:382
12 JLoggerFormattedText->initFile() JROOT/libraries/joomla/log/loggers/formattedtext.php:137
13 JFolder::create() JROOT/libraries/joomla/log/loggers/formattedtext.php:237
14 JFolder::create() JROOT/libraries/joomla/filesystem/folder.php:188
15 JFolder::create() JROOT/libraries/joomla/filesystem/folder.php:188
16 JFolder::create() JROOT/libraries/joomla/filesystem/folder.php:188
17 JFolder::create() JROOT/libraries/joomla/filesystem/folder.php:188
18 JFolder::create() JROOT/libraries/joomla/filesystem/folder.php:188
19 JFolder::create() JROOT/libraries/joomla/filesystem/folder.php:188
20 JError::raiseWarning() JROOT/libraries/joomla/filesystem/folder.php:182
21 JError::raise() JROOT/libraries/joomla/error/error.php:276

Call stack
# Function Location
1 JSite->dispatch() JROOT/index.php:42
2 JError::raiseError() JROOT/includes/application.php:208
3 JError::raise() JROOT/libraries/joomla/error/error.php:251

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

More
10 years 9 months ago #5 by Frank A
SOLVED part 2

There was a missing element in the tmp path :whistle:

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

More
10 years 9 months ago #6 by xillibit
It seems that you have a permissions issue on /logs directory, but if you have solved the issue you don't need to check that.

I don't provide support by PM, because this can be useful for someone else.

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

More
10 years 9 months ago #7 by Frank A
Yes, this is a problem with crappy Plesk, when yuo add a new website to a server it defaults to Apache instead of fastCGI, pain in the @@@@ - I thought had checked the settings but must have looked at another of my domains on the server....

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

Time to create page: 0.409 seconds