Hi,
I was using the renderer FckEditor in Jira 3.5, and I had to switch to JEditor when I upgraded to 6.1.
For most of the fields, the rendering is correct, but in some cases the html tags are escaped (for example <br/> becomes <br/>). Therefore the tags are visible in the rendered view.
Anybody knows why it happened? And why it only happened in some places?
Hi Pierre,
Please check that Enter mode is set to Paragraphs in JEditor Configuration.
There's also a known bug where JEditor decides to render a field using wiki renderer. In this case wiki renderer encodes tags and tags become visible. This problem is already fixed, the fix will come with JEditor 1.5.48 (next release).
Hi Alex,
Thanks for your answer. Enter mode was already set to Paragraph, but I found a workaround: I simply copied the content of the rendered view to the Source view.
When will the new version be relased?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ETA is next week.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I have upgraded to 1.5.48, but the problem is still there:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Pierre,
These html tags look like copied from one of MS products. Do you see the tags only after copying contents or when you type text into the editor too?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We were using Jira 3.5 with Fckeditor, and when we migrated to Jira 6.1 and JEditor, that rendering problem appeared on some issues. When creating new issues there is no problem.
I know that some users used to copy from word into fckeditor, so it may be the reason why only some fields have rendering problems.
One possibility is to copy the content of the rendered view into the source view, but the problem is that there are thousands of fields with that problem. Do have an idea about how I could fix all the problematic field quicklier?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The problem is clear now.
When JEditor renders fields it decides if the contents are html formatted or wiki formatted (wiki text can contain html). It looks like for some code created by FCK JEditor makes incorrect decision.
The simplest way to fix this on your side is to update all of these fields in DB wrapping content into <div> ... </div> tag. This will force JEditor to render as html.
On our side we can change the patterns used to decide if the content is html.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have tried to wrap the content of some fields with <div>...</div> with an SQL update, but the field still aren't rendered correctly.
Even though the whole content is wrapped in a div in the DB, in Jira, there is a paragraph after the </div> tag (in the Source view):
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you start editing an issue where tags are visible and save it with JEditor the issue will be stored like this in DB. If you already saved this issue before then wrapping with <div> tags won't help.
However other issues should be fixed, try checking them.
If this problem persists in all issues please check the html in DB, there should be no encoded tags (like < and >).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok, you are right, it works for the unedited fields :). I also had to wrap the columns oldstring and newstring in the table changeitem so that the change history is rendered correctly.
Thanks a lot for you help!
Pierre
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.