Dropzone Elements Not Showing Up [Continuation]

Hi @dan & @ben,

Sorry to bump this one again. :slightly_smiling_face:

New post as the forum software wouldn’t let me post another reply to the original thread. :wink:

As you would expect, I am running Elements 0.7.9 (23506).

As I haven’t had a response to my last post on the previous thread from over two weeks ago, I just wanted to check if this problem (originally reported at the end of February) is on your radar to fix. It is edging into a show-stopper area for me now!

It makes it incredibly difficult to edit components that are embedded in a dropzone when using the editor. As my Blog DevPack relies on users being able to edit their components (in a dropzone), this will make the DevPack effectively unusable for any users.

The file I sent you for this basis problem (which btw, I haven’t had any feedback on) may illustrate the issue?

Again, apologies for the new thread and for the bump. :slightly_smiling_face:

Sorry for not sorting this out. I think it got lost in all the feedback :grimacing:

The old threads are a bit hard to follow. To ensure we’re working on the correct issue, could you please summarise the exact problem you’re having and what you’d like fixed? Could you also re-post the required files to reproduce this issue?

A video demonstrating the problem would also be most helpful.

Sorry to be a bother, but I’d like to get this resolved for you as soon as possible for you!

Here is a video that demonstrates the issue. When I drag components into the dropzone, they don’t appear in the node browser but they do appear in the breadcrumb.

CleanShot 2025-04-26 at 14.23.18

I have emailed you a link to the project in Elements Cloud. :slightly_smiling_face:

I have the project but we’re going to need the Dev Component too :grimacing:

Emailed to you directly this time :slight_smile:

EDIT: Email got rejected :astonished_face:, so have uploaded it to pCloud for you - link in email.

Yup, got it, thanks for taking the time to sort it all out — Will dig in and report back next week :saluting_face:

Hey @logrunner, just to let you know this should be fixed in the next build (0.7.10), due out shortly!

1 Like

Hi @dan et al,

Thanks for fixing this; confirmed it is now fixed in V 0.7.10 (23513). :slightly_smiling_face:

1 Like