Hi,

Installing CB pack on a bare new J!3.6.2 site looks good and works fine.

Now, I am on the way to convert a J!3.5 site to J!3.6.2
The first tests show that
- When the owner of a group posts a message only the last one is in the database ("POST n° 1" and then "POST n° 2" => only "POST n° 2" is in the database.
- Although, this last post is in the database, it cannot be seen in the Wall

- A member of the group that tries to post gets the message "You do not have sufficient permissions to edit this post."

I suspect that these problems may come from the "old" version.
Other CB plugins are OK.

What could I do to regenerate a clean GroupJive installation over the existing one?

BTW, tested either with the purity_iii and with protostar : both gave the same.

Thank you for your advice.
So I reinstalled GroupJive and went on with the following test

Groups:
Registered
|_ Member (13)
·|_ Paid Member (17)
··|_ Premium (29)
···|_ Gold (35)

Access:
Registered: Registered, Member, Paid Member, Premium, Gold
Member: Member, Paid Member, Premium, Gold
Paid Member: Paid Member, Premium, Gold
Premium: Premium, Gold
Gold: Gold

The TEST Group belongs to the TEST category which is set for Member access.

The test consist in posting a first post "P1"
and directly after, a second post "P2"

Results:

- OK means that we get the two posts apart with two lines in the #__groupjive_plugin_wall table
In such a case, within saveWallEdit in component.cbgroupjivewall.php, $row->id was NULL

- NOT OK means that the second post takes the place of the first one in the only one line of the #__groupjive_plugin_wall table
In such a case, within saveWallEdit in component.cbgroupjivewall.php, $row->id had a value (in my case, it was 1)

Between each test, the user accesses were modified directly, for instance:
DELETE FROM `#__user_usergroup_map` WHERE `user_id` = {the_user_id};
REPLACE INTO `#__user_usergroup_map` (`user_id`, `group_id`) VALUES ({the_user_id}, 43);
TRUNCATE TABLE `#__groupjive_plugin_wall`

The cache on the server was cleared.
and the user reconnected in the front end.

The following profiles of the same user {user_id} were tested:
(13) ## Member OK
(17) ## Paid Member OK
(29) ## Premium NOT OK
(35) ## Gold NOT OK

There is maybe a problem traversing the ACL tree.

I hope this will give some direction to find what's going on, because for the present the Wall is unusable for us.

Hi Krileon,

I did as you said : delete the table and reinstall GJ Wall => The bug is still there

Steps to reproduce the bug:
1- Post a message "Post 1" in the Wall
2- Immediately after, post a second message "Post 2" in the Wall (not an answer)
3- Delete the post(s) for the next test.

Member will show you the 2 Posts => OK
Connect as Adherent and repeat the 3 steps => OK
Connect as Premium and repeat the 3 steps => NOT OK: You will get the second post over the first one
Same connected as Gold => NOT OK

I sent you a PM.

Thank you for your attention