Are compound elements editable?

[jbuck79]

Hi, hope someone reads this. I'm looking at the Compound Elements feature and it's really intriguing, but I'm not sure I'm understanding something correctly. The Module.txt says that the sub-elements are editable. Does that mean that they are editable when creating the element, or they can be edited when adding them to a layout? If it's the latter, it doesn't work for me.

I'd like to be able to, for a simple example, make a compound element with two HTML elements. Then when I drag that to my Page's layout, be able to edit the HTML in those elements. That's not possible, right? If it is, is there a trick to get it working?

Thanks for making this module, it has some cool stuff.

[aipetryakov]

Hi.

Compound elements are definitely editable after you put it to layout.
This functionality had been broken after some changes in Orchard.Layout module.
But now I fix it. It works for 1.10.2. I have not tried it on other versions.

Compound element allow you two type of editing:

1. If you put empty container to compound element, example canvas element, then you can fill that container when you use compound element.
2. If you put plain element (not container) to compound element, example HTML, then you can change the content of it HTML element when you use compound element.

So, your use case with two HTML elements should be work now. But i also suggest you to consider Snippet Fields, that covers some functionality of Compound Element. (https://www.youtube.com/watch?v=hvVukPqg2kY&index=5&list=PLpCsCyd254FpFB-O4mW6q8z0lEqwdIuXa - from min 22, i just watch it by myself right now :)

[jbuck79]

Thank you so much for taking a look at this!

After using it for a few days, it seems to be working pretty well. We are having an issue with it though. When you drag a compound element onto the layout, you just get a blank element. In order to see and edit the compound element, you need to save the content item and then refresh the page. Is there anything we can do to fix that? I've tried it on both 1.10.1 and 1.10.2 and both versions have the same issue (it actually seems to work a little better on 1.10.1).