Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-85254

Workflow doesn't know which of the available languages is the default one

    Details

    • Type: Bug
    • Status: Closed
    • Resolution: Duplicate
    • Affects Version/s: 7.0.0 DXP SP7, 7.0.X, 7.1.0 CE GA1, Master
    • Fix Version/s: None
    • Labels:
    • Fix Priority:
      3

      Description

      Summary
      When site's current language is not contained in the available languages of the asset, Workflow doesn't know which of those was chosen to translate the content title, therefore causing a mismatch between the flag icon and the translated title itself.

      Steps to Reproduce

      1. Go to Liferay > Content > Web Content;
      2. Click on New > Folder, fill the required fields and Save;
      3. After creating the Folder, click on the content's options, then Edit;
      4. Under "Structure Restrictions and Workflow", choose "Default Workflow for this Folder";
      5. Select the Single Approver Workflow and Save;
      6. Enter the Folder;
      7. Add a new Basic Web Content and Submit for Publication;
      8. My Account > My Workflow Tasks > Assigned to My Roles;
      9. Change the site's language to Portuguese (append /ja/ after hostname:port in URL);
      10. Click on the pending task;
      11. Note that above the Web Content's title, the Brazil flag is displayed;

      Actual Results
      The flag icon that chooses the language of the content's title shows pt_BR even though the only translation available is en_US.

      Expected Behavior
      Workflow should know what is the language used in the translation of the content's title and match that with the flag icon instead of displaying the flag of the current site's language.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Days since last comment:
                  26 weeks, 3 days ago