Content tree (Page tree) macro is not recognizing emojis added to page title's consistently

XMLWordPrintable

    • 1
    • Severity 3 - Minor

      Issue Summary

      If an icon was not in the "frequent used" emojis before and was added to the page title's emoji, it does not display the emoji icon in the content tree (page tree) macro as expected, it display a different emoji previously used in other page's title (or from frequent emojis) or the previous emoji used before changing to the current emoji chosen.

      The behavior is that it does not match the page's title emoji and left sidebar pagetree's emoji to what is displayed in the macro's emoji.

      If you remove the emoji, publish and then try to add the emoji again, it also does not display the emoji correctly. Since the last option was "no emoji" it will display no emoji in the macro.

      Sometimes if status are added to the page, when changing status, it also changes emojis randomly to another previously used emoji in the page's title.

      Steps to Reproduce

      1. Create a page with the page tree macro with @ self or home in the macro's options
      2. Create some pages as children pages of the previous page created, with a title but with no emoji
      3. Add some emojis to the page's content and other page's titles now and publish, e.g: :zap, :eye, :tennis and :yarn 
      4. Check the parent page page tree macro
      5. Add an emoji to the title and publish e.g: zap emoji
      6. Add another emoji, eg.: eye and publish
      7. Check the parent's page tree macro
      8.  Add another emoji not used before: e.g: minus emoji
      9. Check the page tree macro
      10. Hard refresh and check the page tree macro on the parent page again

      Expected Results

      Emojis will change everytime on the parent's page page tree macro, when the children page is published.

      Actual Results

      Page tree's macro is not updated  with the emoji used (minus example).

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            Assignee:
            Unassigned
            Reporter:
            Jessica
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: