You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ofbiz.apache.org by "Mridul Pathak (Jira)" <ji...@apache.org> on 2026/09/29 16:21:00 UTC

[jira] [Closed] (OFBIZ-13623) Two missing null-guards cause NPEs instead of the clean no-op the original mini-lang produced

     [ https://issues.apache.org/jira/browse/OFBIZ-13623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mridul Pathak closed OFBIZ-13623.
---------------------------------
    Fix Version/s: Upcoming Branch
                   24.09.08
       Resolution: Fixed

> Two missing null-guards cause NPEs instead of the clean no-op the original mini-lang produced
> ---------------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-13623
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-13623
>             Project: OFBiz
>          Issue Type: Bug
>          Components: party
>    Affects Versions: Upcoming Branch, 24.09.07
>            Reporter: Mridul Pathak
>            Assignee: Mridul Pathak
>            Priority: Major
>             Fix For: Upcoming Branch, 24.09.08
>
>
> *1. {{setCommunicationEventStatus()}}* dot-accesses {{communicationEvent.statusId}} with no null-guard after {{queryOne()}}. Direct sibling of a bug already fixed elsewhere in this file for {{setCommunicationEventRoleStatus()}} (OFBIZ-13591) — that fix never got applied here.
> *2. {{sendContactUsEmailToCompany()}}* dot-accesses {{productStoreEmailSetting.bodyScreenLocation}} with no guard; {{productStoreId}}/{{emailType}} are optional attributes, so a normal unconfigured setting throws an NPE on this public, unauthenticated "Contact Us" handler, after the {{CommunicationEvent}} has already been created.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)