[MGNLMAIL-44] Mailing system does not work with Pages Created: 11/Aug/10  Updated: 03/Nov/15  Resolved: 03/Nov/15

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

Type: Bug Priority: Major
Reporter: Benoit Segaert Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

I tried to use the mailing system integrated in Magnolia.
From the Tools->Mail, "Text message configuration" is working fine.
But if I tried to use "Html page configuration" with one of my pages on my site, I received the following message:
Error: Error on line 137: The entity name must immediately follow the '&' in the entity reference.
In the debug logs, we have :
INFO info.magnolia.module.mail.templates.MgnlEmail 10.08.2010 17:31:36 - Retrieving content from magnolia:http://localhost:8080/magnoliaAuthor/wsextranet/global/error405
INFO info.magnolia.module.mail.templates.MgnlEmail 10.08.2010 17:31:36 - Creating http client for user:superuser
INFO info.magnolia.module.mail.templates.MgnlEmail 10.08.2010 17:31:36 - Filtering images
ERROR info.magnolia.module.mail.commands.MailCommand 10.08.2010 17:31:36 - Could not send email:Error on line 137: The entity name must immediately follow the '&' in the entity reference.

But the site is not configured to http://localhost:8080.
The defaultBaseUrl=https://extranets.worldsteel.org

It seems that the defaultBaseUrl is not used.
For more info, cf; http://jira.magnolia-cms.com/browse/SUPPORT-686



 Comments   
Comment by Michael Mühlebach [ 03/Nov/15 ]

Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
Given that the this issue has seen no attention for quite a while and belongs to an outdated version, we're not going to address this issue any more. Instead we will focus on issues with a higher impact and more votes.
Under the assumption this issue is together with it's associated version no longer relevant, I'm going to close it to set expectations so the issue doesn't stay open for ages with no updates. If it is still relevant please feel free to open a new issue in the appropriate project.

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