View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
2699 | Composr | custom_comcode | public | 2016-07-10 02:23 | 2016-07-10 13:55 |
Reporter | PDStig | Assigned To | Chris Graham | ||
Priority | high | Severity | minor | ||
Status | resolved | Resolution | fixed | ||
Summary | 2699: Composr 10 pre-RC13: Custom comcode tags are not being parsed when using WYSIWYG / tag assistant | ||||
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. | ||||
Additional Information | This seems to be a Composr 10 pre-RC13 issue as I didn't have this issue on RC12. | ||||
Tags | No tags attached. | ||||
Attach Tags | |||||
Time estimation (hours) | |||||
Sponsorship open | |||||
|
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. |
|
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? |
|
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. |
Date Modified | Username | Field | Change |
---|---|---|---|
2016-07-10 02:23 | PDStig | New Issue | |
2016-07-10 13:34 | Chris Graham | Note Added: 0004116 | |
2016-07-10 13:47 | Chris Graham | Note Added: 0004117 | |
2016-07-10 13:55 | Chris Graham | Note Added: 0004118 | |
2016-07-10 13:55 | Chris Graham | Status | Not Assigned => Resolved |
2016-07-10 13:55 | Chris Graham | Resolution | open => fixed |
2016-07-10 13:55 | Chris Graham | Assigned To | => Chris Graham |