Feature Request: Repeatable Options

[gambitph]

Feature Request: Repeatable Options

[bfintal]

I like this new Repeatable option. I'm also creating a theme now and I've just stumbled upon the need to create fields for inputting social icons for a footer. The Repeatable option would be the answer to this.

Perhaps the syntax for this can be:

$panel->createOption( array(
    'type' => 'repeatable',
    'id' => 'my_repeatable',
    'options' => array(
        array( ... ), // option parameters, like the array you pass to a createOption call,
        array( ... ), // each one is a new option in the group
        array( ... ),
    ),
) )

Then doing a getOption would give you a multi-dimensional array of the grouped values

What do you think?

I think though that we should still do #10 for simpler options that can just sort items and enable/disable items.

[ardalann]

Yeah that's exactly what I had in my mind.
We also need settings such as:
addable (bool)
removable (bool)
sortable (bool)

Yes you're right. #10 should be separate.

[MickeyKay]

Any update on this one? I'm in desperate need of some repeatable options for a plugin I'm working on in which the user needs to be able to add/remove inputs. Furthermore, they would ideally be able to add/remove groups of inputs, since each repeatable item consists of two inputs (e.g. width and height). Any ideas?

[bfintal]

Sorry Mickey, quite busy now and unfortunately can't do any Titan
development. Hopefully in 1-2 weeks I can allot some time for Titan :(

[MickeyKay]

Checking in again :) This is definitely the number one feature request on my end right now. Repeatable options and option groups is a MUST for me. I'm trying to figure out which framework to base our theme/plugin work on moving forward, and this is really the most important factor right now. Any word?

Thanks Ben!

[fa7ad]

BUMP!!
Any update on this?

[IzaacJ]

BUMP ! Update on this please. Migrating from Redux to Titan, due to some features, but missing a repeatable (that I actually made myself for redux through extentions). Might build one myself and make a pull request.

[nickkuijpers]

Bump ;( I'm using unyson.io untill this has been created..

[emilsgulbis]

Bump

One of the most critical field types. Bump.

[hellor0bot]

Would be an awesome feature. Any time to implement it?

[otjutt]

Bump

[aManNamedJed]

Bump -- this would be great!

[sasimon]

In my research, the idea that "repeat" should be an option is a misconception. When implemented as an option, it leads to requiring one or more of the field. The correct cardinality of any repeater not marked "required" is ZERO or more. The more successful repeaters are implemented as classes, for they can store their code as variables even when the length of the repeater is equal to zero.

[andrastudio]

Any update on this feature?
Would love to see this in Titan but last commit was 8 months ago.

[Sotiris-k]

Bump for this great feature.

[vladbndko]

Bump

Bump.
Currently they are busy for big... LOL