Without richtext: missing empty spaces (and line breaks) when adding the FAQ article to your reply
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Reproduce the issue with Frontend::RichText disabled, a FAQ article containing line breaks, and a ticket reply using the FAQ selector. Compare the inserted content in AgentFAQEdit with AgentFAQZoom, then verify that field spacing and line breaks are preserved when the FAQ is added to the response.
Written by the indexing model from the issue text.
Description
When de-activating Frontend::RichText and afterwards reply to a ticket article, you see there are missing empty spaces and line breaks/returns.
FAQ article:
Added FAQ article to my response:
- Go to Admin > System Configuration > Frontend::RichText and de-activate it. (Don't forget to deploy)
- Create any new FAQ article. For testing purposes, use line breaks.
- Go to any ticket and reply to any article (select any response template)
- Click on "FAQ" in between subject and text to select an FAQ article to put into your reply.
- After selecting it, it is put into your response. See the missing empty spaces between the field name (Symptom, Problem, Solution) and your entered text. Also see that your line breaks are missing - this might be a different issue, as it is also only visible in AgentFAQEdit, but not in the AgentFAQZoom.
- Dominant language
- Perl
- Stars
- 0
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from RotherOSS/FAQ
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
tidy code
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
bug good first issue
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
1.severity: security
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
api7/lua-resty-saml#63 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100