Question Migrating from Kunena 1.5.11 to 1.7.2 broke category manager "add categories" function.

Please advise,

I have a Joomla 1.5.25 site that had Kunena 1.5.11 stable running on it.

When installing Kunena 1.7.2 it identified the older version and gave me the option to migrate my database. I did migrate my database and no errors were reported - all steps were reported with a green ok. Outwardly everything looked good.

However now whenever I try to add a new category, Kunena assigns it Id 0 and that apparently violates database integrity.

• It screws up the nesting / offset display for nested categories - creating additional incorrect indentation (confused over parentage?)
• When I try to edit that category, it is missing information (e.g. title) but querying the categories table shows the data is there.
• When I try to save any changes to that broken category I get a duplicate key SQL error on Id 0
• When I try to add additional categories, I get a duplicate key SQL error on Id 0.

When I delete that new category (that broke the database) integrity appears to be restored, except that no new categories can be added without causing the above errors.

When I restore the database and downgrade back to version 1.5.11 all appears to be working normally again e.g. I can add categories without causing errors.

My configuration info:

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: 96M | Max file upload: 10M

Kunena menu details:

Joomla default template details : yoo_phoenix | author: YOOtheme | version: 5.5.19 | creationdate: January 2012

Kunena default template details : Blue Eagle (default) | author: Kunena Team | version: 1.7.2 | creationdate: 2012-01-31

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

Warning: Spoiler!

[th]Kunena config settings:[/th]

board_offline	0
board_ofset	0
enablerss	0
enablepdf	1
threads_per_page	20
messages_per_page	6
messages_per_page_search	15
showhistory	1
historylimit	6
shownew	1
jmambot	0
disemoticons	0
template	default
showannouncement	1
avataroncat	0
catimagepath	category_images/
showchildcaticon	1
annmodid	62
rtewidth	450
rteheight	300
enableforumjump	0
reportmsg	1
username	1
askemail	0
showemail	0
showuserstats	1
showkarma	1
useredit	1
useredittime	0
useredittimegrace	600
editmarkup	1
allowsubscriptions	1
subscriptionschecked	1
allowfavorites	1
maxsubject	50
maxsig	300
regonly	0
changename	0
pubwrite	0
floodprotection	0
mailmod	1
mailadmin	0
captcha	1
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	zip,txt,doc,gz,tgz
filesize	120
showranking	1
rankimages	1
avatar_src
fb_profile
pm_component
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	my
default_sort	asc
alphauserpointsnumchars	0
sef	1
sefcats	0
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	none
integration_activity	communitybuilder
boxghostmessage	0
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	720
show_session_type	0
show_session_starttime	0
userlist_allowed	0
userlist_count_users	1
enable_threaded_layouts	0
category_subscriptions	post
topic_subscriptions	every
pubprofile	1
thankyou_max	10
email_recipient_count	0
email_recipient_privacy	bcc
email_visible_address
captcha_post_limit	0

Third-party components: CommunityBuilder 1.7.1

Third-party SEF components: None

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

Modules: None

Please advise of any workarounds or fixes for this problem.

I may have isolated fixed the problem.

1. Skimming a LOT of posts in this forum, I finally stumbled one that mentioned

(yoursebsite)/administrator/index.php?option=com_kunena&view=install&layout=schema

to report on schema differences - (expected vs found?)

2. Comparing the scheme differences report to the jos_kunena_... table structures, I found several tables with a primary key of "id" that should be autonum but was NOT. I used MySql administrator to correct all instances where I found that.

That seems to have corrected the categories problem I cited. Too early to tell if it broke (or failed to fix) anything else.

I did notice what may be errors in that schema diagnostic...

Several text fields are defined in the database as not null with default value of "" but the schema checker appears to be looking for not null with no default value.

I left those fields as not null with default "" even though scheme checker doesn't like that.

Some examles:

Schema diff report:

<table name="kunena_announcement" action="alter">
<field name="title" type="tinytext" null="0" action="alter" after="id"/>
<field name="sdescription" type="text" null="0" action="alter" after="title"/>
<field name="description" type="text" null="0" action="alter" after="sdescription"/>
</table>

vs Schema:

