Important Fatal error from Kunena search plugin

Hi,
uninstalling the Kunena Search Plugin helped... but that's no news. The purpose was to be able to search in articles, Kunena, Blog, etc. from one search box, but for some reason the result was just a white page whenever I did a search with the Kunena search plugin enabled. But I've uninstalled both the plugin and the search module now. The latter, by the way, worked fine all along.

I am not sure what you mean with not having a Kunena menu..? On my homepage, I use the Joomla topmenu, and one of the items here is to the Kunena forum. In here, I have the Kunena Menu. Should I do this differently?

thnx so far.

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: 120 seconds | Max execution memory: 64M | Max file upload: 10M

Joomla default template details : bonusforum_20110718_hvid | author: bonus-forum.dk | version: 1.1 | creationdate: 2011-07-17

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!

[th]Kunena config settings:[/th]

board_title	Bonusforældre Forum
board_offline	0
board_ofset	0.00
offline_message	<h2>The Forum is currently offline for maintenance.</h2> <div>Check back soon!</div>
enablerss	0
enablepdf	0
threads_per_page	20
messages_per_page	6
messages_per_page_search	15
showhistory	1
historylimit	6
shownew	1
jmambot	0
disemoticons	0
template	example
showannouncement	1
avataroncat	0
catimagepath	category_images/
showchildcaticon	1
annmodid	62
rtewidth	450
rteheight	300
enableforumjump	1
reportmsg	1
username	1
askemail	1
showemail	0
showuserstats	1
showkarma	0
useredit	1
useredittime	1
useredittimegrace	600
editmarkup	1
allowsubscriptions	1
subscriptionschecked	1
allowfavorites	1
maxsubject	50
maxsig	300
regonly	0
changename	0
pubwrite	0
floodprotection	0
mailmod	0
mailadmin	0
captcha	0
mailfull	1
allowavatar	1
allowavatarupload	1
allowavatargallery	1
avatarquality	65
avatarsize	2048
allowimageupload	0
allowimageregupload	1
imageheight	800
imagewidth	800
imagesize	150
allowfileupload	0
allowfileregupload	1
filetypes	txt,rtf,pdf,zip,tar.gz,tgz,tar.bz2
filesize	120
showranking	1
rankimages	1
avatar_src	fb
fb_profile	fb
pm_component	no
userlist_rows	30
userlist_online	1
userlist_avatar	1
userlist_name	1
userlist_username	1
userlist_posts	1
userlist_karma	1
userlist_email	0
userlist_usertype	0
userlist_joindate	1
userlist_lastvisitdate	1
userlist_userhits	1
latestcategory	0
showstats	1
showwhoisonline	1
showgenstats	1
showpopuserstats	1
popusercount	5
showpopsubjectstats	1
popsubjectcount	5
usernamechange	0
rules_infb	1
rules_cid	1
help_infb	1
help_cid	1
showspoilertag	1
showvideotag	1
showebaytag	1
trimlongurls	1
trimlongurlsfront	40
trimlongurlsback	20
autoembedyoutube	1
autoembedebay	1
ebaylanguagecode	en-us
fbsessiontimeout	1800
highlightcode	0
rss_type	topic
rss_timelimit	month
rss_limit	100
rss_included_categories
rss_excluded_categories
rss_specification	rss2.0
rss_allow_html	1
rss_author_format	name
rss_author_in_title	1
rss_word_count	0
rss_old_titles	1
rss_cache	900
fbdefaultpage	recent
default_sort	asc
alphauserpointsnumchars	0
sef	1
sefcats	1
sefutf8	0
showimgforguest	1
showfileforguest	1
pollnboptions	4
pollallowvoteone	1
pollenabled	1
poppollscount	5
showpoppollstats	1
polltimebtvotes	00:15:00
pollnbvotesbyuser	100
pollresultsuserslist	1
maxpersotext	50
ordering_system	mesid
post_dateformat	ago
post_dateformat_hover	datetime
hide_ip	1
js_actstr_integration	0
imagetypes	jpg,jpeg,gif,png
checkmimetypes	1
imagemimetypes	image/jpeg,image/jpg,image/gif,image/png
imagequality	50
thumbheight	32
thumbwidth	32
hideuserprofileinfo	put_empty
integration_access	communitybuilder
integration_login	communitybuilder
integration_avatar	communitybuilder
integration_profile	communitybuilder
integration_private	uddeim
integration_activity	communitybuilder
boxghostmessage	1
userdeletetmessage	0
latestcategory_in	1
topicicons	1
onlineusers	1
debug	0
catsautosubscribed	0
showbannedreason	0
version_check	1
showthankyou	1
showpopthankyoustats	1
popthankscount	5
mod_see_deleted	0
bbcode_img_secure	text
listcat_show_moderators	1
lightbox	1
activity_limit	0
show_list_time	48
show_session_type	0
show_session_starttime	0
userlist_allowed	1
userlist_count_users	1
enable_threaded_layouts	0
category_subscriptions	topic
topic_subscriptions	every
pubprofile	0

Third-party components: CommunityBuilder: The file doesn't exist comprofilej.xml ! | Jomsocial 2.2.3 | UddeIm: The file doesn't exist uddeim.j15.xml !

Third-party SEF components: None

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

Modules: Kunena Latest 1.6.4

lovgret wrote: Uninstalling the Kunena Search Plugin helped...

I assume that you mean that you don't get the "white page" symptom any more, is that correct?

lovgret wrote: I am not sure what you mean with not having a Kunena menu..? On my homepage, I use the Joomla topmenu, and one of the items here is to the Kunena forum. In here, I have the Kunena Menu. Should I do this differently?

There is a "standard" approach. You've decided to do things differently; that's OK. I assume that you are fully familiar with the intricacies of the Joomla menu "system" - I have to admit, that the Joomla menu "system" is too complicated for me to understand and that's why I just do things the "standard" way.

If you want to customise your own Kunena menu there is a good technical article on that subject. Please read Customised Menus .

The main point that I want to ascertain is that we've positively identified the cause of the fatal error. If, as you say, uninstalling the Kunena Search (plugin or module) fixes the problem, then we may need to investigate this deeper. This is the first time we've received a report like this; maybe it has something to do with J! 1.6.x (or J! 1.6.5 in particular)?