Akanksha_Pratih

AEM 6.2 touch ui ACS Commons NODE_STORE multifield does not works as expected when there are more than 1 multi-fields and they have mandatory fields - Adobe Experience Manager

I'm trying to create a Touch UI dialog with 2 multi-fields of type "granite/ui/components/foundation/form/multifield" and ACS_Commons_Nested as NODE_STORE.The first multi-field works perfectly fine: Its has two text fields(mandatory) and a path fieldsThe second multi-field has two text fields(mandatory): this doesnt works fine, Cant save the dialog only by reordering fields: Save is disabledCant save the dialog only by deleting any of the fields: Save is disabledMandatory check does not works pr...

454

Re: Overlayed Form Start component not working after migrating from AEM 6.2 to AEM 6.4 - Adobe Experience Manager

Found the issue, this is happening due to changes in /libs/cq/ui/widgets/source/widgets/wcm/FormActionSelection.jswhere the state of calling dialog field is passed on to the rendered dialog field. "wi.setDisabled(this.disabled)"

563

Re: AEM6.4 Classic UI damadmin Issue - Adobe Experience Manager

For me its not landing to destination folder, Its landing onto DAM root folder. Somehow default behavior isn't working. I can see that in the console there is some error as below:"Uncaught RangeError: Maximum call stack size exceeded at Array.join (native) at CQ.EXT.tree.AsyncTreeNode.getpath....." in widget.js

5.8K

AEM6.4 Classic UI damadmin Issue - Adobe Experience Manager

In AEM6.4 on classic ui damadmin console if we move any image which is present in a child folder, the image is moved properly but the page refreshes and points to topmost folder in DAM. In actual, after the page refresh the control should remain in the same folder where the move was performed.Inputs plz

6.0K

Re: Overlayed Form Start component not working after migrating from AEM 6.2 to AEM 6.4 - Adobe Experience Manager

can it be related to FoundationDeprecate renderReadOnly on Granite UI form componentsUI Shell 3.0 no longer uses this optionthis I found in AEM 6.3 release notes.If yes, what can be the solution ?

565

Overlayed Form Start component not working after migrating from AEM 6.2 to AEM 6.4 - Adobe Experience Manager

Hi ExpertsWe have overlayed foundation form start component in AEM 6.2. After overlaying a few changes were done in the dialog, like the action id dropdown was disabled such that it always uses one specific value from dropdown options and the view data CTA still did work. Now after migrating to AEM 6.4, the View Data CTA is disabled and we are not able to move to bulk editor on click of the CTA.On debugging found that its disabled as the action id dropdown is disabled by us. It used to work fine...

1.0K

Re: AEM 6.1 Touch UI Component Inplace editing not working - Adobe Experience Manager

I'm able do to inpace editing for the component after using OOB textimage.js file but not otherwise. Now I have another component which have number of text fields along with an image field. I want to enable inplace editing only for image. I added inplace editing node as in OOB image component. I'm able to see edit pencil and after clicking on it toolbar to edit image appears. - I'm not able to drap drop image directlyBut again its not working. - I'm able to rotate the image also, but after the i...

842

AEM6.2, Make Image field mandatory in Touch UI Dialog - Adobe Experience Manager

I'm creating a component which contains a Image field as well. I have to make that field mandatory in touch ui dialog.Property required=true is working fine for textfields but not for image field. Is there any other property available to make image field mandatory in touch dialog.If not, what is the other way ? Thanks

597

Re: AEM 6.1 Touch UI Component Inplace editing - Adobe Experience Manager

Hi HemantInplace editing is working for text but not for image. When I click on "Edit(pencil)" on component toolbar, I get two options: Image and Text.If I click on "Text" option, I'm able to edit text part of component.But if I click on "Image" option, the image which is already there on my component opens as popup on left top corner of page and then I'm able to do nothing.Kindly HelpBelow is my xml:

4.2K

AEM 6.1 Touch UI Component Inplace editing not working - Adobe Experience Manager

I have created a text-image component using sightly, to be used in touch UI. Need Inplace editing functionality for the same.Added editconfig with inplaceEditing node but its not working for touch UI and working for classic UI.Compared with OOB textimage component, there I'm able to do inplace editing and one edit pencil is also visible on component toolbar. Have both dialog and cq: dialog with proper fields as well. Not able to find what is the issue with my component.Please help

1.5K

AEM 6.1 Touch UI Component Inplace editing - Adobe Experience Manager

7.4K

Re: AEM 6.1 Sightly: org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension No use provider could resolve identifier - Adobe Experience Manager

Got the solution, my class name started with lower case letter just changed it to upper case and it worked.

499

AEM 6.1 Sightly: org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension No use provider could resolve identifier - Adobe Experience Manager

Hi I'm just trying to call a simple wcmUsePojo class implementation from an aem component, but while doing so I'm getting below given error:org.apache.sling.scripting.sightly.impl.engine.extension.use.UseRuntimeExtension No use provider could resolve identifier "myClassName".The code is very simple and does not contain any complex stuff yet, still its not working. the bundle is active and the pojo class package is also available in exported packages.The code snipped is as given below: Dummy Text

867

AEM 6.1 How to change "jcr:isCheckedOut" property value from false to true - Adobe Experience Manager

HiOne of the page of our site is not editable, on checking its properties we found out that the has a property "jcr:isCheckedOut" marked as false and that's why we were not able to edit that page.I could just find that it is related to versioning. But could not figure out, how it happened and to change it back to true.Please help

4.3K

Re: Restrict Dialog Opening Conditionaly through Listener AEM6.1 - Adobe Experience Manager

If I use box.hide() and- Place the listener directly under Dialog: Error alert is shown and after that the dialog opens with all the fields shown & enabled.- Place the listener at any sub level after dialog: Error alert is shown and after that the dialog opens with no fields shown. Requirement is that the Dialog should not open at all. Can I get box.parent(dialog) and hide it ?Please suggest if there is any other solution

481

Restrict Dialog Opening Conditionaly through Listener AEM6.1 - Adobe Experience Manager

HiI have created a component with design dialog and I want this component to be editable only on base template and not on other templates. For this, I have added a listener to the dialog and in its "render" property I have written below code:function(box) { var currentPage = $('#design_basepage').val(); if(currentPage == undefined){ alert('This component can be edit in the Base page only.'); box.close(); }}In the above code "design_basepage" is a variable provided in base template. This code wor...

660