FO 2.2.2 - Workspace and group permissions problem

[alx]

When upgraded from FO 2.2.1 to 2.2.2, there seems to be a problem with the group permissions:

Within the group that already exists, there are Internal Collaborator and Administrator accounts. Administrators can post and view all files correctly, within the designated workspace. The other users, however, cannot view a newly-posted file. The only way to make this possible is to:

• edit the workspace permissions for the given group
• select a higher-level workspace
• click on "apply to all submembers"
• Save changes

The aforementioned procedure must be repeated for every subsequent file that is added, or after the last file that has been uploaded, so that they all become visible.

The problem is similar to this topic:
Data is saved but disappears! - Workspace Permissions Problem

[asdfghj]

i have noticed some issues with with group permissions as well..

i seem to not be able to assign tasks to other users.  i can assign to myself, or the main company, but no the other users.  i have super admin privileges, and complete access to all workspaces and users.  i have tried group privileges with full rights to everyone and all the workspaces.  i have tried to set individual accounts with proper settings, and we cannot assign tasks to each other.  have not noticed any other issues, but this is a major one for me.

I upgraded from 1.7.5 to 2.2.2 because i had issues with previous 2.x versions and this seemed to be the most full/stable so i finally made the move.

[asdfghj]

i think there is definitely some kind of permissions issue with the new groups.

i had myself as super admin (still super admin) and my colleagues as executive, and their personal settings were at 0, ie, for each individual they had no permissions for anything.  they are all part of a group, that has full permissions for workspaces, full for users and limited for other admin stuff.  once i changed their user type to manager (instead of executive), with same user perms, and group perms, i can assign tasks to them.

i dont know if this is on purpose, but seems weird that user type trumps other permissions, for example, if a user is set to executive, but i give them additional custom permissions in a group, they should get those.  that way i dont have to change user type when i change permissions, just use the group setting for mass changes, and user type stays the same, so i dont have to explain why employee x is set to manager, but employee y is set to executive.

[dominusego]

Problem.

[alx]

Just upgraded from FO 2.2.2 to 2.2.3.1 and the problem persists 

[dominusego]

+1

[alx]

Just upgraded from FO 2.2.3.1 to 2.2.4 and the problem persists 

[dominusego]

+1

[lordfed]

I see the same problem  only on centos,
no problem on windows or ubuntu
and not mysql problem(it instald on centos where i fistly install fenq).
Sorry for my english.

[alx]

Well, I had two cases of different FO installations on Ubuntu and Debian, and they both had the same problem. I haven't tested it with a clean install to see how it behaves, but the latest upgrade has certainly not resolved the problem.

[franponce87]

Dear Everyone,

We have looked into this report you all made but were not able to reproduce it.
If you could please explain us step by step the reproduction steps, that would be much appreciated.
Perhaps it is an issue that started in a previous version and has already been fixed, or can you do this with the 2.2.4.1 version from scratch? I mean from scratch, not within an upgrade.

Thank you.

Best regards,
Francisco

[alx]

Francisco, you are right!

I just tested it on a clean installation of FO 2.2.4.1 on Windows with XAMPP (PHP 5.4.4) and the problem no longer occurs.

I initially noticed it on an Ubuntu installation with PHP 5.3.6-13ubuntu3.10, when upgraded from FO 2.2.1 to 2.2.2 and persists until the currently latest version (2.2.4.1).

I took a DB backup of a problematic installation, loaded it locally on the aforementioned XAMPP system and the problem is still there. Hence, it seems that it most probably is a bug in FO 2.2.2 that keeps propagating.

Assuming that I provide you with a copy of the "problematic" DB structure, would it be useful to you for looking into the matter and providing a remedy for it? (Unfortunately, I cannot provide you with the full data due to privacy issues).

Best regards,
Alex

[franponce87]

Dear Alx,

Thanks for your confirmation! No wonder we were not able to reproduce it..

All right then, when possible we will look into the matter again and see how it goes, but I have the following question as well: were you using Feng 1.X before and then upgraded to Feng 2?

As to accessing to your data, it would be MUCH easier and faster doing it that way, but, we cannot do it if you are not subscribed to our services.. therefore that is why we have not been able to look much into this nor solve it, even though we care.

Best regards,
Francisco

[alx]

Dear Francisco,

No, I did not use FO 1.x. The initial version was 2.0.0 (2.0.0.8 stable). Well, if you can find out what went wrong in the update from FO 2.2.1 to 2.2.2 and fix it in one of the future upgrade scripts, that would be fine.

I tried creating new users and/or groups, but it didn't make any difference. Making everyone an admin did not work either. It seems that there is no way to avoid the repeated update in the group permissions :/

By the way, offering to share my DB structure with you was not meant to be a "personal service" request, but rather to help you track down the source of the problem. It is then up to you whether and how you will make use of it. Can't demand much for something given for free


Regards,
Alex