Question 500 Error in Forum Configuration and forum

what would you think about overwriting the "/public_html/administrator/components/com_kunena" folder with the contents of the known good one on the newly created test website?

Scratch that.

I think this is obviously third party related. Here's what I did. I renamed the kunena_config table, renamed the /public_html/administrator/components/com_kunena directory. Reinstalled Kunena from the install link and without making any changes to the default configuration the Forum Configuration page still does not load. I put everything back to the way it was so no progress or regression.

I guess a side by side comparison of the file system is next. Verifying files from the known good site with the effected site.

Want to bounce this off you Sozzled, see what you think.

I was comparing the clean install with my broken install and found a number of files on my broken config that are not on the clean. I assume these are from previous installs of Kunena since I have been running this instance since early 1.5 version. one file specifically that I find, kunena.communitybuilder.php is not in the new version.

here's the two options I'm thinking of trying.

1. Rename the "/public_html/components/com_kunena" directory and reinstall Kunena.

2. Rename the "/public_html/components/com_kunena" and load a copy from the known good directory from the other site.

3. any suggestion you have?

Disregard, I've already tested this in reverse on my test site and I could not make the test site break in the matter that my live site is broke. To recap, I copied the installation of Kunena to my test site, data base tables and all. Could not break it. Has to be in the CB component.

GOT IT!
Well the error message

I blanked out my account name.

So who is this, Kunena or CB?

The call comes from Kunena: ../administrator/components/com_kunena/libraries/integration/access.php on line 288. Why it happens, we don't know. Your situation is unusual. You had an abortive attempt to upgrade or migrate to J! 1.6 and it's left "stuff" behind. A solution may involve unpacking a fresh J! 1.5.23 kit over your site. I just don't know if patching-up or applying more band-aids is worth the effort.

What you found only confirms what we already knew. For some reason, Kunena does not like something on your site and Kunena objects in such a way as to result in a HTTP 500 error. Not very elegant but, then again, whatever's causing the problem is not too nice, either.