Avoid e-notices on pages with tabs #22892
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Avoid e-notices on pages with tabs, by ensuring tabHeader items contain the necessary keys.
Before
On pages with tabs (manage event, campaign conduce survey, etc) e-notices were frequently triggered from within
TabHeader.tpl
. These resulted fromTabHeader.tpl
trying to readtabHeader
keys from each top-level array item.After
The
tabHeader
array is re-assigned inCRM_Core_Form
andCRM_Core_Page
just before the template is rendered, with all keys defined for eachtabHeader
tab array.Technical Details
This could have been resolved by changing the arrays assigned to
tabHeader
within induvidual pages. However, this centralises the logic incase new array keys are added in future, and will ensure notices are not caused by any extensions usingTabHeader.tpl
.