Uploaded image for project: 'Jahia Community'
  1. Jahia Community
  2. JAHIA-2968

Sp5: Category Field: no versioning/staging enable -> everything goes live straight ahead - no workflow status modification

Details

    • Bug
    • Resolution: Done
    • Major
    • xCM 5.0 SP5
    • xCM 5.0 SP4
    • None
    • Sp4 20722

    Description

      I have a std double page which is validated. I went on the metadata sub-engine and in the category field. I add a few category (just select the checkbox) and clicked on ok. No othre change in my container.

      -> the workflow state is staying green. No possible validation
      -> in Live mode the categoriy modifications are directly applied (I am usng the category browins template to verify what is available)

      TestRail: Results

        Attachments

          Activity

            [JAHIA-2968] Sp5: Category Field: no versioning/staging enable -> everything goes live straight ahead - no workflow status modification

            Yes SP5 sorry

            scroisier Stephane Croisier (Inactive) added a comment - Yes SP5 sorry

            you mean, sp5 ?

            tdraier_old Thomas Draier (Inactive) added a comment - you mean, sp5 ?

            So I repopen this issue for SP4 in order to be refactored.

            scroisier Stephane Croisier (Inactive) added a comment - So I repopen this issue for SP4 in order to be refactored.

            There's two way to get categories for a content object - either using the metadata, either using the category service.
            Metadata are workflow aware - the object must be validated so the categories goes live.
            CategoryService is not workflow aware, as it's based on jahia_link table - changes are directly live and aren't versioned.
            Keeping both systems is completely inconsistent - categoryService must be refactored to use only metadata fields. But probably not for sp4 ..

            tdraier_old Thomas Draier (Inactive) added a comment - There's two way to get categories for a content object - either using the metadata, either using the category service. Metadata are workflow aware - the object must be validated so the categories goes live. CategoryService is not workflow aware, as it's based on jahia_link table - changes are directly live and aren't versioned. Keeping both systems is completely inconsistent - categoryService must be refactored to use only metadata fields. But probably not for sp4 ..

            For the point 2) in Live mode the category modifications are directly applied (I am usng the category browins template to verify what is available):

            Our category service does not distinguish between live and edit mode. Even if the metadata field itself supports staging, categories are managed via JAHIA_LINK database table, where no workflow state information is stored. Current API for categories also does not support it.

            Please let me know if the category service needs to be refactored for SP4 and I will open a new JIRA issue (or a subtask).

            shyrkov Sergiy Shyrkov (Inactive) added a comment - For the point 2) in Live mode the category modifications are directly applied (I am usng the category browins template to verify what is available): Our category service does not distinguish between live and edit mode. Even if the metadata field itself supports staging, categories are managed via JAHIA_LINK database table, where no workflow state information is stored. Current API for categories also does not support it. Please let me know if the category service needs to be refactored for SP4 and I will open a new JIRA issue (or a subtask).

            Fix for the point 1) -> the workflow state is staying green. No possible validation

            Resolution: corrected side-effect of the JAHIA-2883 fix. 'shared' language is not filtered out now, when retrieving language states
            Now the workflow state is correctly retrieved.

            shyrkov Sergiy Shyrkov (Inactive) added a comment - Fix for the point 1) -> the workflow state is staying green. No possible validation Resolution: corrected side-effect of the JAHIA-2883 fix. 'shared' language is not filtered out now, when retrieving language states Now the workflow state is correctly retrieved.

            People

              tdraier_old Thomas Draier (Inactive)
              scroisier Stephane Croisier (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                TestRail: Runs

                  TestRail: Cases

                    Packages

                      Version Package
                      xCM 5.0 SP5