Hi, Abe.

the fix we have given you - SQL query - should have fixed the issue, if it hasn't then we need site/database access. Without access there is no more I can do for you... I'm sorry.

Thanks for your curt input Michal,

First, I'm Ade, and not Abe. Some duty of care would help Jomsocial, and also make my day!

And , yes...it's apparent that there is not more you can do on this. Maybe someone else may have a more user-friendly solution
without needing to pore through own company's entire database.

No, I vehemently disagree. I'd like to argue that poring our company's database is not a great substitute for a good workable solution!

I repeat, the seemingly viable portion is at www.jomsocial.com/forum/installation/168...ql-select-count-from but the solution was not shown and was inconclusive in this thread.

Regards.

Hi Ade,

We can assist with fixing your fault by many methods

1. With the requested access, so we can look at the database and repair as needed
2. You can provide a test site that is a copy of the live site. If user privacy is an issue then you populate the test database with dirty data
3. You can provide us with a SQL table structure only so we can compare where the error may be.
4 You can now upgrade to Jomsocial 4 which is the current version and see if that fixes it.
5. You can continue to try and find a resolution yourself without providing us access but this can often cause frustration and make an issue continue for a lot longer than needed.
6 You can get a second opinion from an independent 3rd party developer if you believe our suggestions for the solution may not be correct.

Continuing this post is in it's current state is counter productive unless you are going to allow us to help you by choosing one of the above options,

Hi Paul.

I shall be bringing some issues to your attention in good time.

For now, I assure you that unusual effort has been made on this thread to enable a productive solution already, with some patience. So far, I (and team) have installed and looked through every single available version of Jomsocial since 2010. To recap, the problem is not present in the last version of 3.1.x; this singular issue started with the first version of Jomsocial 3.2. As a starting point (vide your Point 3), it seems reasonable to repeat that the shots of table structure were provided 3 days ago. I'd said (above):

'I checked/compared own xxx_community_groups with your screen-capture and both matched. Please see a complete shot of own _community_groups at www.mysite/php-myadmin-database-tables.html . Am I missing something here?'

There's more capture if required. Again, the page is www.mysite/php-myadmin-database-tables.html

Regards.

Hi Ade,

The database needs the query run on it that you were given to correct the issue. Please show a screen shot of the result of that query once it has been run.

Quick Update:

Hi Paul.

Thanks for getting back. I appreciate it.

This serves to confirm receipt moments ago. I'm on the move between locations and shall get someone to look at it or set about it myself, in good time, on return to the office. 'Shall definitely get back.

Regards.

Hi Paul.

Ha, I took a closer crack at it and it's solved. How?

1. Trying the provided code gave the same error result, exactly as included in my post 5 days ago (see screen shot as requested at www.mysite.com/php-myadmin-database-tables.html ).

2. I have the niggling feeling the code might have worked on older versions of php; but with language deprecations, etc., etc. on php5, I thought to look closer at the ensuing #1064 error result; error was because the code surrounded the table and field names with '

3. Deciding it was not own server side issue, running ALTER TABLE xxxx_community_files ADD groupid INT(11) NOT NULL; did the trick and each group is back (xxxx for own table).

[Now thinking of other different flaws needing fixing...]

Regards.