• Icon: Sub-task Sub-task
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • None
    • System
    • None
    • False
    • None
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • API CCS Sprint 37 (3Scale), API CCS Sprint 38 (3Scale), API CCS Sprint 39 (3Scale), API CCS Sprint 40 (3Scale), API CCS Sprint 42 (3Scale), API CCS Sprint 43 (3Scale), API CCS Sprint 44 (3Scale) 2

      Some attributes are not ignored when user would like to do update of object.
      Use case:

      • user read object via "/admin/api/cms/X/ {id}.json GET"
      • change/add some attributes
      • try to update object via "/admin/api/cms/X/{id}.json PUT"

      The update fails because some autogenerated attributes are not ignored in PUT. I think this is wrong because user should remove them before updating the object and attributes like these are ignored in other PUT API endpoints.

      File PUT autogenerated attributes: "created_at", "updated_at", "url", "title", "content_type"
      Section PUT autogenerated attributes: "created_at", "updated_at"
      Partial PUT autogenerated attributes: "created_at", "updated_at", "published"
      Page PUT autogenerated attributes: "created_at", "updated_at", "hidden", "published"
      Layout PUT autogenerated attributes: "created_at", "updated_at", "published"

            Unassigned Unassigned
            rh-ee-jlledo Joan Lledo
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: