since ‎09-11-2018
‎10-12-2019
abhisheks144250
Level 2
Re: Dam Overlay issue in AEM 6.4 abhisheks144250 - Adobe Experience Manager
Update:/libs/dam/content/schemaeditors/forms/default/itemsto/conf/dam/content/schemaeditors/forms/customName/itemsnot apps
2368
Views
0
Likes
0
Replies
Request URI too Large (414 Error) with foundation-wizard-control-src abhisheks144250 - Adobe Experience Manager
Hi,i am getting request URI too large error. My data(attaching on clicking next) has increased in recent times. But we are not using ajax call through JS or something that sort.The general solution for 414 is changing GET to POST as i googled.But i am not sure how to change the behaviour of foundation-wizard-control-src.We are using "foundation-wizard"( foundation-wizard — Granite UI 1.0 documentation )AEM version: 6.4
427
Views
0
Likes
1
Answers and Comments
Re: Dam Overlay issue in AEM 6.4 abhisheks144250 - Adobe Experience Manager
It helped. thanks
2368
Views
0
Likes
0
Replies
Re: Dam Overlay issue in AEM 6.4 abhisheks144250 - Adobe Experience Manager
/libs/dam/content/schemaeditors/forms/default/itemsto/apps/dam/content/schemaeditors/forms/customName/items
2368
Views
0
Likes
1
Replies
Dam Overlay issue in AEM 6.4 abhisheks144250 - Adobe Experience Manager
Hi Everyone,trying to overlay in AEM6.4(Migration project from 6.1):/libs/dam/content/schemaeditors/forms/default/itemsto/libs/dam/content/schemaeditors/forms/customName/items(even if i keep default in place of customName) it doesn't works.Its working fine in 6.1.Objective:Assets.html->Select an asset->properties.Here we want to add a custom field.But its not happening, even if i kept whole hierarchy directly in /apps it still takes from libs.other overlays are working fine(except dam).
2597
Views
1
Like
4
Replies
Re: AEM 6.4 UserManager userManager = userManagerFactory.createUserManager(session); abhisheks144250 - Adobe Experience Manager
Use:import org.apache.jackrabbit.api.security.user.UserManager;
1643
Views
0
Likes
0
Replies
Dialog validation not working in 6.4 abhisheks144250 - Adobe Experience Manager
Having issue with validating dialog fields(in 6.4).Same is working in AEM 6.1.2 fields are there, One dropdown and one is textbox. Both should be mandatory.My select box resource type is: granite/ui/components/foundation/form/select1)else if ($(checkField).hasClass("coral-Select")) { inputField = $(checkField).find("select option:selected"); var inputFieldPatent = $(inputField).parent(); inputFieldPatent.checkValidity(); inputFieldPatent.updateErrorUI(); } 2)I tried with: var api = $(dropdownVal...
1147
Views
0
Likes
3
Answers and Comments
Re: How to save a JSON property in multifield in JSON rather than in Nodes abhisheks144250 - Adobe Experience Manager
Thats correct, but we are migrating from 6.1 to 6.4. This will require a lot of code change i guess in the project i am working.
1828
Views
0
Likes
1
Replies
How to save a JSON property in multifield in JSON rather than in Nodes abhisheks144250 - Adobe Experience Manager
Hi,I have a multifield in AEM 6.4(referring granite/ui/components/coral/foundation/form/multifield).I want to save a JSON property as "Items" : {"language":"/content/languages/english","textText":"temp","emptytext":"jkjkjkjk"}By default in aem 6.4 its storing these as nodes, which will lead me to a code change at many places.Any way round there so that it still stores in JSON format instead of nodes.Note: already tried acs-commons-nested="JSON_STORE" but not working in 6.4.acs-commons-nested="JS...
2252
Views
0
Likes
4
Replies
AEM 6.4 UserManager userManager = userManagerFactory.createUserManager(session); abhisheks144250 - Adobe Experience Manager
Getting exception in AEM 6.4,with code as:UserManager userManager = userManagerFactory.createUserManager(session);resourceResolver = FFF.getResourceResolver(resourceResolverFactory, session);PayloadLookup payloadLookup = new PayloadLookup(item, session, userManager);Exception:com.adobe.granite.workflow.WorkflowException: java.lang.UnsupportedOperationException: No longer supported (UserManagerFactory#createUserManager(Session)).
1871
Views
0
Likes
3
Replies
Re: fieldAPI.getName is not a function abhisheks144250 - Adobe Experience Manager
1 more thing is like..my multifield is now: granite/ui/components/coral/foundation/form/multifieldbut my fileupload is: cq/gui/components/authoring/dialog/fileuploadcan this be a issue? as 1 is coral other is not?Solution?
791
Views
0
Likes
0
Answers
Re: fieldAPI.getName is not a function abhisheks144250 - Adobe Experience Manager
as soon as debugger will proceed this will give a error.
791
Views
0
Likes
0
Answers
Re: fieldAPI.getName is not a function abhisheks144250 - Adobe Experience Manager
Issue still persists...i dont have a RTF.There is a Select box(Image/video)(granite/ui/components/coral/foundation/form/select). Based on the selection,( cq/gui/components/authoring/dialog/fileupload) uploads the file. This whole set is inside a multifield(granite/ui/components/coral/foundation/form/multifield) . Have given composite property to multifield as true.shubhaga1 granite/ui/components/coral/foundation/form/multifield
869
Views
0
Likes
0
Answers
fieldAPI.getName is not a function abhisheks144250 - Adobe Experience Manager
Same dialog with ACS commons works in 6.1, but when i am referring my multifield to coral/foundation in 6.4 which has "image select" and trying to save this error is coming.
2356
Views
0
Likes
7
Answers and Comments
Likes given to
Likes from