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

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 Error in Forum Configuration and forum

More
14 years 10 months ago #98827 by Bob Britt
Replied by Bob Britt on topic Re: 500 Error in Forum Configuration and forum
to recap the issue.

1. if Kunena logon module is uses it generates the 500 error. Simply go back to CC logon module and that problem is resolved.

2. If anything other than "None" is set in the "Login and Registration" it generates the 500 error.

3. 500 error is generated when trying to access the Forum Configuration page on the Kunena page of the Admin. all forum config has to be edited directly on the SQL table, i'm comfortable working in SQL but as you can imagine, it's not the desired approach here.

I suspect this is some sort of authentication issue between CB and Kunena.

Related thread at CB support.

www.joomlapolis.com/forum/154-advanced-m...na-forum-integration

Here's my current config.
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: 30 seconds | Max execution memory: 64M | Max file upload: 64M

This message contains confidential information

Joomla default template details : tntsmalllogo | author: Rob Mooar | version: 1.1 | creationdate: 2009-10-25

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.1

Third-party SEF components: None

Plugins: System - Mootools Upgrade: Enabled | System - Mootools12: Disabled | Kunena Discuss 1.6.4

Modules: Kunena Stats 1.6.4 | Kunena Login 1.6.4

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

More
14 years 10 months ago #98828 by Matias
Replied by Matias on topic Re: 500 Error in Forum Configuration and forum
Yes, the issue seems to be in CB integration -- something goes wrong in there.

Please share us your 500 errors (debug turned on): if they come from Joomla they are usually very useful.

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

More
14 years 10 months ago #98838 by Bob Britt
Replied by Bob Britt on topic Re: 500 Error in Forum Configuration and forum
Yes it would be useful. But there's no debug info.

This is the full text of the error, even with debug on..trying to access the forum configuration page on the admin side.

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
Apache mod_fcgid/2.3.5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at www.modelersalliance.com Port 80

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

More
14 years 10 months ago #98884 by Matias
Replied by Matias on topic Re: 500 Error in Forum Configuration and forum
The issue suggests that you could have a bad PHP or Apache configuration, broken .htaccess file, you could be running into a PHP bug or something like that. Usually when someone gets this error, it's happening in application level (Apache or PHP compiler itself), not inside PHP script. In most cases these errors are easy to fix, though, as the most common reason is a small typo in some configuration file.

In most cases finding out where Apache stores its error log file and looking into last lines just after reloading the page should reveal you what's happening.

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

More
14 years 10 months ago #98899 by Bob Britt
Replied by Bob Britt on topic Re: 500 Error in Forum Configuration and forum
Thanks for you interest in this issue Matias, I will try to get access to the apache log files and see if anything is going on there can can track this down.

I checkouted out the htaccess file, I find this section in my current file,
Code:
########## Begin - Joomla! core SEF Section # RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_URI} !^/index.php RewriteCond %{REQUEST_URI} (/|\.php|\.html|\.htm|\.feed|\.pdf|\.raw|/[^.]*)$ [NC] RewriteRule (.*) index.php RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization},L] # ########## End - Joomla! core SEF Section

Compaired to the default I find from the Joomla install files.
Code:
########## Begin - Joomla! core SEF Section # RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] # # If the requested path and file is not /index.php and the request # has not already been internally rewritten to the index.php script RewriteCond %{REQUEST_URI} !^/index\.php # and the request is for root, or for an extensionless URL, or the # requested URL ends with one of the listed extensions RewriteCond %{REQUEST_URI} (/[^.]*|\.(php|html?|feed|pdf|raw))$ [NC] # and the requested path and file doesn't directly match a physical file RewriteCond %{REQUEST_FILENAME} !-f # and the requested path and file doesn't directly match a physical folder RewriteCond %{REQUEST_FILENAME} !-d # internally rewrite the request to the index.php script RewriteRule .* index.php [L] # ########## End - Joomla! core SEF Section

Can't answer why they are so different. Can you see any issues there?

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

  • C0n
  • C0n's Avatar
  • Offline
  • Premium Member
  • Premium Member
  • Only the strongest will survive
More
14 years 10 months ago - 14 years 10 months ago #98904 by C0n
Replied by C0n on topic Re: 500 Error in Forum Configuration and forum
The only diffrence i see is you authorize the http request before you allow them access to execute the index.php no diffrence in the files only in the .htaccess rules order.
Last edit: 14 years 10 months ago by C0n.

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

Time to create page: 0.260 seconds