Mayukh007

Adobe Experience Manager

Adobe Campaign Classic

Adobe Campaign Standard

Adobe Experience Platform

Adobe Analytics

Adobe Audience Manager

Adobe Target

Adobe Experience Cloud

Adobe I/O Cloud Extensibility

Adobe Advertising Cloud

Marketo

Magento

Adobe Creative Cloud

Adobe Document Cloud

Workfront, an Adobe company

since

Online

Level 3

Re: content package not getting installed using install folder in ui.apps - Adobe Experience Manager

HI, Yes, that issue got resolved by adding 2 folders under ui.apps called "install.author" and "install.publish" and copy-pasted the content package zip. When you run maven build it will install the package wither to author or author+publish. It has some limitation as well... If you need full detail and setup let me know.

Re: Unable to Run Dispatcher Flush Invalidate.cache - Adobe Experience Manager

Thank you for the suggestions jbrar and asutosh. Here is what I see/did:1. In my .any file under /allowedclients, I do have allowed PUBLISH_IP from /etc/sysconfig/httpd file and the value is correct in that file and set to my publisher ip. I have still added new rule to explicitly add published ip and restarted apache:/2{/glob "10.238.32.42"/type "allow"}still curl command does not work. 2. Also when I check the dispatcher flush agents in Author and Publisher they are also not working and giving...

Re: Unable to Run Dispatcher Flush Invalidate.cache - Adobe Experience Manager

Hi Asutosh, I dont see your post here, but I did try this as well "curl -k -H "CQ-Action: DELETE" -H "CQ-Handle:/content/abc" -H "Content-Length: 0" -H "Content-Type: application/octet-stream" https://10.xx.56.xx/dispatcher/invalidate.cache". With http I get same 403 and with https I get connection refused.

Re: Unable to Run Dispatcher Flush Invalidate.cache - Adobe Experience Manager

Hi Asutosh, This does not work even when I login to dispatcher machine and run curl command. I get same 403 error. So I think issue is actually in dispatcher permission. Also like I mentioned in my command, the domain does not exist, that might be a reason..

Re: Unable to Run Dispatcher Flush Invalidate.cache - Adobe Experience Manager

Hmm...this post does not talk about the issue I have having. i am using similar curl command for specific path which works in all other existing dispatchers, so command is good.

Re: Unable to Run Dispatcher Flush Invalidate.cache - Adobe Experience Manager

Just a point to mention, the host "My_env_host_name" is not created yet, is it giving 403 due to that..?

155

Unable to Run Dispatcher Flush Invalidate.cache - Adobe Experience Manager

HI,I am trying to run a jenkins job to flush dispatcher cache and getting below error. 403 Forbidden Forbidden You don't have permission to access /dispatcher/invalidate.cache on this server. Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request. Command I ran:curl -H "CQ-Action: Delete" -H "CQ-Handle: /content/" -H "CQ-Path: /content/" -H "Content-Length: 0" -H "Content-Type: application/octet-stream" -H "Host:My_env_host_name" http://IP...

162

Issue with Experience fragment and Templates - Adobe Experience Manager Assets

HI, I am seeing an issue in one of our newly built AEm env. We are 6.5.7.I created a template using Empty page template which have single layout container > added the path of template in my XF folder allowed path > but then when I create a XF using that template, I dont see my layout container in the XF. Any thoughts?

Re: Disable JS minification only for Author - Adobe Experience Manager

It seems some bundle restart was required which i did not require in my local. Restarting instance fixed the issue in Dev

Re: Disable JS minification only for Author - Adobe Experience Manager

Hi Vaibhavi, although it worked in my local, but I dont see that updated in our Dev env....Do we need to restart any bundle to take it into effect

Re: Disable JS minification only for Author - Adobe Experience Manager

Thank you Vaibhavi, it works perfectly.

109

Disable JS minification only for Author - Adobe Experience Manager

HI,Is there way to disable minification only or Author but not for Publisher.We installed SP7 and it has issue with component edit and the solution is to disable minification of JS. But we don't want to disable minification in publisher as it will impact performance. The Apache Granite HTML Library Manager property is present in our config "htmllibmanager.minify". So I can not manually disable minification from OSGi as next build will overwrite it as we have it set as "true" in code. I do not se...

124

Re: Hi Arun and Team, We have similar situation with token.... - Adobe Experience Manager

Thank you for the response Arun..will try your solution

Re: What role is required for a non-admin user to change... - Adobe Experience Manager

