Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-25949

Ability to make Fields of a Content Type read-only

    Details

    • Type: Feature Feature
    • Status: Declined
    • Priority: High High
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: Customer request
    • Component/s: None
    • Labels:
      None

      Description

      When a field is read-only, users should not be able to change its value in the edit screen.

      Our use case:

      A field called “Name” on a Content Type should not be editable, it is set to a hard-coded value on creation as it must match a pre-defined value elsewhere in our system. If users are able to change the Name, the site will not work as expected.

      Example: Make published dates in article page read only. Please check attached screenshot for more details.

        Activity

        Sweta Pandey created issue -
        Sweta Pandey made changes -
        Field Original Value New Value
        Description When a field is read-only, users should not be able to change its value in the edit screen.

        Our use case:

        A field called “Name” on a Content Type should not be editable, it is set to a hard-coded value on creation as it must match a pre-defined value elsewhere in our system. If users are able to change the Name, the site will not work as expected.
        When a field is read-only, users should not be able to change its value in the edit screen.

        Our use case:

        A field called “Name” on a Content Type should not be editable, it is set to a hard-coded value on creation as it must match a pre-defined value elsewhere in our system. If users are able to change the Name, the site will not work as expected.

         Example: Make publication dates in article page read only. Please check attached screenshot for more details.
        Sweta Pandey made changes -
        Description When a field is read-only, users should not be able to change its value in the edit screen.

        Our use case:

        A field called “Name” on a Content Type should not be editable, it is set to a hard-coded value on creation as it must match a pre-defined value elsewhere in our system. If users are able to change the Name, the site will not work as expected.

         Example: Make publication dates in article page read only. Please check attached screenshot for more details.
        When a field is read-only, users should not be able to change its value in the edit screen.

        Our use case:

        A field called “Name” on a Content Type should not be editable, it is set to a hard-coded value on creation as it must match a pre-defined value elsewhere in our system. If users are able to change the Name, the site will not work as expected.

         Example: Make published dates in article page read only. Please check attached screenshot for more details.
        Sweta Pandey made changes -
        Attachment published_date.png [ 26860 ]
        Ricardo Correia (Inactive) made changes -
        Fix Version/s Customer request [ 11018 ]
        Hide
        André Rømcke added a comment - - edited

        Hi,

        this feature is planed to be covered in the next year by means of introducing native field groups (not config based), and secondly be able to limit permissions on these to archive what you request here and many other things. Potentially followup on that is to make these reusable so a set of fields (a field group) can be reused across content types.

        So declining this feature request as duplicate. For more information, to give input, and to watch, see: https://jira.ez.no/browse/EZP-24119

        Best,
        André Rømcke
        VP Engineering

        Show
        André Rømcke added a comment - - edited Hi, this feature is planed to be covered in the next year by means of introducing native field groups (not config based) , and secondly be able to limit permissions on these to archive what you request here and many other things. Potentially followup on that is to make these reusable so a set of fields (a field group) can be reused across content types. So declining this feature request as duplicate. For more information, to give input, and to watch, see: https://jira.ez.no/browse/EZP-24119 Best, André Rømcke VP Engineering
        André Rømcke made changes -
        Status Open [ 1 ] Declined [ 10015 ]
        Resolution Duplicate [ 3 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Declined Declined
        7d 2h 47m 1 André Rømcke 30/Jun/16 4:46 PM

          People

          • Assignee:
            Unassigned
            Reporter:
            Sweta Pandey
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: