RotherOSS / RotherOSS/FAQ

Without richtext: missing empty spaces (and line breaks) when adding the FAQ article to your reply

Open
#33 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Perl
Stars
0
Forks
6
PR merge metrics
No merged PRs in 30d

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:

Image

Added FAQ article to my response:

Image

  • 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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

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.

Assessment

Tech stack
perl
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.