HI Suresh, The issue is actually with Touch UI. In Touch UI when user clicks on Change password button, I see JS error in console. But using Classic UI it works fine. Not sure if this is AEM Touch ui issue or something wrong in our authoring

133

Hi Arun and Team, We have similar situation with token.... - Adobe Experience Manager

Hi Arun and Team,@Arun_Patidar We have similar situation with token.json. our sites are mostly public and we dont need calls for token.json hit publisher. So we used your above solution to redirect call to a dummy json. but now we have CUG pages in the site and we were validating if we need to bring back token.json for CUG pages. Questions:1. Even if now token.json returns dummy value, AEM still works in CUG pages...Shouldn't AEM stop accessing CUG page when my token.json value is wrong and does...

430

What role is required for a non-admin user to change AEM password - Adobe Experience Manager

HI, Can a regular AEM user can change his password in AEM Authoring..? What is the role we need to assign to that usert to be able to change only his/her own password (self serving option)..?

158

Custom validation logic in Content Fragment Model - Adobe Experience Manager

Request for Feature Enhancement (RFE) Summary: With more and more increased usage of Content Fragment for Headless applications (who consume JSON CFs from AEM), there is plenty of requirement where application teams need more control on each fields in Content Fragment. Currently there is no option to add custom field validations, add javascript validations or Regex in Content Fragment. Use-case: Content Authors make mistake where they save and publish critical data in CFs. Need custom validation...

204

Re: Add custom field validation in Content Fragment Model... - Adobe Experience Manager

Sure Brian..will add the suggestion and thank you for the help/solutioning.

184

Re: Add custom field validation in Content Fragment Model... - Adobe Experience Manager

Hi Brian, Sorry if I misunderstood..but the below solution is also based on single input field....In my case I need to compare values from two different Date input fields in CF and then hide Save button in case Date1>Date2

197

Re: Add custom field validation in Content Fragment Model... - Adobe Experience Manager

The JS is working now in terms of showing red mark in field but I dont see Save button getting greyed out if I enter "not allowed" value. I can still save the CF.Also can I use this "pattern" to compare 2 date fields , something link show red mark id Date1>Date2 in that CF...?

212

Re: Add custom field validation in Content Fragment Model... - Adobe Experience Manager

Also when i add the code "$('input[name=text_fld]').attr("pattern", 'working|works');" in console, I still see Save button enabled with wrong value.

239

Re: Add custom field validation in Content Fragment Model... - Adobe Experience Manager

hI Brian, Thank you for the solution. What I understood from the solution is that I can add Regex to validate a field. It is not something content author can doo on the fly but Develop need to set the regex for them to use. In my case I have requirement where they will add 2 date fields and need to check if date1>date2...can we achieve this sort of validation...

250

Adding field validation in custom Content Fragment Model's data types - Adobe Experience Manager Assets

Hello, We have a requirement where we need to add custom field validation when creating a content fragment (CF) using a custom content fragment model (CFM).Currently when I create a CFM, I only see some limited option like can mark field as required or specify max char limit etc. But what if i need to create a custom date field called "Age" where I can specify Regex or logic that selected date can not be in past date etc, something like that... I know we can create custom data types which I can ...

123

Add custom field validation in Content Fragment Model / Content Fragment - Adobe Experience Manager

293

Re: Unable to see Create button in Content fragment Model... - Adobe Experience Manager

Thank you Chitra for pointing out..

152

Re: Unable to see Create button in Content fragment Model... - Adobe Experience Manager

I can narrow down the issue as:If I goto here - ttp://localhost:4502/libs/dam/cfm/models/console/content/models.htmlI can see create folder button.

123

Unable to see Create button in Content fragment Model or Template page - Adobe Experience Manager

HI Guys, Suddenly I noticed i can no longer see "Create" button to create folder in CFM or Template page. I can create CF or templates inside already create folders though.I am logged in ad "admin", so should not be access issue. I am at AEM 6.5.5. Dont see create folder options here:http://localhost:4502/libs/dam/cfm/models/console/content/models.html/confhttp://localhost:4502/libs/wcm/core/content/sites/templates.html/conf Any help would be appreciated.

185

Re: ACS Common Dispatcher Flush agent not working - Adobe Experience Manager

HI Maximilian_Voss, looks like the issue with French pages are that I was adding them with English page name but for some reason looks like the cache getting cleared if I add the pages in Dispatcher Flush page with French Title. The pages are getting stored in Dispatcher cache with French Title...Not sure what changed but it was always working with page name and there we were using same page name for both En and Fr....!!

304