#2699 - Composr 10 pre-RC13: Custom comcode tags are not being parsed when using WYSIWYG / tag assistant

By PDStig
Added 9th Jul 2016, 10:23 PM
5 views

Identifier	#2699
Issue type	Minor issue (breaks specific functionality)
Title	Composr 10 pre-RC13: Custom comcode tags are not being parsed when using WYSIWYG / tag assistant
Status	Completed
Handling member	Chris Graham
Addon	custom_comcode
Description	When using WYSIWYG / the comcode tag assistant, custom comcode tags are not being properly parsed. They are generated in such a way they are not rendered properly and instead rendered as direct text. When manually editing it to its proper format via. the source feature, it'll then work properly.
Steps to reproduce
Additional information	This seems to be a Composr 10 pre-RC13 issue as I didn't have this issue on RC12.
Funded?	No

The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Rating

Unrated

Comments

By Guest posted 10th Jul 2016, 9:34 AM

Can you be more specific on what you consider the "proper format" to be, and what exactly "direct text" means with respect to the editor?

They're not going to show final HTML direct in the editor, but I'm unclear exactly what you're seeing and what you are expecting.

By Guest posted 10th Jul 2016, 9:47 AM

I think you're saying that the highlighting effect isn't there (kbd tag in the source view)?
So just a very minor bug right?

By Guest posted 10th Jul 2016, 9:55 AM

Ok I found and fixed a problem in recent optimisations that caused the small bug I found and potentially others, so I'll consider this fixed unless reopened.

#2699 - Composr 10 pre-RC13: Custom comcode tags are not being parsed when using WYSIWYG / tag assistant

Rating

Comments

Statistics