Multifield component not working on TouchUI - AEM 6.2 SP1 | Community
Skip to main content
S
sonalik77795449
Level 3
September 18, 2017
Solved

Multifield component not working on TouchUI - AEM 6.2 SP1

  • September 18, 2017
  • 4 replies
  • 3611 views

Hi Team,

The multifield touch UI component doesnt seem to work on my local and any of our AEM instances for 6.2 SP1.

I get the following error on the console  while trying to add the field -

Uncaught RangeError: Maximum call stack size exceeded

    at instanceGenerator._addListeners (clientlib.js:187)

    at instanceGenerator._addListeners (clientlib.js:188)

    at instanceGenerator._addListeners (clientlib.js:188)

    at instanceGenerator._addListeners (clientlib.js:188)

    at instanceGenerator._addListeners (clientlib.js:188)

    at instanceGenerator._addListeners (clientlib.js:188)

    at instanceGenerator._addListeners (clientlib.js:188)

I have tried several package installations from the links below with no luck.

We have a production release due soon and would really appreciate your help on this.

Links I referred -

touch-ui-nested-multi-field-panel.zip - Google Drive

Multifield component in TouchUI dialogs - ZenGarden approach

Experiencing Adobe Experience Manager - Day CQ: AEM 6 SP2 - Touch UI Multi Field Component

touchUI-multifield throws "CUI is not defined" error

    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 kautuk_sahni

    If you are getting Uncaught RangeError: Maximum call stack size exceeded on click of Add Field button, make sure you have not added any customized Multifield.js files.

    This typically happens because 2 xtypes have the same namespace and therefore AEM tries to load both.  I've seen this with ACS Commons installed (with their multifield panel) and also a custom multifield being installed.

    Also read this comment:- Re: Custom Multifield is not working In AEM

    solution:-

    1. Install the acs-aem-common version 3.9.0

    2.LILI made the multifield working in AEM 6.3 by using

         granite/ui/components/coral/foundation/form/multifield.

         granite/ui/components/coral/foundation/form/fieldset

         granite/ui/components/coral/foundation/fixedcolumns

         granite/ui/components/coral/foundation/container

         granite/ui/components/coral/foundation/form/textfield

    ~kautuk

    4 replies

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity ManagerAccepted solution
    Community Manager
    September 19, 2017

    If you are getting Uncaught RangeError: Maximum call stack size exceeded on click of Add Field button, make sure you have not added any customized Multifield.js files.

    This typically happens because 2 xtypes have the same namespace and therefore AEM tries to load both.  I've seen this with ACS Commons installed (with their multifield panel) and also a custom multifield being installed.

    Also read this comment:- Re: Custom Multifield is not working In AEM

    solution:-

    1. Install the acs-aem-common version 3.9.0

    2.LILI made the multifield working in AEM 6.3 by using

         granite/ui/components/coral/foundation/form/multifield.

         granite/ui/components/coral/foundation/form/fieldset

         granite/ui/components/coral/foundation/fixedcolumns

         granite/ui/components/coral/foundation/container

         granite/ui/components/coral/foundation/form/textfield

    ~kautuk

    Kautuk Sahni
      Ratna_Kumar
      Ratna_Kumar
      Level 10
      September 19, 2017

      Hi,

      Yes, Kautuk is correct!!

      If you are getting Uncaught RangeError: Maximum call stack size exceeded on click of Add Field button, make sure you have not added any customized Multifield.js files.

      This has been well explained in this article: http://www.aemcq5tutorials.com/tutorials/touchui-multifield-component-using-htl/

      Hope this helps!

      Ratna.

      S
      sonalik77795449Author
      Level 3
      September 19, 2017

      Thankyou everyone for the quick response.I got the component working by uninstalling ACS commons package

        S
        srinuetta
        Level 2
        April 6, 2018

        Is  AEM 6.1  good to migrate from classic-ui to touch-ui?

        Terms & ConditionsAccessibility statement

        Loading footer...