Skip to main content
DavidNg6
Level 2
February 26, 2026

AEM form core components - Uncaught TypeError: AuthorUtils.getAFWindow(...).$ is not a function

Hello,

 

Recently tried to enable AEM form core components following this guide: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/forms/adaptive-forms-core-components/enable-adaptive-forms-core-components

 

Everything ok till try to edit the template blank-af-v2. When I go to the template editor it shows the below error:

Uncaught TypeError: AuthorUtils.getAFWindow(...).$ is not a function
    at Object.getGuideContainerPath (guideCommonAuthoring.js:1339:50)
    at HTMLDocument.<anonymous> (guideTouchAuthoringEditLayer.js:1028:52)
    at HTMLDocument.fn (jquery.js:4831:18)
    at HTMLDocument.dispatch (jquery.js:5232:27)
    at elemData.handle (jquery.js:4884:28)
    at Object.trigger (jquery.js:5136:12)
    at HTMLDocument.<anonymous> (jquery.js:5866:17)
    at jQuery.each (jquery.js:371:19)
    at jQuery.fn.init.each (jquery.js:137:17)
    at jQuery.fn.init.trigger (jquery.js:5865:15)

 

I used this code to create my new project: 

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.3.1:generate \
 -D archetypeGroupId=com.adobe.aem \
 -D archetypeArtifactId=aem-project-archetype \
 -D archetypeVersion=56\
 -D appTitle="My Site TEST" \
 -D appId="mysitetest" \
 -D groupId="com.mysite" \
 -D includeDispatcherConfig="n" \
 -D includeFormsenrollment="y" \
 -D aemVersion="6.5.23"

 

Tried playing around with the page footer and header component but no luck

Any advise why this error?

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

4 replies

DavidNg6Author
Level 2
February 26, 2026

Sorry forgot to mention I’m AEM 6.5.23

Translate
VishalKa5
VishalKa5
Level 6
March 1, 2026

Hi ​@DavidNg6 ,

  • The error happens due to a JavaScript or jQuery conflict after enabling AEM Forms Core Components.

  • AEM is trying to use jQuery inside the Adaptive Forms editor, but it is either not loaded correctly or overridden.

  • Most common reason: Custom jQuery added in header/footer overriding AEM’s internal jQuery.

  • It can also be caused by client library loading issues or version mismatch (AEM, Forms add-on, archetype).

  • Check for multiple jQuery versions in the browser, remove custom jQuery, verify Forms clientlibs, clear cache, and restart AEM.

Thanks,
Vishal

Translate
    DavidNg6Author
    Level 2
    March 3, 2026

    Hi ​@VishalKa5 , thanks for the suggestions.

    Is weird because tried with a new fresh AEM local environment and new AEM project.

    Will try again with latest SP, Forms Add On and archetype.

    Translate
    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity Advisor
    Community Advisor
    March 3, 2026

    Hi ​@DavidNg6 ,

    That error almost never comes from jQuery; it comes from missing/miswired Adaptive Forms Core proxy components in your project.

    Do this:

    1. Redeploy your project (including ui.apps)
      mvn clean install -PautoInstallPackage Then check that you have: 
      /apps/mysitetest/components/adaptiveForm/...
        formcontainer
        textinput
        dateinput
        panelcontainer
        ...
    2. Verify the template uses those proxies
      Open: 
      /conf/mysitetest/settings/wcm/templates/blank-af-v2/jcr:content

      Make sure every sling:resourceType used by the template points to something that actually exists, e.g.: mysitetest/components/adaptiveForm/formcontainer
      and not to some other app (e.g. core-components-examples/... or another project) that you don’t have in /apps.

    3. Double‑check via JSON
      Open your AF page JSON: /content/forms/af/<your-form>.infinity.json
      For each sling:resourceType under mysitetest/components/adaptiveForm/..., confirm there is a matching node under /apps.
      If any are missing, create/copy those proxy components into your ui.apps module and redeploy.

    4. Restart AEM and retry template editor.

      Once all resourceTypes used by blank-af-v2 resolve to real /apps/mysitetest/... components, the AuthorUtils.getAFWindow(...).$ is not a function error disappears.

     

    Translate
    Amit Vishwakarma - Adobe Commerce Champion 2025 | 17x Adobe certified | 6x Adobe SME
    Terms & ConditionsAccessibility statement

    Loading footer...