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 33
    • Issues 33
    • 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
  • #3060
Closed
Open
Issue created Mar 11, 2014 by bmortier@bmortierMaintainer

We should try to ease migrations when schema attributes are disappearing

When we remove an attribute from the schema and LDAP objects still have it they can’t be edited though fd anymore.

(from redmine: issue id 3060, created on 2014-03-11, closed on 2014-08-07)

  • Relations:
    • relates #3230
  • Changesets:
    • Revision b97b4d9b by Côme Chilliet on 2014-07-29T16:04:00.000Z:
Fixes #3060 Using obsolete for deprecated attributes and objectclasses
  • Revision 50b99a4d by Côme Chilliet on 2014-07-29T16:04:35.000Z:
Fixes #3060 Using obsolete for deprecated attributes and objectclasses in schemas
  • Custom Fields:
    • Bug in version: 1.0.8
  • Uploads:
    • 0001-Fixes-3060-Using-obsolete-for-deprecated-attributes-.patch
    • 0001-Fixes-3060-Using-obsolete-for-deprecated-attributes-.patch
Assignee
Assign to
Time tracking