Problem
| Info |
|---|
For Multiexcerpt - Cloud: Some of the Emoticons are not rendering properly when place placed inside a MultiExcerpt This happens only in the new fabric(V2) page editor. It works for the old editor. This is only an issue in Confluence Cloud. It only happens for the dynamic (Fast) MultiExcerpt and MultiExcerpt Include macros. Atlassian has announced that they will NOT remove the legacy page editor from Confluence so you can use that editor: Atlassian says, "The legacy editor isn't going anywhere" Emoticons we know work It does not happen for the static macros. Emoticons that were available in old/legacy pages work fine in the new/fabric page editor:
Emoticons that are new in the new/fabric page editor are broken |
Why it Happens
Atlassian has removed access to the information about how the Emoticon is rendered.
Workaround
We have searched for a workaround but it's not possible given the nature of this bug. Atlassian has removed the information we could use to fix it on our end. So we don't have the information needed to know what the original emoji value wasConfluence incorrectly styles "new" emoticons as "emoticon-blue-star" when they are rendered in the body of a third party macro (if the macro is a "rich-text staticContentMacro").
THIS IS A BUG IN CONFLUENCE: CONFCLOUD-69848
We recommend that you open a support case directly with Atlassian requesting that the source of emoji values be available to third-party rich-text macros. Please give your feedback to Atlassian about their decision to provide this information to macros by voting on or commenting on CONFCLOUD-69848
Workaround
If you use the new/fabric page editor then use the DYNAMIC (Fast) MultiExcerpt macros instead of the STATIC ones. The “Fast” MultiExcerpt macros are the dynamic ones. See /wiki/spaces/SUP/pages/147360348
Same thing goes for MultiExcerpt Includes. Use the DYNAMIC (Fast) ones instead of the STATIC ones. Emoticons that are available in the new/fabric page editor but not available in the old/legacy editor are the ones that are broken.
OR... use the old/legacy page editor. Atlassian has announced that they will NOT remove the legacy page editor from Confluence so you can use that editor: Atlassian says, "The legacy editor isn't going anywhere"
If your site does not have the legacy page editor template available when creating pages then you can open a support case with Atlassian to have them turn it on for your site.
We recommend that you open a support case directly with Atlassian requesting that the source of emoji values be available to third-party rich-text macros. Please give your feedback to Atlassian about their decision to provide this information to macros this bug by voting on or commenting on CONFCLOUD-69848
...
We are keeping track of our internal efforts by using Issue
...
| Jira Legacy | ||||||
|---|---|---|---|---|---|---|
|
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...