Thank you all!

Is there any way to move an activity from one workspace (default workspace) to another (custom) workspace?

Hi preethamk69474858.My issues were related with some overlays of original CQ 5.6.1 components, in /libs/foundation/components/*. With foundation/components/page, exactly. These overlays didn't work with newest versions of AEM 6.4.Once deleted these overlays, we started to be able to edit the compon...

I'm sorry. The example package from official documentation works fine on fresh AEM 6.4 installation. I was installing on a new AEM 6.4 installation, but with other project deployed on it, and it seems this project is interfering with standard AEM functionality.I'll investigate further. Thank you all...

Hi Ankur!We don't have any errors on loading the page. But we've an error when clicking in the parsys 'Drag components here' container. The console error is:http://localhost:4502/mnt/overlay/wcm/core/content/editor/_jcr_content/content/items/content/content/items/styleselector.form.html/content/mywe...

Thank you Scott. What about the article [1] in the official AEM 6.4 documentation? In this example, there's only a foundation/components/parsys, and it doesn't work. Even with a simple text or title component.I'm going to open a Support Ticket. Thanks.[1] Create a Fully-Featured Website (JSP)

Hi Ratna.Thanks for your response, but it doesn't help. Obviously, unless they are deprecated, components should work. But they don't.Of course, the original components were developed as JSP components, as HTL-Sightly was not available with CQ 5.6.1. We don't need to create new HTL components, we ne...

Hi!I've reviewed this official AEM 6.4 documentation page:Create a Fully-Featured Website (JSP)I've downloaded and installed the package from this page (website-1_0.zip), and I've the same issue. It doesn't work. You can configure in design mode the components available in a parsys, but you can't ad...

Hi Masters!I’m working with templates and components developed originally in CQ 5.6.1, but now deployed on an AEM 6.4 instance.Basically, my templates are static templates with some typical <cq:include path="par" resourceType="foundation/components/parsys"/>. I know the components need the new Touch...

The problem was related to the use of oak:Unstructured nodes, which are not ordered nodes. I changed it to nt:unstructured nodes and the problem was solved.Thank you very much!