Dropzone Elements not showing up

[Beblebroks (Nicolas)]

Hi,

when using a dev-pack component. The Elements thrown inside the one of the Dropzones (as seen in the screenshot) do not showing up. This component has 2 dropzones.

The Tooltip Dropzone is part of a template, which is used twice but within a if - else, so the code does not to be written twice. In the edit mode I am able to hide the tooltip (small red icon). So I am using the template in edit = true + hide = false and edit = true

[ben]

very hard to tell what is going on here from the info/screenshots.

Does this happen in both a Custom Component and Dev Pack component?

Could you post either a project with a custom component or the raw template code that has this issue, then I can take a look

[Beblebroks (Nicolas)]

Will do later.

[Beblebroks (Nicolas)]

Hi @ben,

I tested it with a local component that works. I might need to reimport and see how that goes. I will do some more test today and give you a feedback.

Did not forget it, its just a bit bigger to reproducing. In case I find the issue with the dev pack, I will send that pack via email to @dan

Thats what I was worried about:

[Beblebroks (Nicolas)]

Nevermind I got it reproduced. Its related to templates and dropzones. Same behavior in custom vs dev-pack.

elementsapp://downloadDocument/eauQlhosDHOz

[ben]

Thanks for this, I’ll take a look asap!

[logrunner (Jon)]

Hi @ben, I am running Elements 0.6.9.

I have a DevPack which has from one to three drop zones, depending on how the properties are configured. Opened the project this morning and have noticed that the DevPack node has lost all its drop zones in the Page Layout (Node tab). However the drop zones and their content are shown in the Editor.

Here is what it looks like in Elements:

[logrunner (Jon)]

HI @ben

Now running 0.7.2.

Just to clarify my post. The dropzone is shown in the node browser, it is just the anything you drop into the drop zone is not shown as a child of the dropzone. So it makes it almost impossible to move around the dropzone content.

I am using dropzones so that when a blog page is setup, the user can configure how the blog post should look, on both the list of posts and single post pages.

[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?