"This macro does not provides rendering in WYSIWYG editor" escaping into copy
I'm not sure exactly what the steps are to reproduce yet but we have a client using the TinyMCE editor to edit content and add / edit macros and we are finding that often the text "This macro does not provides rendering in WYSIWYG editor" manages to leak into the actual page copy.
Googling the phrase terms up a few sites that seem to have suffered the same problem.
Does anyone have any familiarity with this and what usage might be causing it?
This only happens occasionally. I suspect when the user is editing an existing macro or perhaps they are copy-pasting in the wysiwyg.
Whilst it looks like that text was leaking outside of the macro into the main copy, on a couple of pages I just looked at, re-publishing the page fixed the problem which suggests to me something else is happening. I can't think what the problem might be that just republishing would fix it
The content is fetched from an umbraco:Item in the template.
"This macro does not provides rendering in WYSIWYG editor" escaping into copy
I'm not sure exactly what the steps are to reproduce yet but we have a client using the TinyMCE editor to edit content and add / edit macros and we are finding that often the text "This macro does not provides rendering in WYSIWYG editor" manages to leak into the actual page copy.
Googling the phrase terms up a few sites that seem to have suffered the same problem.
Does anyone have any familiarity with this and what usage might be causing it?
The site is running version 4.6.1
Thanks
Hi Patrick
Does this only happen on certain occasions or everytime the macro is saved?
And how is the content from the rich text editor fetched? Using a XSLT macro or umbraco:Item in the template?
/Jan
Hi Jan
This only happens occasionally. I suspect when the user is editing an existing macro or perhaps they are copy-pasting in the wysiwyg.
Whilst it looks like that text was leaking outside of the macro into the main copy, on a couple of pages I just looked at, re-publishing the page fixed the problem which suggests to me something else is happening. I can't think what the problem might be that just republishing would fix it
The content is fetched from an umbraco:Item in the template.
Thanks
is working on a reply...