How do you export a design dialog xml file after performing a conversion? | Community
Skip to main content
Level 3
Mar 17, 2018 3:40 AM UTC
Solved

How do you export a design dialog xml file after performing a conversion?

I just used the Dialog Conversion Tool to convert a design dialog from Classic to Touch UI as part of a 6.1 to 6.3 upgrade. Now I need to export the proper XML or folder structure to add that to the codebase. What's the proper way to do that? This is where I'm running into trouble. I've tried using VLT following instructions here, but this creates multiple folders and it doesn't work when I build the code to try and have it re-added to the datastore. I've tried navigating to the path of this component.xml and the file that comes back also doesn't work. What am I doing wrong? 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Ratna_Kumar
Ratna_KumarAccepted solution
Level 10
Mar 19, 2018 4:09 AM UTC

Hi,

I understand your question. Once you converted dialog from Classic UI to Touch UI, you can export the XML from eclipse using export option - For this you need to install AEM plugin in eclipse.

See this thread for more information: AEM 6.3 - Maven build is successful but still doesn't install content

Also, please look into this WKND article: Getting Started with AEM Sites Part 2 - Creating a Base Page and Template

Hope this helps!!

~Ratna.

7 replies

Level 3
Mar 20, 2018 4:55 PM UTC

So I used "repo get" and it returns a bunch of nodes, but they still don't work. In fairness the converted version of this didn't work anyway. Even before export. I suppose I have to look for a new method to convert the design dialogue.          

Translate
smacdonald2008
Level 10
Mar 19, 2018 5:42 PM UTC

As shown in that article - you can use the Eclipse tool to get the code into a source repo.

Translate
Level 3
Mar 19, 2018 5:40 PM UTC

So this can't be done with anything other than Eclipse? The folks on StackOverflow seemed to believe that VLT should do the trick, but I saw the same thing you did, smacdonald2008​. I saw a bunch of nodes and therefore nothing I could use in code.

Translate
smacdonald2008
Level 10
Mar 19, 2018 2:03 PM UTC

Ratna is correct too - the conversion tool simply converts the dialog. It has nothing to so with getting your dialog into a code repository. See Commit Content Root to Source Control (Optional) in the 2nd link Ratna provided.

Translate
Ratna_Kumar
Ratna_KumarAccepted solution
Level 10
Mar 19, 2018 4:09 AM UTC

Hi,

I understand your question. Once you converted dialog from Classic UI to Touch UI, you can export the XML from eclipse using export option - For this you need to install AEM plugin in eclipse.

See this thread for more information: AEM 6.3 - Maven build is successful but still doesn't install content

Also, please look into this WKND article: Getting Started with AEM Sites Part 2 - Creating a Base Page and Template

Hope this helps!!

~Ratna.

Translate
smacdonald2008
Level 10
Mar 18, 2018 10:53 PM UTC

I just tested this.

It converted my Classic dialog to a Touch UI dialog located here:

/apps/AEM63App/components/content/helloworld/cq:dialog

This is all the conversion tool. It does not export XML or anything like that. It converts a classic ui to touch ui dialog nodes.

Translate
smacdonald2008
Level 10
Mar 18, 2018 10:27 PM UTC

After you convert a dialog - you should have a Touch UI dialog under the component. Is that happening in your situation.

Translate