Thanks JaideepBrar for the suggestion. Given a vanity url example of '/annual-reports', how would you configure apache so that it knows whether it should redirect to page request in the CMS under /content/wherever or to an asset in the CMS under content/dam/wherever? And in the case of assets what request extension would you add to the request for the resolver process to act on? Neither apache redirects nor sling mappings are author-friendly. I'm looking for a solution where, for example, an au...

Re: Vanity Urls for DAM assets dorianhallward - Adobe Experience Manager

Thank you for the suggestion ka786. I wondered about sling internal mappings but I'm not sure I would describe that as "authoring-friendly"(?)

Vanity Urls for DAM assets dorianhallward - Adobe Experience Manager

Hi is there an equivalent vanity urls feature for DAM assets?Are there other authoring-friendly ways to achieve something similar (with minimal developer involvement (e.g. sling internal mappings))? For example we'd like to have a vanity URL for a terms-and-conditions document hosted in the DAM. The vanity url would map to somewhere like /content/dam/weretail/docs/legal/terms-and-conditions-2019.pdf

Re: How to test Rich Text Editors with Hobbes? dorianhallward - Adobe Experience Manager

Arun Patidar thanks for pointing out the deprecation of Hobbes.js in AEM 6.5. That's news to me and quite disappointing given the efforts we've put into using it. smacdonald2008 do you have any info on what went wrong with Hobbes? Why was it still part of the reference project in AEM 6.4 if there were no plans to maintain it from 6.5?Hobbes.js is almost a good solution to automated testing with AEM. The things I think are missing include,Although it is possible to start Hobbes tests in a semi-au...

Re: How to test Rich Text Editors with Hobbes? dorianhallward - Adobe Experience Manager

kanchanm42092031,notwithstanding the point about Hobbes.js deprecation in AEM 6.5, yes you can absolutely use Hobbes.js for "authoring auto tests". The crucial part of an automated test for use of a rich text editor in author mode, is correctly locating the rte container, i.e.before then adding appending some characters to it, i.e.you then need to click 'done' or 'save' or whatever to post the input back to be stored in the content tree.

Re: Dispatcher - font files are cached with size 0 following design tree activation dorianhallward - Adobe Experience Manager

Thanks for the suggestion hamidk11679710. We are aware of the advice to move clientlibs out of etc/designs (and note: our issue does not involve http 404 errors as in Clientlibs not loading the fonts when placed in apps). Our issue is not seen when requesting pages directly from a publisher instance, so i am happy our font files hosted at /etc/designs/sh/assets/fonts are accessible and served correctly from AEM.On closer inspection, the caching problem only arises when requests are made first ...

Dispatcher - font files are cached with size 0 following design tree activation dorianhallward - Adobe Experience Manager

When we upload a new custom clientlib - to etc/designs - and then do a tree activation, the next time we request a webpage that includes those font files, then the font files are created in the dispatcher with file size 0. The resulting impact is that when requesting a web page in the browser, font files are not properly downloaded (browser reports "Failed to decode downloaded font:")We can work around this issue by connecting to the dispatcher and manually removing the font files before re-requ...

Re: How to test Rich Text Editors with Hobbes? dorianhallward - Adobe Experience Manager

