Скачать или смотреть How to Properly Map an ObjectStorage Domain Property in TYPO3 Fluid Forms

Learn how to correctly map a domain property of type `ObjectStorage` in TYPO3 Fluid forms to avoid common errors and exceptions in Extbase.
---
This video is based on the question https://stackoverflow.com/q/63056198/ asked by the user 'denis' ( https://stackoverflow.com/u/391216/ ) and on the answer https://stackoverflow.com/a/63160245/ provided by the user 'denis' ( https://stackoverflow.com/u/391216/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: TYPO3: How to get a domain property field with type ObjectStorage SomeSubType mapped from a fluid form in extbase?

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Understanding the Issue in TYPO3

When working with TYPO3 and Extbase, developers often encounter challenges with domain properties, particularly those of type ObjectStorage. This type is essential for managing collections of related objects, but it can be tricky to set up correctly, especially when it comes to Fluid forms. A common error arises when trying to map a property from a form input to an ObjectStorage field in a domain object, leading to frustrating exceptions and confusion.

In this guide, we will unravel how to correctly configure an ObjectStorage property in TYPO3 10LTS, so you can ensure your form data is mapped properly without encountering exceptions.

The Setup

The Domain Model

Let's assume you have a domain model with a property defined as follows:

[[See Video to Reveal this Text or Code Snippet]]

Here, companyEmployees is an ObjectStorage that will hold instances of the Employee class.

The Fluid Template

In your Fluid template, you might have a field to gather input for the firstName of an Employee:

[[See Video to Reveal this Text or Code Snippet]]

The intention here is that when the form is submitted, TYPO3 should automatically populate the ObjectStorage with an Employee instance filled with the provided firstName.

Identifying the Problem

Upon submitting the form, it's common to encounter the following exception:

[[See Video to Reveal this Text or Code Snippet]]

This error suggests that TYPO3 was unable to determine the correct type for the child property of companyEmployees, which is critical for mapping the input data to the object model.

The Solution

To resolve this issue, we need to ensure that TYPO3's object mapper can accurately derive the type from the property. Here’s how to properly set up your setter method to avoid these kinds of exceptions.

Step 1: Correctly Define the Setter Method

You need to implement the setter method for companyEmployees. Here's the correct way to do that:

[[See Video to Reveal this Text or Code Snippet]]

Important Points to Remember

Fully Qualified Names (FQN): You must use the FQN in the PHPDoc @ param notation. This is crucial in Extbase, especially for TYPO3 10LTS, even if it isn’t needed in other areas.

Omit Parameter Type: Notice that we don’t specify the type of the parameter in the function signature. Using ObjectStorage $companyEmployees would lead to issues because PHP does not support subtypes. Instead, you should declare it as:

[[See Video to Reveal this Text or Code Snippet]]

Why This Works

By omitting the type declaration for the parameter, you allow Extbase to default to using the @ param annotation to determine the correct type. This approach eliminates the confusion that can arise from mismatched type expectations and integrates smoothly with TYPO3’s object mapper.

Conclusion

By following the steps outlined above, you can successfully map an ObjectStorage domain property in TYPO3 Fluid forms without encountering type-related exceptions. Ensure that your setter methods are correctly defined with the appropriate PHPDoc annotations, and you’ll be well on your way to managing collections of objects efficiently in your TYPO3 application.

Remember, the devil is often in the details, especially when dealing with complex structures like ObjectStorage. Implement these best practices, and you can save yourself from hours of debugging and frustration in the future!