Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fusiondirectory fusiondirectory
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 35
    • Issues 35
    • List
    • Boards
    • Service Desk
    • Milestones
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • fusiondirectoryfusiondirectory
  • fusiondirectoryfusiondirectory
  • Issues
  • #2142
Closed
Open
Issue created Mar 18, 2013 by bmortier@bmortierMaintainer

gosaMailAccount is used in core but is not in core.schema

Hello, We use gosaMailAccount is users filter. But in LDAP, if an objectClass does not exists, filter does weird things : (objectClass=gosaMailAccount) is FALSE, but (!objectClass=gosaMailAccount) is FALSE too. So either we move gosaMailAccount in core.schema or we change those filters.

(from redmine: issue id 2142, created on 2013-03-18, closed on 2013-03-20)

  • Changesets:
    • Revision 799671b4 by Côme Chilliet on 2013-03-20T10:24:24.000Z:
Fixes: #2142 Hiding mail filter when mail plugin is not installed
  • Revision 74969c01 by Côme Chilliet on 2013-03-20T11:04:13.000Z:
Fixes: #2142 Removing gosaMailAccount from filters if mail is not installed
  • Custom Fields:
    • Bug in version: 1.0.4
  • Uploads:
    • 0001-Fixes-2142-Hiding-mail-filter-when-mail-plugin-is-no.patch
    • 0002-Fixes-2142-Removing-gosaMailAccount-from-filters-if-.patch
Assignee
Assign to
Time tracking