Add new trigger for custom fields to manage the form before display in the backend#38423
Closed
roland-d wants to merge 1 commit intojoomla:4.2-devfrom
Closed
Add new trigger for custom fields to manage the form before display in the backend#38423roland-d wants to merge 1 commit intojoomla:4.2-devfrom
roland-d wants to merge 1 commit intojoomla:4.2-devfrom
Conversation
…n the backend Hide the default field for the menuitem custom field Signed-off-by: Roland Dalmulder <contact@rolandd.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Pull Request for Issue #38244
Summary of Changes
The new
menuitemfield cannot use nor has any use for theDefault valuefield. Since there is no switch we can use to set this field a new plugin trigger has been added with the nameonCustomFieldsPreprocessFormwhich can be picked up by the custom fields plugins.Using this new trigger we can remove the
Default valuefrom the form and the mentioned error will not happen.Testing Instructions
List of Menu ItemsabcActual result BEFORE applying this Pull Request
Page crashed with a fatal error
Expected result AFTER applying this Pull Request
The content editing page loads as expected an article can be edited/created.
Documentation Changes Required
Yes, plugin trigger
onCustomFieldsPreprocessFormneeds to be documented.