this is my setup:
I created one dropdown (D1) with fixed options. Choosing one option reloads a second dropdown (D2), with options from a read-data-event (up to 800 options). Choosing one option in D2 reloads a radio button with options from a read-data-event (4-10 options) based on D2. I did this, like it was in the demo.
Everything works, but each time i change the option in D2, it takes longer and longer to refresh the radio button and after 4 changes my browser crashes. I found that the querys, one can find in the browser analysis tab (firefox), getting more and more each time i change D2.
Did i messed up some configuration or are 800 options simply too much? I would accept a bit more loading time, but i dont get, why the querys are stacking up.
Do you have the latest update 6.0.12 installed ?
If your main question got answered then please mark the answer using the button!
yes, 6.0.12 is installed.
PS: I also encountered the fact, that when I use a fieldset area inside a repeater area, the fieldset doesn't get the right key per iteration. It seems to get only the last key/last data item of the data array. Shall i open a new topic for that or did you know about that already?
I alternated the setup to a textfield with an "on: change" event reloading a radios group (some usability reasons). In the reload_radio_group event in the setup I placed custom php with my query code, returning an array which is used by the radios group.
Same problem here. More and more queries are send by the browser until it crashes. (queryresults are now much smaller).
This was a bug but has been fixed in the newest update 6.0.13, did you apply it ?
Seems fine now. Thanks for the help!
2CheckOut.com Inc. (Ohio, USA) is an authorized retailer for goods and services provided by ChronoEngine.com