[MGNLMAIL-99] Page content has not been processed properly when user chooses 'page' option in mail template Created: 12/Mar/19  Updated: 01/Mar/22  Resolved: 01/Mar/22

Status: Closed
Project: Magnolia Mail Module
Component/s: None
Affects Version/s: 5.5.1
Fix Version/s: 5.5.11

Type: Bug Priority: Neutral
Reporter: Viet Nguyen Assignee: Jaroslav Simak
Resolution: Fixed Votes: 0
Labels: maintenance, to-verify
Remaining Estimate: Not Specified
Time Spent: 6d
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLMAIL-93 Email can not be sent when content is... Closed
documentation
to be documented by MGNLMAIL-122 DOC: Page content has not been proces... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Documentation update required:
Yes
Sprint: Global Maintenance 4, DevX 4
Story Points: 5

 Description   

When fixing MGNLMAIL-93, we recognized that we are having some issues when user chooses to send a 'page' in email.

  • First of all, 401 and 403 error codes produced when user choose to send a 'page' email if the page is protected despite putting username and password into mail template configuration.
  • Secondly HTML Tidy empty the content returned by HTTPClient which failed the content processing in MgnlPageEmail.cleanupHtmlCode(...) function.

To support our minor version release, we decided to fix the ProtocolException and SendConfirmationEMailProcessor first in MGNLMAIL-93, also providing a link to the page within email content, then creating this ticket to follow up with the full feature described below:

The Page option means that we send the content of a page to the user. The internal process reads the page content, pastes the content in the body of the email, and sends the mail to the user.
The page itself does not need to available to the visitor. It's enough that the Magnolia internal process can access the page and get its content. You should be executing the process in a context that provides access to pages.


Generated at Mon Feb 12 06:03:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.