Repeatable Fields

[adrian]

Thanks Ryan - sounds like you are on it

Yeah, I figured they weren't a replacement for pages when dealing with lots of entries. Definitely a great option to have in the arsenal though and I think they will be much friendlier for the client with those couple of enhancements.

[pwusr]

I am receiving this error when I add a new page (clicking on pages) & also click AddItem to add more repeater items.

Error    Maximum function nesting level of '100' reached, aborting! (line 95 of D:\wamp\www\pwabc\processwire\wire\core\Data.php)

I have a repeater field with two repeater fields : one a text type and second one, page(array) type.
I have set Ready to Edit Repeater Items as 0.
Using Processwire version - ProcessWire-2.2.9-9

Kindly tell me what might have caused this error.
Thanks a lot.

[Soma]

Repeater shouldn't be excessively used and nested. It's not built for that use and will likely cause some problems. I thougth Ryan decided to put a restriction already to prevent nested repeaters. Anyhow there seems to be a function going nested wild and is limited per some setting on server or php I think.

[WillyC]

[quotamos]Error    Maximum function nesting level of '100' reached, aborting! (line 95 of D:\wamp\www\pwabc\processwire\wire\core\Data.php) [/quotamos]

u. turnn off xdebug

  or. you like turn up xdebug nest leval

[pwusr]

Thank you for your replies.

But I removed the repeater field and created the field again with just 2 fields (one a text type and second one, page(array) type) as before.

I have added just one repeater item in the page.

And, I am getting this error again.

[ryan]

WillyC is right, you need to increase your nesting level in xdebug, or disable xdebug.

ini_set('xdebug.max_nesting_level', $limit)

[KentBrockman]

Hey there,

PW is great and so are repeaters.

But i am bothered by great amounts of items in a repeater-field. So much to scroll...

Is it possible to change the settings in a way that when a page is loaded in the manager, the repeater-field itself is visible, but the populated items in it are collapsed by default?

Thank you for your support.

[diogo]

You can define that option on the fields themselves. Go to input -> visibility, and choose "always collapsed". If it works on templates, it must work inside repeaters...

But in my opinion, if you feel that need, you shouldn't be using repeaters. Repeaters are supposed to make your life easier and spare you from some clicks, not the opposite. If what you describe is happening, I would say, use normal pages instead.

[KentBrockman]

diogo, thank you for your reply.

Perhaps my description was bad. Repeaters fit perfect for the needs of the project and the costumers are in love with it, because they understand it in a second.
In my point of view, there is no need to use pages. It's just a little bit of cosmetics to the usability in the admin.

Your suggested solution doesn't work, because in case of "allways collapsed" the whole "repeater" is collapsed.
I just want to collapse the items (not the fields) inside by default.

Any further suggestions?

Thanks.

[diogo]

I didn't mean to do it on the repeater field settings, but on the settings of each of the fields that are inside the repeater. I will try it.

edit: it seems to work:

[KentBrockman]

Yeah, i got your point, but then you just collapse the fields inside every item.
The item itself stays open.

[diogo]

Ah, ok! I got it now

[diogo]

Quick and dirty solution would be to had this line to your admin-theme:

$(".Inputfield_repeater .ui-sortable > li").addClass("InputfieldStateCollapsed");

you could add it in the end of the main.js file for instance

$(document).ready(function() {
    ProcessWireAdminTheme.init();

    // very dirty hack to collapse the repeaters, make something nicer later
    $(".Inputfield_repeater .ui-sortable > li").addClass("InputfieldStateCollapsed");
}); 

[ryan]

We'll be adding more configurability to repeaters in the next version or so, including an option to have them collapsed by default (the repeater items themselves), ability to control labels of repeater items, and automatic sorting. 

[KentBrockman]

Quick and dirty solution would be to had this line to your admin-theme:

$(".Inputfield_repeater .ui-sortable > li").addClass("InputfieldStateCollapsed");

you could add it in the end of the main.js file for instance

$(document).ready(function() {
    ProcessWireAdminTheme.init();

    // very dirty hack to collapse the repeaters, make something nicer later
    $(".Inputfield_repeater .ui-sortable > li").addClass("InputfieldStateCollapsed");
}); 

diogo,

thank you for your quick and dirty solution.

Does it work in your projects? Here the "repeaters" still stay open.

Ryan, that's really good news! We are looking forward to the next version (or so)

[n0sleeves]

Where's the download buttom for this Module? I don't see it. Nevermind. It's installed by default, just not enabled. I'm an idiot..Please ignore

[fenton]

hi everyone,

is there a way to only allow 1 image per repeater field (repeater with input type image) to be uploaded. I guess it could be confusing for an user to have the option to upload several pictures for the same repeater item:

thanks a lot, cheers, j

[MadeMyDay]

Hey Kunane, nice to see you here ;-)

Just define "Maximum files allowed" as 1 in the image field (tab "details") that you use for the repeater item. 

[fenton]

hey Marc! thanks

oh, of course, I'm an idiot (no sleep).

[wishbone]

couldn't we have the option to sort repeater items manually??

[kongondo]

couldn't we have the option to sort repeater items manually??

Not sure what you mean. I thought this was already possible via drag and drop on a page by page basis (pages with repeater fields..Works for me..

[wishbone]

I don't understand "page by page basis"... I want to move repeater items to change the order, as with pages...

btw, how do I upload an image here?

[kongondo]

Sorry. I thought you meant changing the order of repeater fields within a page....

Repeaters are pages as well (check under Admin if unsure about this). I have just checked and I can manually change the order of repeater pages via PW drag-and-drop (move). They stick to their positions in the tree. However, for some reason, the order is not being respected when outputting the repeaters, even when I specify sort=sort in my selector. I must be doing something weird (or need right settings in my template) since other sort options are working, e.g. sort=title. Don't have time to test right now but you can try and see how it goes..

Edit:

strike through...

[Soma]

You can already sort the repeater items manually with drag and drop.

[kongondo]

You can already sort the repeater items manually with drag and drop.

Soma, isn't that what I just said above hehe.