Accessing container path in classic UI dialog listener. | Community
Skip to main content
A
aembee
Level 3
May 25, 2020
Solved

Accessing container path in classic UI dialog listener.

  • May 25, 2020
  • 6 replies
  • 7653 views

Hi,

 

I have classic UI dialog with xtype selection and selectionchanged listeners. container, box and value parameters are passed to the listener.

When I try to get the container path using container.path, I get value undefined but I'm able to get the path value using dialog.path.
In the same dialog. I have xtype multifield and I'm able to get the path using container.path.

Is there any documentation on how many such out of the box parameters are available for listeners? 

Thanks in advance!

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 Ravi_Pampana

Hi

 

You can find the extjs listeners/events in below link

 

https://docs.sencha.com/extjs/6.2.0/modern/Ext.field.Select.html

6 replies

Ravi_Pampana
Community Advisor
Ravi_PampanaCommunity AdvisorAccepted solution
Community Advisor
May 25, 2020

Hi

 

You can find the extjs listeners/events in below link

 

https://docs.sencha.com/extjs/6.2.0/modern/Ext.field.Select.html

    A
    Adobe Employee
    aemmarc2Adobe Employee
    Adobe Employee
    May 25, 2020

    You should probably move away from ExtJS use in AEM. It's been in a deprecated state for several years / major releases.

      A
      aembeeAuthor
      Level 3
      May 25, 2020
      Agreed, but the project is already using it.
      VeenaVikraman
      Community Advisor
      VeenaVikramanCommunity Advisor
      Community Advisor
      May 25, 2020

      @aembee What version of AEM are you using ? agree with @aemmarc2 . Unless you are using any version which doesn't support Touch UI ( I don't think that should be the case as most of the older version prior to 6.3 should be out of support now ) 

      A
      aembeeAuthor
      Level 3
      May 25, 2020
      @veenavikraman, I'm using AEM 6.4 but components are built using classic UI
      VeenaVikraman
      Community Advisor
      VeenaVikramanCommunity Advisor
      Community Advisor
      May 25, 2020
      I am sorry prachiz. I have been out of touch with xtypes and classic UI for almost 3+ years. Hope some other community members can get you an answer
      VeenaVikraman
      Community Advisor
      VeenaVikramanCommunity Advisor
      Community Advisor
      May 25, 2020

      @aembee Apologies 😐. I couldn't be of much help here. as I mentioned din reply its been quite a long time I am out of touch with xtypes and classic UI . Hope you get help soon. 

       

      Also a recommendation, put a note to your architects or business leads to get the dialog converted to Touch UI. If you are using HTL with Sling models , then you might not have much work to do there , but else if your code is also in JSP, then you might have a bit more work, but trust me it is worth the effort ✌ 

      A
      aembeeAuthor
      Level 3
      May 25, 2020

      @veenavikraman, Thanks for the guidance 🙂
      Actually, we are using JSP with classic UI. 

      Terms & ConditionsAccessibility statement

      Loading footer...