Callout not recognized
in progress
Brianne Benett
When upgrading from the basic WYSIWYG editor to the advanced WYSIWYG editor, the callouts are often not recognized as such. Meaning when I click on the callout the contextual menu does not open and I can't edit it. Therefore, I must create a new callout in the advanced editor before editing.
Log In
D
D360 Product Management
in progress
D
D360 Product Management
closed
P
Prabhakaran Parasuraman
Hi Brianne, thanks for reaching out to us. We would like to understand the configuration you've provided in the old WYSIWYG editor for the callouts. If any screenshots of the basic WYSIWYG editor on the callouts will be great to understand your issue. Or do you expect to act on the callouts after switching to the Advanced WYSIWYG editor?
Should you have any specific preferences, feel free to share them. Your cooperation and understanding are appreciated.
Rachelle Carson
Prabhakaran Parasuraman I have noticed the same thing as Brianne. We didn't have any special configuration for callouts in the old editor, we just used the tool to insert them. When converting from the old editor to the new, the callouts lose the function to delete or edit or them properly. You can see in my screenshots how it changes the code when converting.
P
Prabhakaran Parasuraman
Rachelle Carson: Thanks for your response, we will investigate the mentioned issue and get back to you. Your patience and understanding are appreciated.
Rachelle Carson
Prabhakaran Parasuraman Thanks! I did misspeak about the ability to delete them. We can still do that. However, the formatting of the callouts looks totally different when converting from one editor to the other. This is not an ideal situation, as we'd have to manually redo all the callouts, if we want to use the new editor.
P
Prabhakaran Parasuraman
Rachelle Carson: Thanks for your patience. I would like to inform you that the issue you raised in the feedback has been successfully resolved. Now, all your callouts will be rendered as expected. We appreciate your time and valuable input. We would like to close this feedback.
If you have any further questions or need assistance in the future, please don't hesitate to reach out.
Rachelle Carson
Prabhakaran Parasuraman I just migrated an article to the new editor and I am seeing the same issues occurring. It doesn't appear to be fixed on my end.
P
Prabhakaran Parasuraman
Rachelle Carson: Thanks for your response. When you switch your article from the old WYISYWIG editor, the same configurations will be updated in the advanced WYSIWYG editor. All your previously reported issues are resolved and please try to switch to the advanced WYSIWYG editor now and let us know if you're still facing any issues in the callouts.
Your cooperation and understanding are appreciated. Thank you.
Rachelle Carson
Prabhakaran Parasuraman The issue remains that the callouts created in the old editor look different than the callouts created in the new editor. When I migrate an article, it keeps the old formatting for existing callouts and when I add a new one, it is a new format. My style guide and accessibility considerations do not permit me to have inconsistent formatting between articles and especially not within one article. Which means, I will have to go and manually recreate every callout in my KB, of which there are many. This is inconvenient and time-consuming.
P
Prabhakaran Parasuraman
Rachelle Carson, thanks for your response. As of now, while switching from the old WYSIWYG editor to the advanced WYSIWYG editor, all the format configurations with the format will be migrated. The border color has been provided as an additional function for the advanced WYSIWYG editors. You can now, include the border by clicking on the available functions from the floating menu of the callouts.
We will try to incorporate this in our future action items to display the callouts with border color as default and change the status of this feedback.
Your understanding and patience are appreciated. Thanks for your valuable time.
Liam Tanner
Rachelle Carson This is the exact issue I'm experiencing, and this is a blocker for us migrating to the new editor. Our knowledge base has approximately 1200 pages per version, so manually updating every callout across all articles isn't practical.
Prabhakaran Parasuraman Is there any update on whether this will be addressed?