<table name="kunena_announcement">
<field primary_key="yes" name="id" type="int(3)" null="0" extra="auto_increment"/>
<field name="title" type="tinytext" null="0" default=""/>
<field name="sdescription" type="text" null="0" default=""/>
<field name="description" type="text" null="0" default=""/>
<field name="created" type="datetime" null="0" default="0000-00-00 00:00:00"/>
<field name="published" type="tinyint(1)" null="0" default="0"/>
<field name="ordering" type="tinyint(4)" null="0" default="0"/>
<field name="showdate" type="tinyint(1)" null="0" default="1"/>
<key name="PRIMARY" unique="1" columns="id"/>
</table>

Another example:

Diff report:

<table name="kunena_categories" action="alter">
<field primary_key="yes" name="id" type="int(11)" null="0" extra="auto_increment" action="alter"/>
<field name="description" type="text" null="0" action="alter" after="hits"/>
<field name="headerdesc" type="text" null="0" action="alter" after="description"/>
<field name="class_sfx" type="varchar(20)" null="0" action="alter" after="headerdesc"/>
</table>

vs Schema report:

<table name="kunena_categories">
<field primary_key="yes" name="id" type="int(11)" null="0" default=""/>
<field name="parent" type="int(11)" null="1" default="0"/>
<field name="name" type="tinytext" null="1"/>
<field name="cat_emoticon" type="tinyint(4)" null="0" default="0"/>
<field name="locked" type="tinyint(4)" null="0" default="0"/>
<field name="alert_admin" type="tinyint(4)" null="0" default="0"/>
<field name="moderated" type="tinyint(4)" null="0" default="1"/>
<field name="moderators" type="varchar(15)" null="1"/>
<field name="accesstype" type="varchar(20)" null="0" default="none"/>
<field name="access" type="int(11)" null="0" default="0"/>
<field name="pub_access" type="tinyint(4)" null="1" default="1"/>
<field name="pub_recurse" type="tinyint(4)" null="1" default="1"/>
<field name="admin_access" type="tinyint(4)" null="1" default="0"/>
<field name="admin_recurse" type="tinyint(4)" null="1" default="1"/>
<field name="ordering" type="smallint(6)" null="0" default="0"/>
<field name="future2" type="int(11)" null="1" default="0"/>
<field name="published" type="tinyint(4)" null="0" default="0"/>
<field name="checked_out" type="tinyint(4)" null="0" default="0"/>
<field name="checked_out_time" type="datetime" null="0" default="0000-00-00 00:00:00"/>
<field name="review" type="tinyint(4)" null="0" default="0"/>
<field name="allow_anonymous" type="tinyint(4)" null="0" default="0"/>
<field name="post_anonymous" type="tinyint(4)" null="0" default="0"/>
<field name="hits" type="int(11)" null="0" default="0"/>
<field name="description" type="text" null="0" default=""/>
<field name="headerdesc" type="text" null="0" default=""/>
<field name="class_sfx" type="varchar(20)" null="0" default=""/>
<field name="allow_polls" type="tinyint(4)" null="0" default="0"/>
<field name="id_last_msg" type="int(10)" null="0" default="0"/>
<field name="numTopics" type="mediumint(" null="0" default="0"/>
<field name="numPosts" type="mediumint(" null="0" default="0"/>
<field name="time_last_msg" type="int(11)" null="1"/>
<key name="PRIMARY" unique="1" columns="id"/>
<key name="parent" columns="parent"/>
<key name="published_pubaccess_id" columns="published,pub_access,id"/>
<key name="msg_id" columns="id_last_msg"/>
<key name="category_access" columns="accesstype,access"/>
</table>

Regardless, it seems that the migration from 1.5.11 to 1.7.2 is NOT properly setting all the necessary attributes on the new jos_kunena_... tables it creates.

Thanks for that information, rasharon (although I'm not personally sure what I can do with it), and I'm trying to attract the attention of the Kunena development team to your issue. I can say, from my own experience, that I've successfully upgraded K 1.5.x to K 1.7.x quite easily and without the issues you've mentioned. I vaguely recall that, once upon a time, I struck a problem upgrading from K 1.5.9 to K 1.6.0-beta (I think) but we resolved that issue relating to a database schema inconsistency and that the installer procedure was modified because of the problem that I had encountered. But this was, like, about 18 months ago and we haven't had any issues reported since then.

From the overall sounds of things, you've fixed your problems. I'm sorry that, in your case, the upgrade was not a totally smooth operation. I hope that others will learn from your experience.

As far as I know, the upgrade to K 1.7.2 (from any of Fireboard, K 1.0.x, K 1.5.x, K 1.6.x) should be a two-mouseclick set-and-forget matter.. Sometimes it's not. Oh well, these things happen.