Feeling Lucky
?
[#38423] - Add new trigger for custom fields to manage the form before display in the backend
- Closed
- 8 Aug 2022
- Medium
- Build: 4.2-dev
- # 38423
- Diff
- roland-d:feature/custom-field-show-default-value
User tests: Successful: Unsuccessful:
Pull Request for Issue #38244
Summary of Changes
The new menuitem field cannot use nor has any use for the Default value field. Since there is no switch we can use to set this field a new plugin trigger has been added with the name onCustomFieldsPreprocessForm which can be picked up by the custom fields plugins.
Using this new trigger we can remove the Default value from the form and the mentioned error will not happen.
Testing Instructions
- Create a new custom field for Articles of the type
List of Menu Items - Set a default value as
abc - Save the custom field
- Edit or create a new article
- The page won't load the article edit form but will show an error on the page.
- Apply this pull request
- Reload the page or restart from step 4
- The page loads as expected and you can edit/create the article
Actual 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 onCustomFieldsPreprocessForm needs to be documented.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_fields Front End Plugins |
| Status | Pending | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-08-08 19:13:56 |
| Closed_By | ⇒ | roland-d | |
| Labels |
Added:
?
|
||