Forums

I would like an explanation Hot To use Repeater Area!

Hi Austre,

Please check this:
https://www.chronoengine.com/faqs/74-chronoforms6/5290-how-to-use-the-repeater-area.html

But please note that the latest release has a bug which will stop the multiplier feature from functioning as expected, if you need a fix then please send me a message using the contact us page.

Best regards,
Max

Hello, Max, I sent you the message abut the patch but did not receive it yet. Elita

Hi Elita,

Just sent it!

Best regards,
Max

Hello, Max, thank you for the patch. Unfortunately, there are no changes😟

Hi Elita,

Please set the button color to green and remove the "Container class".

Best regards,
Max

Thanks, Max, is it possible to get the remove button too? And where can I style this?
[attachment=108190_20170529132631_form9-jpg.jpg][/attachment]

Hi Elita,

Just use class:multiply and class:remove in the button settings and that will configure them to do a multiple or remove.

Best regards,
Max

Hello, Max. Everything works like charm except the Remove buton. Any suggestions?

[attachment=108190_20170531105936_form-button-jpg.jpg][/attachment]

[attachment=108190_20170531105948_form-button1-jpg.jpg][/attachment]

Just a suggestion - how can I get Font awesome icon instead of text for that button?

E.g. <i class="fa fa-plus-square-o"></i>

Another question - How do I configure Repeater in CF6 for DB Save?

Hi Elita,

The remove button is inside the "body" of the repeater ?

You can use the semantic icons:
https://semantic-ui.com/elements/icon.html

I will update the FAQ below to describe the saving process:
https://www.chronoengine.com/faqs/74-chronoforms6/5290-how-to-use-the-repeater-area.html

Best regards,
Max

No, the remove button is in the footer. Should it be in the "body"?

It works. By placing the remove button in the "body" area it started to work.
[attachment=108190_20170601094421_form-button2-jpg.jpg][/attachment]

So. To resume:

To add the "Add" button, place the button in the Repeater Footer area, change it to Button, Add class: multiply in the Advanced Extra Attributes tab.

To add the "Remove" button, place it at the end of the Repeater Body area, change it to Button, Add class: remove in the Advanced Extra Attributes tab.

If you want to style those buttons with icons, use semantic icons with the link above. To have the icons in the center, I added code: style="display:block; margin: 0 auto;"

Dear all,
I'm trying to use a Repeater (see attachment) where I added a button with "class:multiply" and another button with "class:remove" in Advanced Extra Attributes tab, but it doesn't work.
Where I'm mistaking?

Dear hwsassisi, did you get the patch from Max? And did you enable content multiplier in Repeater area settings?

Dear elitakey,
content in repeater are setting is enabled (as you can see in my previous attached screenshot) but I didn't get any patch from Max
Please Max, could you send me the patch?
Rergards

Hi Max,
I'm trying to use the repeater area in this way. I need 10 text fields, and each one should be named "squadra[n]";

I put the repeater, and configured "Data provider" as 10; in the body I put a text field in which I set these parameters:

Label => Squadra[n] (it should be good to view the number also in the label);
name => squadra[n], ID =>squadra[n]

Actually my form gets only last data I input. Where is my mistake?
Thanks

Hello, Max.
I followed your insturctions in
https://www.chronoengine.com/faqs/74-chronoforms6/5290-how-to-use-the-repeater-area.html

Further explanation on how to Save the Repeater data is needed, especially for this sentence:

The Loop Event data provider should be set to {data:Model} which is the paremt of the cloned items data sets, and the "Save data" daat provider should be set to {var:switch_action_name.row}, the "Save data" should be inside the "Body" section of the "Loop event" action.


1. How to set the DataBase for the Repeater? Should it be the separate database?
2. If Yes, how to connect the record from the main DB with that of the Repeater records for further reading? Should it be the special ID for that or what?
I mean - if, e.g there will be 3 Repeater records in the Repeater DB, for one record of Main Data base, how the data later could be retrieved for that record? Example - Main DB contain Record for one person that entered the infomation about domestic animals they have and Repeater DB has 3 records of cats names. How can I later know that this person entered those cats names?🙂
3. Did not understand this: {data:Model} and that {var:switch_action_name.row} - how can I adjust this to my situation. If I understand corectly, Model is that i put in the Field name (Model[n][field_name]). How to interpret this: {var:switch_action_name.row}?

Hi,

I used to like the old ChronoformsV5 repeat area. Simple to understand and to follow, it worked first time I ever used it.

The new one in V6 is as clear as mud and has taken me an hour to work out there is a bug. Please can I have the patch.

Can I suggest the following:

1. That someone writes a much clearer explanation of the way it works, step by step with illustrations
2. A second explanation on how to set arrays (where to do it and how these work)
3. A third section on how to set up the database to receive the information (if this is required)
4. A tutorial video - using these step by step examples
5. An example multiplier form so that people can look at one that works and take the details away.

Meantime,can I please have the patch, so I can wrestle with the next section.

Please, please, please can someone help with tutorials and examples for ChronoformsV6.


Richard

Hi,
I need the path too
regards

Hi,

I'm trying to have some illustrations done soon, so hopefully they will be ready in the next week or two.

Please send me a message using the Contact us page to get the patch file.

Best regards,
Max

Hello, Max, how is going with the promised explanations on how to set the arrays and DB in CFv6 Multiplier? World is waiting for it...

Hi Elita,

Hopefully this will be ready in the next day or two, I'm working on it.

Best regards,
Max