Summary of Changes

FieldsFormServiceInterface was added in 5.1 as a sub-interface of FieldsServiceInterface because adding prepareForm() to the existing interface would have broken implementers. It carried @deprecated 5.1.0 will be removed in 7.0 and the note to move the method into FieldsServiceInterface in 7.0. This does that: prepareForm() is now declared on FieldsServiceInterface, the sub-interface is removed, the four core implementers (LegacyComponent, ContentComponent, ContactComponent, UsersComponent) implement the base interface, and FieldModel checks the base interface.

FieldsServiceTrait keeps providing the empty default prepareForm(), so a component that uses the trait, as the core ones do, needs no change beyond the interface name.

Testing Instructions

1. Code review: grep -rn FieldsFormServiceInterface libraries administrator components plugins finds nothing.
2. Apply the patch. Administrator: Content > Fields, create a field for articles; edit an article, the Fields tab shows the field; save with a value and check it on the site.
3. Administrator: Components > Contacts > Fields, create a field for contacts; edit a contact, the Fields tab shows it; save.
4. Administrator: Users > Fields, create a field for users; edit a user, the Fields tab shows it; save.
5. Administrator: Content > Fields > Options, the context lists still show Articles, Contacts and Users.
6. Turn debug on and check no PHP notice, warning or deprecation appears during steps 2 to 5.

Actual result BEFORE applying this Pull Request

Custom field forms work through FieldsFormServiceInterface.

Expected result AFTER applying this Pull Request

Custom field forms work the same through FieldsServiceInterface.

Link to documentations

• No documentation changes for guide.joomla.org needed
• Pull Request link for manual.joomla.org: joomla/Manual#720