Cannot Add or Edit Components in Touch UI | Community
Skip to main content
January 12, 2023
Solved

Cannot Add or Edit Components in Touch UI

  • January 12, 2023
  • 2 replies
  • 3922 views

Seeing this issue across both development and stage on our AEM 6.5.12.0 instances, while working in Touch UI over this last week: "The issue is that periodically ALL components will have their edit options removed, just leaving the Insert and Group options." (Same issues as this thread and this thread, which had no resolutions)

 

Suddenly seeing only Copy, Group, and Convert to EFV:

 

Additionally, the add component button on any parsys has disappeared:

 

The above screenshots are from our stage environment on an administrator account. The same issue is present across other user logins. There are no obvious errors in the granite logs or the web browser console.

 

Fixes attempted without any results:

  • Reinstallation of UI (apps) packages seemed to temporarily restore some functionality sometimes? But then it would occur again very quickly.
  • Suggested Band-Aid fix from this thread to specify "cq:actions" in the cq:editConfig node across components has been unsuccessful in this case.
  • Reverted any recent changes to a git history period prior to when the issue began.
  • Traced back permissions being served to the render function for the menu options, and found the same issue as this post: "For the line starting return ns.pageInfoHelper.canModify(), I think there is some data missing in the page info json object. On my broken machine, I cannot see a permissions array."

 

Any insight/suggestions are appreciated.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by dylanmccurry

I had a similar issue just this week.  I noticed that when I edit any cq:editConfig, authoring across the entire system starts to fail.

 

The resolution I found: I had an overlay of basicpage, where I was hiding/updating the out of the box fields:

/apps/wcm/foundation/components/basicpage/v1/basicpage/tabs/...

 

 

I noticed that removing this overlay fixed the issue.  Ultimately the resolution I found was to copy everything from /libs/wcm/foundation/components/basicpage/v1/basicpage/* and then apply the changes I wanted accordingly.

 

Hope this helps.

 

 

 

2 replies

manjunathdj
January 18, 2023

@jaredatud  - Are you able see components in policies/component groups in templates?

JaredAtUDAuthor
January 18, 2023

Components appear in all sidebar lists and pre-baked template areas as they're supposed to, yes.

manjunathdj
January 19, 2023

@jaredatud  - Can you restart the server and start monitoring the error log and page console(check for any JS errors) to insight the issue first on page load.

dylanmccurryAccepted solution
February 16, 2023

I had a similar issue just this week.  I noticed that when I edit any cq:editConfig, authoring across the entire system starts to fail.

 

The resolution I found: I had an overlay of basicpage, where I was hiding/updating the out of the box fields:

/apps/wcm/foundation/components/basicpage/v1/basicpage/tabs/...

 

 

I noticed that removing this overlay fixed the issue.  Ultimately the resolution I found was to copy everything from /libs/wcm/foundation/components/basicpage/v1/basicpage/* and then apply the changes I wanted accordingly.

 

Hope this helps.

 

 

 

JaredAtUDAuthor
February 22, 2023

Going to give this a try today. You may be right on the mark, as this was something we JUST implemented a change for (hiding unwanted OOTB navigational components).

 

Will check back in a bit. Thanks!