fdCommunityMembershipType should no be used/displayed in community projects dep.

Hi,

Running 1.0.13-fixes

fdCommunityMembershipType is intended to community organization department, not project, like it is described in the current 'fdCommunityMembershipType' objectclass's attributes.

Currently, applying any change to a community project raise the error "attribute 'fdCommunityMembershipType' not allowed," which is normal as it is not expected to appear in community projects tab.

(from redmine: issue id 4927, created on 2016-06-27, closed on 2016-06-29)

• Changesets:
  • Revision 282c8405 by Côme Chilliet on 2016-06-29T04:31:06.000Z:

Fixes #4927 Removed membership options from Community projects

• Revision 7bc01c29 by Côme Chilliet on 2016-06-29T04:32:08.000Z:

Fixes #4927 Removed membership options from Community projects

• Custom Fields:
  • Bug in version: 1.0.13

I don’t understand the explanation. fdCommunityMembershipType is in organizations, not projects, what is the problem?

(from redmine: written on 2016-06-28)

"Currently, applying any change to a community project raise the error "attribute 'fdCommunityMembershipType' not allowed," which is normal as it is not expected to appear in community projects tab."

What I mean is Membership type field exists in project's department form. Which is not expected.

(from redmine: written on 2016-06-28)

Ok, my bad, I didn’t see communityProject was using communityOrganisation as a base. I removed the membership section from the attribute list in communityProject.

(from redmine: written on 2016-06-29)

hello,

tested it works well

Closing it

Cheers

(from redmine: written on 2016-06-29)

Close issue

(from redmine: written on 2016-06-29)

closed

added Removed label