Feature #12886

Add possibility to send multiple objects (object storage) to action

Added by Simon Schaufelberger over 10 years ago. Updated about 1 year ago.

Should have
Target version:
Start date:
Due date:
% Done:


Estimated time:
PHP Version:
Sprint Focus:
Needs Decision


spoken in the case of blog_example, it is not possible to edit multiple blogs at the same time.

What i would like to do is the following:

<f:form controller="Blog" action="multipleedit" name="blog">
<input type="checkbox" value="1" name="tx_blogexample_pi1[blog][]">
<input type="checkbox" value="2" name="tx_blogexample_pi1[blog][]">
<input type="checkbox" value="3" name="tx_blogexample_pi1[blog][]">
<f:form.submit value="Edit"/>

and have an Action like this in BlogController:

public function multipleeditAction(Tx_Extbase_Persistence_ObjectStorage $blog){

Updated by Sebastian Kurfuerst about 10 years ago

  • Category set to 963
  • Target version deleted (Extbase 1.4)
  • Has patch set to No

Updated by Alexander Schnitzler over 8 years ago

  • Target version set to 1910

Updated by Alexander Schnitzler over 8 years ago

  • Status changed from New to On Hold

Updated by Anja Leichsenring over 8 years ago

  • Project changed from 534 to 2559
  • Category changed from 963 to Fluid: ViewHelpers
  • Target version deleted (1910)

Updated by Anja Leichsenring over 6 years ago

  • Status changed from On Hold to New

Updated by Alexander Opitz over 6 years ago

  • Project changed from 2559 to TYPO3 Core
  • Category changed from Fluid: ViewHelpers to Fluid

Updated by Susanne Moog almost 6 years ago

  • Sprint Focus set to PRC

Updated by Claus Due over 5 years ago

  • Status changed from New to Closed

The solution is to use a proper DTO or rely on arrays (which can still be validated), not to turn ObjectStorage into a DTO. For more flexibility, use DTO. For ease, use arrays.

Extbase can map ObjectStorages, of course, but won't do so as root controller action arguments - with good reason: ObjectStorages aren't persistable or validatable themselves - only the contained objects are. Although we could make this possible it would require adding special handling in many contexts right from argument validation to persistence - when the proper response is "use the framework's features: an unpersisted DTO or a plain array".

It sounds like what you need here is a proper DTO.

Closing as "edge case, has multiple workarounds, not indented framework usage".


Updated by Simon Schaufelberger over 5 years ago

ok, thank you for your answer. How could a DTO solution look like?


Updated by Benni Mack about 1 year ago

  • Sprint Focus changed from PRC to Needs Decision

Also available in: Atom PDF