Customer FAQ related articles do not react to RichText editor changes
Nobody has claimed this yet.
- Dominant language
- Perl
- Stars
- 0
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Summary
FAQ.Customer.RelatedArticles.js registers RichText editor event handlers using old CKEditor 4 event names. The current OTOBO RichText editor uses CKEditor 5, so the handlers for key, paste, and blur are not fired.
As a result, changes in the customer RichText body do not trigger the related FAQ article refresh logic.
Affected File
var/httpd/htdocs/js/FAQ.Customer.RelatedArticles.js
Actual Behavior
When typing, pasting, or leaving the RichText editor in the customer ticket message form:
- no RichText-related
console.logoutput appears $('#Subject').trigger('change')is not executed from RichText events- related FAQ articles are not refreshed based on the updated body content
Expected Behavior
RichText editor interactions should trigger the existing FAQ related article refresh logic:
- key input should be detected
- paste should be detected
- blur/focus loss should be detected
- related FAQ articles should update when the body content changes
Technical Cause
The code uses CKEditor 4 style handlers:
CKEditorInstances['RichText'].on('key', ...)
CKEditorInstances['RichText'].on('paste', ...)
CKEditorInstances['RichText'].on('blur', ...)
But Core.UI.RichTextEditor.js creates a CKEditor 5 ClassicEditor instance. CKEditor 5 requires different event APIs
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.
Research direction
Start with var/httpd/htdocs/js/FAQ.Customer.RelatedArticles.js and inspect Core.UI.RichTextEditor.js to confirm how the CKEditor 5 ClassicEditor instance exposes change, paste, and focus-loss events. Preserve the existing $('#Subject').trigger('change') refresh path for typing, pasting, and blur. Done means the related FAQ articles refresh when the customer RichText body changes, without relying on the old CKEditor 4 event names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100