Dropzone Elements not showing up

[logrunner (Jon)]

I have been encouraged by the forum software to create a new thread but realised there was one already!

I am quoting below some of the discussion from the other thread as I think it may throw some light on this issue?

@logrunner

The only problem (and it is a major one!) with the dropzone is that you can’t see any of the components that are in the dropzone in the Node Browser (at least for an Element DevPack that has drop zones in its properties).

Just to clarify, here is an image:

@Beblebroks

Try a restart. I had that also a few times. With a restart it was mostly solved. But I did not figure out a pattern yet.

Mainly after designing a devpack component and using it the first time.

@logrunner

Thanks for the suggestion.

Yes, this is with a DevPack development (my Alloy replacement Blog). I have done numerous restarts as it has been like this for weeks. Initially you could see nodes dropped in the dropzone but once they disappeared they never come back. Even clearing everything out of the dropzone and re-adding doesn’t show anything.

The only way I can edit the structure of contents in the dropzone, is to select the Component at the top of the breadcrumb (Container A) in the image and cut and paste it into an area outside of the dropzone, edit it and then paste it back in. I can only easily select Components in the dropzone by selecting Components in the breadcrumb. This is a workaround in development but would be unusable as a published component.

@Beblebroks

Do you have the same dropzone at more then one place? BUT seperated with @if ... @else logic? I think that could also cause it. I have seen that one before as well.

Interesting, yes I do.

I have 18 dropzones (nine unique) so each is defined twice. They are embedded in a lots of ‘@if … @else’ statements depending on whether in edit mode / properties set etc. Each dropzone will only be shown once to the user having gone through the if/else logic.

@dan / @ben Does the above help with suggesting where this bug could be?