We've now spent 3 man days on this.

We did a repeated the clean install on a subdirectory of the live system which you are welcome to test. This gave the same results as the dev system. This like dev is using GJ 2.4. Further testing showed that if the category was saved, each group saved and the groups in kunena saved user access works. The same applies to the dev server.

The only issue is that a user who is not a member of the group can access from Kunena.

So with GJ 2.4 the issue seems to be caching as saving probably flushes the cache.

We can live with the preceding.

However you kindly installed 2.5rc on our system and as we've detailed earlier the access works from GJ OK but not from Kunena - that is consistent and we could live with that. Live we can live without forums but we cannot live without a working autojoin.

The 2.5 auto join seems to be broken and we've had to turn off registration.

We're now faced with having to install a backup pre 2.5 onto our live system if you cannot fix auto join.

Thanks will go and play. We've also explained why when we turned on debug we got a 500 error about a broken join.

As we've built the clean bare install on a subdirectory of live do you want the path and users?

Sorry excuse our stupidity should have reported as soon as found. It occurred whenever a user tried to access their profile. Header as follows

500 - JDatabaseMySQL::query: 1140 - Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause SQL=SELECT COUNT(*), a.`id`, a.`title`, a.`access`, a.`introtext` AS blog_intro, a.`fulltext` AS blog_full, a.`state` AS published, a.`created`, a.`modified`, a.`ordering`, b.`id` AS section_id, b.`title` AS section_name, c.`id` AS category_id, c.`title` AS category_name, d.`id` AS user_id, d.`name` AS user_name, d.`username` AS user_username FROM `jos_content` AS a LEFT JOIN `jos_sections` AS b ON a.`sectionid` = b.`id` LEFT JOIN `jos_categories` AS c ON a.`catid` = c.`id` LEFT JOIN `jos_users` AS d ON a.`created_by` = d.`id` WHERE a.`sectionid` = 34 AND a.`access` <= 2 AND a.`created_by` = 72 AND b.`published` = 1 AND b.`access` <= 2 AND c.`published` = 1 AND c.`access` <= 2

The error no longer occurs on the live system - you seem to have fixed it

We were trying to isolate it by turning off every component and plugin 1 by 1

Thanks and regards - if you need anything else just ask