Skip to content

Conversation

@stefane2741
Copy link
Contributor

closes #4776

stefane2741 and others added 7 commits December 18, 2025 10:23
1: Customer Body is prepared inside AgentTicketCompose, let
   TemplateGenerator know if there is already HTML present

2: Previous handling of double escaped HTML returned by
   _Replace caused issues for properly, singly escaped
   fields like OTOBO_CUSTOMER_SUBJECT

3: My current assumption is that when TemplateGenerator
   receives IDs (TemplateID, TicketID, etc.) they are
   handled properly

TODO: AgentTicketEmailOutbound and AgentTicketForward should
      both in theory support the same templates as
      AgentTicketCompose, yet they don't run into double html
      escaping issues simply because they don't prepare the
      customer body and therefore e.g. don't display inline
      images at all
Fixed TemplateGenerator->_Replace to work when receiving $Data{Body}
populated by LayoutObject->ArticleQuote. Non-line-limited bodies are
for now limited to 2500 lines, since this is how OTOBO_CUSTOMER_COMMENT
was previously handled.

TODO: AgentTicketForward is the only one of the three modules currently
passing body from ArticleQuote as expected by TemplateGenerator, but
also only temporary right now.
Look at AgentTicket-Compose/Forward/EmailOutbound and standardize how
and where body is passed and how it is included after signature.
TODO: Check other dependents on specifically TemplateGenerator->_Replace
AgentTicketCompose/-Forward/-MailOutbound now all call ArticleQuote
first before passing Data to TemplateGenerator->Template.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants