Message board email updates incorrectly display signature when post is added from Admin > Content > Message Boards

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 6.2.10 EE GA1, 6.2.X EE
• Fix Version/s: 6.2.4 CE GA5, 6.2.X EE
• Component/s: Collaboration, Message Boards
• Labels:
  • liferay-fixpack-portal-62-6210
• Branch Version/s:
  6.2.x
• Backported to Branch:
  Committed
• Story Points: 6
• Fix Priority: 2
• Git Pull Request: https://github.com/hhuijser/liferay-portal-ee/pull/2466

Description

When email updates for message board threads are enabled, the email signature will properly display when a post is added from the portlet. However, regardless of the portlet's configuration, when a post is added from Admin > Content > Message Boards the email signature will always appear as:

[$COMPANY_NAME$] Message Boards
[$MESSAGE_URL$]

[$PORTAL_URL$]

For example:

Liferay Message Boards
http://localhost:8080/web/guest/home/-/message_boards/view_message/24915

http://localhost

Steps to reproduce

1. Add message board portlet.
2. Enable email thread updates for message boards.
3. Change the default message signature (in Message Added Email and Message Updated Email) to anything else, such as [$FROM_NAME$].
4. Add a new thread and subscribe to it, using a valid email account to check emails.
5. Post a message from the portlet. The email update displays the signature as configured in Step 3.
6. Post a message from Admin > Content > Message Boards. The email update displays the signature with the values for:
   [$COMPANY_NAME$] Message Boards
   [$MESSAGE_URL$]
   [$PORTAL_URL$]

Results of Testing

Expected Result: Whether a post is added from the portlet or Admin > Content > Message Boards, the email update's signature should correspond to the portlet's configuration.
Actual Results: When a post is added from Admin > Content > Message Boards, regardless of the actual signature's configuration the signature only contains:
[$COMPANY_NAME$] Message Boards
[$MESSAGE_URL$]

[$PORTAL_URL$]

NOTE:
Issue is fixed in Master by LPS-43575 which cannot be back ported.
This LPS is to track the unique fix to 6.2.x