Dropzone inside of repeatchildren breaks the repeatchildren

Wappler General Bugs
1

Wappler Version : 6.3.0
Operating System : 14.2.1 (23C71)
Server Model: Node.js
Database Type: None
Hosting Type: Local

Expected behavior

What do you think should happen?

The number of dropzones that appear should be the same as the amount of repeats in the repeatchildren

Actual behavior

What actually happens?

There are multiple dropzone instances remaining after the repeatchildren number is reduced.

How to reproduce

See the attached video for a test case showing the failing behaviour. In the test case, firstly there is a repeatchildren containing a header element, along with a dropzone element. This is followed by another repeatchildren which only contains a header element. They both use the same variable number in the repeatchildren. You will see when the number is lowered, the repeatchildren containing the dropzones, does not repeat correctly.

FYI - I have an app that uses multiple dynamic dropzones and have just found this issue. It would be great if you could put a fix in for this asap. Thank you!

2

Just out of curiosity, why do you use multiple drop zones? As each drop zone has already multiple files…?

3

It’s to do with the visuals. Each dropzone is customised for the content/type of the file which is to be dropped onto.

4

Try:

image
image2560×1392 216 KB

5

Hi Ben, thanks for your response. Apologies, I don’t think I detailed the bug specifics very well. The problem occurs when you dynamically lower the number for the repeatchildren i.e in your example, it starts at 1, you change it to 5, then if you change it back to 1 you will see that the number of dropzones is incorrect. Here’s a video of it using your example:

Screen Recording 2024-02-27 at 09.54.11

Here’s another video where I decrement the number by 1 each time. You can see the number of dropzones going wild:

Screen Recording 2024-02-27 at 09.47.50

I’m going to re-open this as a bug if that’s ok, as it’s currently breaking the current design of my latest app.

@George do you know if this is a quick one to fix? If so, might it be possible to push out a fix this week?

Thanks all,
Scott

1 Like
7

My apologies for the misinterpretation. You are right, when the number is reduced, it incorrectly adjusts the repeat containing a dropzone.

1 Like
8

Does it happen in both stable and beta channel or is this a specific beta problem?

9

Hi @patrick, I’ve switched off Beta as shown below and retested. The issue no longer happens, however the dropzone has reverted back to a standard file-picker component. So I’m assuming this means the dropzone component is a Beta component?

image

image

11

Fixed in Wappler 6.3.1

13

Hi team, I’ve attempted to test the fix but after updating Wappler I’m getting the following parsing error. It seems to be coming from the dmxAppConnect.js file update.

image
image729×162 11.7 KB

Any thoughts?

14

This has already been reported and will be fixed in a few hours:

15

That’s great. Thanks.

16

3 posts were split to a new topic: Docker compose cannot be found

17

This topic was automatically closed after 45 hours. New replies are no longer allowed.