Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 920
    • Issues 920
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • Core
  • Issues
  • #1815

Closed
Open
Opened Jun 12, 2020 by gibsonoliver@gibsonoliverDeveloper

Use of the word disable in CiviCRM user screens

I've been thinking recently about the use of the word 'disable' in Civi. It's used quite a lot in the custom data screens/ relationship screens/ options screens etc.

One suggestion is that this is replaced with activate / deactivate. Rather than enable / disable.

Although it may be the right use of the word according to a dictionary definition I don't think its appropriate. Twice before this has been pointed out to me directly by training attendees that they are uncomfortable with its use.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dev/core#1815