Question [SOLVED] Kunena Internal Error: upgrade to 1.7, using jomsocial and jms multisite

Database collation check: The collation of your table fields are correct

Legacy mode: Disabled | Joomla! SEF: Disabled | Joomla! SEF rewrite: Disabled | FTP layer: Disabled |

This message contains confidential information

htaccess: Missing | PHP environment: Max execution time: 30 seconds | Max execution memory: 128M | Max file upload: 256M

Joomla default template details : rt_zephyr_j15 | author: RocketTheme, LLC | version: 1.5.2 | creationdate: October 13, 2010

Kunena default template details : Aphotic II | author: snilloconator | version: 1.6.3 | creationdate: 2010-12-30

Kunena version detailled: Installed version: 1.7.1 | Build: 5162 | Version name: UnderUret | Kunena detailled configuration:

Warning: Spoiler!

[th]Kunena config settings:[/th]

board_offline	0
board_ofset	0
enablerss	1
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	aphotic-II
showannouncement	1
avataroncat	0
catimagepath	category_images/
showchildcaticon	1
annmodid	62
rtewidth	450
rteheight	300
enableforumjump	1
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	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	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	categories
default_sort	asc
alphauserpointsnumchars	0
sef	0
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	auto
integration_login	jomsocial
integration_avatar	jomsocial
integration_profile	jomsocial
integration_private	jomsocial
integration_activity	alphauserpoints
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: AlphaUserPoints 1.5.12 | Jomsocial 2.0.4

Third-party SEF components: None

Plugins: System - Mootools Upgrade: Enabled | System - Mootools12: Disabled | Kunena Search 1.7.1 | My Kunena Forum Posts 1.7.1

Modules: Kunena Latest 1.6.0-RC2

I manage a community using joomla 1.5, jomsocial, kunena and jms multisite components.
After i upgraded to kunena 1.7.1 (from 1.6.x) i detect this problem only on the slave site www.thelastteam.com (not on the main site www.thelastgames.net ). The forum tables are shared between the 2 sites (linked). So what could be the problem?

Kunena Internal Error: Please enable Kunena Debug Mode and report problem in the www.kunena.org forum.

If i enable the debug mode, when i click on forum:

500 - JDatabaseMySQL::query: 1054 - Unknown column 'c.accesstype' in 'on clause' SQL=SELECT c.id FROM tlt_kunena_categories AS c INNER JOIN abc_community_groups_members AS g ON c.accesstype='jomsocial' AND c.access=g.groupid WHERE c.published=1 AND g.approved=1 AND g.memberid='68'

Hello,

What do you mena by the forum tables are shared between two sites, this is strange ? Is it worked before ?

In your table tlt_kunena_categories, there is missing the column accesstype i don't know why. Try to recreate this table.

Yes it worked before.
The sites use the same tables for kunena (the 2 db are linked and share some tables).

*** Topic moved ***

Looks like a mess to me. I don't see the support implications here (and that's why I moved the topic).

We don't support templates that are not written by the Kunena team. We don't support RC versions of Kunena add-ons. We don't necessarily "support" Kunena integration with every version of Jomsocial, either. Lastly, I don't know who knows about how to run Kunena from two different websites sharing the same database table.

What do the folks at JomSocial have to say about your problem?

It looks like tlt prefixed database was not upgraded when you upgraded Kunena. Table 'tlt_kunena_categories' should have field called 'accesstype', but it doesn't.

So obviously you either failed to upgrade both sites or the plugin that helps you to share tables between sites isn't working with our ALTER TABLE queries during upgrade process.

Moved to support: this issue has nothing to do with JomSocial.

Where is located the installed version when the installation packet check if i need upgrades? is there a version.xml or something similar? thanks

It's in database, can-i see the structure of your table jos_kunena_categories ?

before that i would like to explain you the situation.

Our site, www.thelastgames.net , is a social network based on joomla 1.5.25 plus jomsocial 2.04 and kunena forum.

The community needed to deploy multiple subsites for gamers teams and clans so we decided to use Joomla Multisite component (latest version installed 1.2.69)

All the other components upgrades was done easily, as described on extension upgrade instruction on jms guides.
The procedure needed to update components within all the network is this one:
1) install the new version of the component on the main site
2) install the new version of the component on every subsite (if there are database changes)

As Kunena changed some tables from 1.6.2 (the previous version that was installed on the site) and 1.7.1 i proceeded with the upgrade also on the slave site. When i did that it says the 1.7.1 version of kunena is already installed, but then i start having the issues described before.
I asked to you where is stored the component version to try a trick:
If i remove the latest version update from the database or wherever is stored i can proced with the upgrade in the slave sites. I tried also that way deleting the row where version 1.7.1 is stored in kunena_version, but when i tried to upgrade from the subsite it says again that the version installed is 1.71. Why is that? Do i need to change or delete something else to deceive the component doing the upgrade?

Kunena detects installed version from the database -- and DB is saying that it's already the latest (because of you already installed it). So if you're using only one database, you should be able to make Kunena to work just by running the installer in all sites, even if it says that it's already using the latest version.

So if multisite component works right, you should be able to get all sites working just by doing what the guide says -- and ignore what Kunena is saying during the installation.