kanchanm42092031hi we found this was just a case of getting the CSS selectors right. If you are still looking into this would you be happy to share a snippet of your html markup and the hobbes.js scripts you are using to test it? (I'm not sure what you mean by 'context')

Re: DAM Assets - how to make request activation workflow available? dorianhallward - Adobe Experience Manager

smacdonald2008 this requirement, to have a “request publication“ workflow for individual DAM assets (as there is for pages), feels like it should be a standard OOTB feature. is there a formal way to request this as an enhancement to forthcoming AEM releases?thanks

Re: How to override AEM default favicon icon and page title in AEM 6.4 ? dorianhallward - Adobe Experience Manager Assets

I was looking at how to add a favicon for a site and saw this thread. Sounds like the approach is different now to the one linked above: with AEM core components, using the page component and editable templates, we can now specify a client library (provided we have set "allowProxy=true") as the location for things like favicons. The page component will then look for image files with specified names - see head.html

Re: Should Target work with custom html elements? dorianhallward - Adobe Target

Thanks again John for your suggestions. My forum question here is not a programming one. It's about using the Target GUI. When we try and edit one of our existing website pages (served by Aem) the Target GUI - that allows you to highlight parts of a page and change text and images - fails to correctly swap-in the target user's proposed amendments to text and images. The html parts of the Web page that target can't seem to amend are specifically the sh-header custom elements in my snippet above. ...

Re: Should Target work with custom html elements? dorianhallward - Adobe Target

John thank you very much for taking the time to reply. We have written our components via a javascript framework: Vue.js. Our components make extensive use of custom html elements. So i suppose the root of my question is: do custom html elements pose a problem for Adobe target, in terms of locating text and images to replace in a/b tests? For most of our custom html elements Adobe seems OK, but it struggles with the sh-header in my original snippet

Should Target work with custom html elements? dorianhallward - Adobe Target

We have components in Experience Manager written via a javascript framework. As a result there are custom html elements in our markup. This is presumably quite a common scenario. Target seems to struggle to work with this markup - in terms of amending text and images.What should Target be able to do in this case and - if it is problematic - what can our developers or adobe do to help?Here's a snippet example of our markup,

Re: Preferred method to sync content - from prod to stage - in AEM 6.4? dorianhallward - Adobe Experience Manager

Thanks for asking smacdonald2008 we hadn't considered crx2oak. I will give that a try.

Re: Preferred method to sync content - from prod to stage - in AEM 6.4? dorianhallward - Adobe Experience Manager

Thanks for taking the time to reply smacdonald2008 What do other customers do: presumably this is a fairly common use case? Anything Adobe recommends as an OOTB solution (online backup? VM clones of live Aem instances?) Any further info appreciated. Regards Joe

Preferred method to sync content - from prod to stage - in AEM 6.4? dorianhallward - Adobe Experience Manager

Our content authors and AEM developers would like pages and assets hosted in AEM authoring and publishing 'staging' environments to be as similar as possible to the production environment, via an automated mechanism, (e.g an overnight 'rsync'-style copy).What is the most straightforward and most reliable way to achieve this? Essentially we'd like to copy the "diff" from live to stage, preserving anything on staging that is newer than live. So far we have considered a few options, Jackrabbit vaul...

Re: Dispatcher CORS configuration - gap in documentation dorianhallward - Adobe Experience Manager

Thanks jonnowso has your solution been to,1. set osgi CORS policy2. configure your apache/dispatcher cache section to enable CORS header pass through and cache CORS response headers in dispatcher3. configure mod_headers in apache to overwrite any Access-Control-Allow-Origin response headers cached by the dispatcher and replace that header value with the matching entry from your whitelist?If i've understood how it works that sounds great and i will give it a try.Still feels like the aem/dispatch...

Re: Dispatcher CORS configuration - gap in documentation dorianhallward - Adobe Experience Manager

smacdonald2008 can Adobe help with any further info about my follow up point around CORS header caching?Are there any other ways to address the problem that the first requesting origin is the one that gets written into the header cache (meaning subsequent requests from other authorised origins are blocked)?Would having individual CORS policies for each allowed origin help - or would the caching problem still be there? Are there other ways to configure the apache dispatcher to allow CORS respons...

Re: SVG is not showing on Google Chrome dorianhallward - Adobe Experience Manager

Installing an upgraded osgi org.apache.sling.security-1.1.16.jar corrects this issue (presumably adding the right headers into the response if @fernandou23761826 's analysis of the problem is correct).@ kautuksahni is this the official solution? how will this get rolled out, do i need to include sling security jar as a provided dependency along with custom code?

Re: Dispatcher CORS configuration - gap in documentation dorianhallward - Adobe Experience Manager

Hi thanks @smacdonald2008.Actually this is proving more problematic than we first thought - some advice and further info from Adobe would be appreciated. So far, I've only been able to get CORS request handling to work via the dispatcher if we add appropriate 'header' entries to the 'cache' section of the dispatcher config. So whether we want to or not, we end up caching CORS response headers. The problem is that in our use case we have an osgi CORS policy regex that allows a number of origins b...

Dispatcher CORS configuration - gap in documentation dorianhallward - Adobe Experience Manager

Hi,I've just worked through configuring our AEM dispatchers to support CORS requests and I think the Adobe documentation needs improvement. Configuring a CORS policy via system/console was straightforward enough but while direct requests to our publish instances returned a valid response (with expected "Access-Control-Allow-Origin:..." in the response headers) requests via our dispatchers did not (and no CORS request handling was being logged in our publisher's output). I couldn't understand the...

Re: DAM Assets - how to make request activation workflow available? dorianhallward - Adobe Experience Manager

Thanks for your suggestion Arun Patidar but I explicitly do not want to implement a custom workflow, i want to reuse the OOTB workflows available with AEM. I just want some advice on how to configure doing that for individual assets

DAM Assets - how to make request activation workflow available? dorianhallward - Adobe Experience Manager

Hi,we would like to use AEM OOTB functionality to support a publication workflow. To achieve this, we have set user group privileges to deny access to all workflow models under /etc/workflow/models - except for request_for_activation (and _deletion and _deactivation). Great: when authors upload new assets and create new pages that use those assets, they don't get to pick from individual workflows but can instead use the "Request for publication" option in sites to bring up the libs/wcm/core/cont...

Re: Can't find feature pack 22818 (content fragments) - where is it? dorianhallward - Adobe Experience Manager

Thanks Kunwar. Is it the case that neither the feature pack 22818 nor the cumulative fix pack for 6.3 - mentioned in my previous comment - are available? Is it normal for the Adobe website to publicise FPs and CFPs that aren't there yet?How do I get those in the short term? I looked on the licensing site with our customer account but presumably that's not intended to distribute feature packs to customers (?). I'm the meantime I will (amidst some confusion) raise a support case.

Re: Can't find feature pack 22818 (content fragments) - where is it? dorianhallward - Adobe Experience Manager

Thanks for following up smacdonald2008. This FP is hot off the press (May 2018) so it'd be good to know where it is. A colleague has also tried to locate it in adobeaemcloud marketplace - just to make sure it's not down to my account credentials.I wondered if it's been incorporated in Adobe Experience Manager Help | Release Notes: AEM 6.3 Cumulative Fix Pack - can't quite tell from the documentation there...UPDATE: I can't seem to get to download the cumulative fix pack https://www.adobeaemclo...

Can't find feature pack 22818 (content fragments) - where is it? dorianhallward - Adobe Experience Manager

Hi, this web page Content Fragment Updates and Content Services - Feature Pack Release Notes includes a link to FP 22818 ("This feature pack replaces the set released in October 2017.") but the adobeaemcloud.com/content/marketplace page shows an error and in package share a search for 22818 returns no results.Has this FP been incorporated into something/ somewhere else?thanks

Re: Path field throwing error in AEM 6.4 Touch UI dorianhallward - Adobe Experience Manager

Thanks Kunwarunfortunately my mistake was even more basic - the data source for my picker - e.g. /content/myapp/dam wasn't there on the target VM environment So spurious "{value}" actually a red herring.I think I went down a bad line of enquiry. Printing and sending you the stack trace was helpful though - because it pointed out to me that there's no issue with the "/mnt/overlay..." request path - just the parameters appended to it. Easy really, some additional error info returned in the respon...

Re: Path field throwing error in AEM 6.4 Touch UI dorianhallward - Adobe Experience Manager

smacdonald2008 and Kunwarthanks for your help with this.Embarassingly it looks like the problem is down to the spurious ""{value}" +" added into the middle of my defaultPickerSrc string. I'm not sure how that works in my local but doesn't work elsewhere

Re: Path field throwing error in AEM 6.4 Touch UI dorianhallward - Adobe Experience Manager

Hi smacdonald2008no, unfortunately, I am amending customisation provided from a third party - and who had a contractor working for them to add some further indirection! The previous supplier's code has a 'targetCollection' property value of '#cq-commerce-product-picker-collection' in their /apps/foo_app/components/widget/content/externalbrowser/picker node, which I see is similar to properties under /libs/commerce/gui/content/common/productfield. Perhaps that's where they took their inspiration...

Likes given to

User

Count

Likes from

User

Count

Guidelines

Cookie preferences