Touch Ui behavior not allowed in classic UI project

Avatar

Avatar
Level 1
diegoeflz4887
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile

Avatar
Level 1
diegoeflz4887
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile
diegoeflz4887
Level 1

26-08-2020

Hi, everyone!

 

I am starting to work in AEM and I was required to implement experience fragments functionality on a classic UI project for migration to Touch UI. Currently, I am working with AEM 6.5, I have already created my editable templates configuration under the /conf folder as the official documentation recommends https://docs.adobe.com/content/help/en/experience-manager-65/developing/platform/templates/page-temp.... However I am facing the following problems:

 

1. None of my layout containers is displaying the option "insert component". 

Screen Shot 2020-08-26 at 9.41.12 AM.png

2. When I try to access the "Edit Template" option in Page information icon on my page editor toolbar, it does not redirect me to the corresponding editable template, I mean, nothing happens.

3. This behavior is present as well in the We-retail OOTB project of my instance that neither shows the emulator option on the page editor toolbar.

 

I am assuming that is some configuration of my project but not a clue. Thanks in advance for your attention and help!

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

645 likes

Total Posts

607 posts

Correct reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

645 likes

Total Posts

607 posts

Correct reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
BrianKasingli
MVP

26-08-2020

@diegoeflz4887,

Classic UI is deprecated, and Adobe encourages developers to create more modernised solutions via using Touch UI, HTL, and using Sling Models. 

Creating editable template has a lot of configurations if you are getting errors, be sure to check the error.log in your development environment as the logs printed will be very useful. A very good tutorial can be found here:

  1. Editable Template Lesson Part 1 - http://www.sgaemsolutions.com/2017/09/dynamic-editable-templates-in-aem-63.html
  2. Editable Template Lesson Part 2 - http://www.sgaemsolutions.com/2017/09/dynamic-editable-templates-in-aem63.html

Also, when you are utilising the AEM WCM Core Page Component V2, classic UI is not supported, https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/aem-wcm-core-components-v2....

 

 

Answers (2)

Answers (2)

Avatar

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,442 likes

Total Posts

3,318 posts

Correct reply

941 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile

Avatar
Coach
MVP
Arun_Patidar
MVP

Likes

1,442 likes

Total Posts

3,318 posts

Correct reply

941 solutions
Top badges earned
Coach
Contributor 2
Ignite 10
Give Back 700
Boost 1000
View profile
Arun_Patidar
MVP

26-08-2020

Can you try to create a test project using archetype 22 or 23 and deploy in your instance. If template editor does not work for this project as well then it seems something is wrong with your instance

https://github.com/adobe/aem-project-archetype

Avatar

Avatar
Validate 1
MVP
Theo_Pendle
MVP

Likes

238 likes

Total Posts

251 posts

Correct reply

105 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 10
Ignite 1
View profile

Avatar
Validate 1
MVP
Theo_Pendle
MVP

Likes

238 likes

Total Posts

251 posts

Correct reply

105 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 10
Ignite 1
View profile
Theo_Pendle
MVP

26-08-2020

Hi @diegoeflz4887,

Here are a couple of pointers:

  1. What does your browser console say? It sounds like you may have a JS error that is preventing certain UI elements from loading correctly. 
  2. Have you overlayed anything under /libs/wcm/foundation/components/basicpage?