- Posts: 9
- Thank you received: 0
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
Question [Topic archived by moderator] Recent Discussions/My Discussions show multiple copies of same post.
Thanks
Please Log in or Create an account to join the conversation.
It looks like our query fails to group threads together. I just cannot understand why
Please Log in or Create an account to join the conversation.
If I go into a topic there is just one copy of the record as there should be.
The only thing I've done recently to the forums is that I moved a topic from one forum to another but that was before the upgrade and it appeared to have worked.
Thanks for your time.
Please Log in or Create an account to join the conversation.
Looking at the upgrade.xml file included with Kunena, I believe that the "add_key" function didn't work on my upgrades. I believe because the tables are in the wrong collation. Should they be UTF8_General_ci for Kunena? Everything on my site is, except the FB tables.
Thanks for any help. Hope I'm making some sense.
Please Log in or Create an account to join the conversation.
1) Do you have custom code in Kunena?
2) Does your fb_users table have primary key on userid?
Collation does not matter (except it breaks UTF-8 characters), but it tells that you have used FB or K1.0 before. Did you also have J1.0? I ask this because migration scripts from J1.0 to J1.5 tend to break jos_fb tables.
PS: in our wiki is an article how to fix collation.
Please Log in or Create an account to join the conversation.
1) Do you have custom code in Kunena?
No custom code...
2) Does your fb_users table have primary key on userid?
It did not have a primary key on userid. It appears that the update file attempts to create that custom key. It did not on my table I tried to create the key manually with the sql statement used in the upgrade script and it errored indicating that there was already a column with that name. (also because I have duplicate userids right now.) The question I've got now is how to clean that user table up...
Could I empty it, add the primary key to user id and re-sync users in Kunena?
Yes, this site was originally on 1.0 and migrated to 1.5.
Thanks!
Please Log in or Create an account to join the conversation.