Report bug
See our new modern addons portal Completely automatic.


other versions



The best way to install Kdyby/Replicator is using Composer:

$ composer require kdyby/forms-replicator:@dev

Place the Replicator class to folder, where RobotLoader can find it and add following line to app/boostrap.php or to BasePresenter::startup().


Attaching to form

It can be used for simple things, for example list of dates

use Nette\Forms\Container;

$form->addDynamic('dates', function (Container $container) {

Or complex combinations, for example users and their addresses

$form->addDynamic('users', function (Container $user) {
        $user->addText('name', 'Name');
        $user->addText('surname', 'surbame');
        $user->addDynamic('addresses', function (Container $address) {
                $address->addText('street', 'Street');
                $address->addText('city', 'City');
                $address->addText('zip', 'Zip');
                // ...
        }, 1);
        // ...
}, 2);

There has been little misunderstanding, that when form is submitted, and new container is created, that replicator automatically adds default containers. I was not sure if this is the correct behaviour so I've added new options $forceDefault in a934a07 that won't let you have less ten default count of containers in replicator.


Handling is trivial, you just walk the values from user in cycle.

use Nette\Application\UI\Form;

public function FormSubmitted(Form $form)
    foreach ($form['users']->values as $user) { // values from replicator
        dump($user['name'] . ' ' . $user['surname']);

        foreach ($user['addresses'] as $address) { // working with values from container

Replicator is not suitable for handling file uploads. If you do not have detailed knowledge, how the forms work, and don't need Replicator's functionality specifically, consider using a “Multiple File Upload” component instead.

Editation of items

You can use names of nested containers as identificators. From the nature of form containers, you can work with the like this

public function actionEditUsers()
    $form = $this['myForm'];
    if (!$form->isSubmitted()) { # if form was not submitted
        # expects instance of model class in presenter
        $users = $this->model->findAll();
        foreach ($users as $user) {
            # fill the container with default values

And modify the handling

public function FormSubmitted(Form $form)
    foreach ($form['users']->values as $userId => $user) {
    # now we have asscesible ID of the user and associated values from the container
    // ...

Adding and removing of containers

There is an example in sandbox, where every container has button to be deleted and at the end is button for adding new one

protected function createComponentMyForm()
    $form = new Nette\Application\UI\Form;

    $removeEvent = callback($this, 'MyFormRemoveElementClicked');

    // name, factory, default count
    $users = $form->addDynamic('users', function (Container $user) use ($removeEvent) {
        // ...
        $user->addSubmit('remove', 'Remove')
            ->setValidationScope(FALSE) # disables validation
            ->onClick[] = $removeEvent;
    }, 1);

    $users->addSubmit('add', 'Add next person')
        ->onClick[] = callback($this, 'MyFormAddElementClicked');

    // ...

Handlig of add button is easy, next example is useful, when you expect that your users like to prepare more containers before they fill and submit them.

use use Nette\Forms\Controls\SubmitButton;

public function MyFormAddElementClicked(SubmitButton $button)

When you want to allow adding only one container each time, so there will be no more than one unfilled at time, you would have to check for values manualy, or with helper function.

public function MyFormAddElementClicked(SubmitButton $button)
    $users = $button->parent;

    // count how many containers were filled
    if ($users->isAllFilled()) {
        // add one container to replicator

Method Replicator::isAllFilled() checks, if the form controls are not empty. It's argument says which ones not to check.

When the user clicks for delete, the following event will be invoked

public function MyFormRemoveElementClicked(SubmitButton $button)
    // first parent is container
    // second parent is it's replicator
    $users = $button->parent->parent;
    $users->remove($button->parent, TRUE);

If I'd want to for example delete user also frm database and I have container names as idenficators, the I can read the value like this

public function MyFormRemoveElementClicked(Submi vltButton $button)
    $id = $button->parent->name;

Manual rendering

When you add a submit button to replicator, you certainly don't want to try it render as container, so for skipping them, there is a method getContainers(), that will return only existing containers.

{form myForm}
{foreach $form['users']->containers as $user}

    {$user['name']->control} {$user['name']->label}


Or with form macros

{form myForm}
{foreach $form['users']->containers as $id => $user}

    {input users-$id-name} {label users-$id-name /}