leeasling

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

Your achievements

0% to

Tip / to gain points, level up, and earn exciting badges like the new

Open Alerts Bar

Community profile leeasling Level 6

Job title here

Location here

14 BADGES

Learn more

Joined the community 08-07-2014 12:11:15 PM

Offline

View leaderboards

Profile

Trophy case

Top badges earned by leeasling

Boost 1

Re: tel: protocol not working in aem for pathfield classic ui - Adobe Experience Manager

Can you add an image of the HTML source of the anchor tag as it's rendered on the page?

7.4K

Re: tel: protocol not working in aem for pathfield classic ui - Adobe Experience Manager

You have to update the Day CQ Link Checker Service (com.day.cq.rewriter.linkchecker.impl.LinkCheckerImpl) to allow for tel: links.You should also change the content of the href to @ context='uri'

7.4K

Re: Disabling delete option for component - Adobe Experience Manager

Have you tried putting a cq:editConfig in place and not providing the delete option?

2.4K

Re: touch ui page not getting refreshed on adding new component - Adobe Experience Manager

First off, I would maybe try a private browser window and make sure it's not a javascript caching issue.Secondly, I would take a look at your node structure and make sure that the page has a valid cq:template and sling:resourceType.

8.1K

Re: Custom Multifield is not working In AEM 6.3 - Adobe Experience Manager

This typically happens because 2 xtypes have the same namespace and therefore AEM tries to load both. I've seen this with ACS Commons installed (with their multifield panel) and also a custom multifield being installed.

657

Re: AEM Query for property with no value - Adobe Experience Manager

Not to my knowledge with the query builder. Instead of setting the value to blank, could you set it to "none" and query for "none" instead?

3.3K

Re: Content Fragments Use-Cases? - Adobe Experience Manager

1. You're correct. I think the point is that the content itself is located centrally and available for other authors to see, can be controlled by permissions, and you can create snippets based off of a content fragment and variations of a content fragment. From an authoring standpoint I don't believe there is any benefit as far as the number of fields, just that for other authors the content can be viewed centrally without navigating the site to find it.2. Again, good question. Language variatio...

1.5K

Re: AEM Query for property with no value - Adobe Experience Manager

I think the difference is that you removed the value, meaning that the property name still exists on the node but has an empty string - when you save an empty value using a dialog, the property itself is removed - so the not operation looks for the property not being on the node at all. Go ahead and delete the "test" property rather than give it an empty value and the query should return that page.

3.3K

Re: Content Fragments Use-Cases? - Adobe Experience Manager

I think the point of content fragments was to be able to create pieces of content that could potentially be used in multiples places, with or without slight variations, and house them in a single location, rather than prior where you'd need to use a reference component and have the author navigate the node structure to find what they're looking for.To attempt to answer your questions:1. They can be used for anything, long articles, short blurbs, it really doesn't matter the length of the text. Y...

1.5K

Re: Custom Multifield is not working In AEM 6.3 - Adobe Experience Manager

This is very vague.This is also the reason you don't implement custom multifields, because the API's are constantly changing.

688

Re: AEM Query for property with no value - Adobe Experience Manager

You can do the following and remove the property.valueproperty.operator=notYou may also need to add @jcr:content/ to the property name, so the full thing would look like this:path=/content/myproject type=cq:Page property=@jcr:content/sectionEmail property.operation=not

3.3K

Re: Adobe Granite HTML Library Manager - Long term client side cache key - Adobe Experience Manager

It's part of the Apache Configuration. Documentation is here Versioned ClientLibs Apache ConfigurationTo configure Apache to send the right header to set a long TTL:SetEnvIf Request_URI "(\.min)?\.[a-f0-9]+\.js" long_expires=true SetEnvIf Request_URI "(\.min)?\.[a-f0-9]+\.css" long_expires=true Header set Cache-Control max-age=2592000 env=long_expires

948

Re: Tag ID xtype multifield issue in AEM 6.2 - Adobe Experience Manager

Try changing the store from JSON to NODE and make sure your property name for tags is ./cq:tagsAdd this to your dialog fieldacs-commons-nested="NODE_STORE"

802

Re: minifying JS and CSS in 6.2 causing errors - Adobe Experience Manager

the most common cause of this i've found is that you're using a reserved word as a variable name or function name. If you check the error log, you'll see the first time it errors it'll give you a pointer close to the word it failed on.

2.2K

Re: AEM Post Servlet Ajax call fails on first time call when page opened in new browser. - Adobe Experience Manager

You need to update the users information in the browser. Try the below. It clears any current information stored in the users profile and reloads it after successful login.$(document).ready(function() { if(userName && password) { if (CQ_Analytics) { if (CQ_Analytics.ProfileDataMgr) { //Clear the current profile CQ_Analytics.ProfileDataMgr.clear(); } } $.ajax({ type:'POST', url : path[0]+"/j_security_check", data: { j_username: userName, j_password: password, j_validate:"true" }, success: functio...

1.1K

Re: Trouble with HTL includes - Adobe Experience Manager

Remove the "data-sly-unwrap" - you're unwrapping the element that's needed for editing.

774

Re: Sightly component with drag and drop image (get the file reference) - Adobe Experience Manager

public class ImageHelper extends WCMUsePojo { public String getImageSrc() { Image image = new Image(this.getResource(), "image"); if (image != null && image.hasContent()) { image.setSelector("img"); return image.getSrc(); } return null; } public String getBackgroundImageSrc() { return "background-image:url(" + this.getImageSrc() + ")"; } } Some stuff in here.

806

Re: String[] type for Multivalued Properties - AEM - Adobe Experience Manager

Easiest way to handle it is as follows:String[] value = properties.get("propertyName", new String[] {});This will create a string array regardless of 1 or multiple string values, regardless of String or String[] type.

6.5K

Re: Not able to login in AEM Publish instance - Adobe Experience Manager

Check the referrer filter configuration and make sure the domain is allowed.

8.3K

Re: Best approach to show up pages at different levels in component : AEM 6.2 - Adobe Experience Manager

You can use the second piece of code i posted for the multifield of path fields, this will allow you to select multiple pages at really any level, but you can restrict it by path too.

815

Re: Best approach to show up pages at different levels in component : AEM 6.2 - Adobe Experience Manager

I may be misunderstanding the requirements, but it would seem you could simply use the OOTB path field and set the root path to the content structure.If you need to allow them to select multiple then you can put that field inside of a multifield.

811

Re: Is it possible to defer or async JS in ClientLibs (AEM 6.1, using JSP)? - Adobe Experience Manager

I don't believe Adobe is putting any attention on improving support for JSP beyond what's already in place. Sightly is the new standard so it may be worth implementing the component you need this functionality in with Sightly rather than JSP.

4.3K

Re: Loading Sightly templates outside of /apps - Adobe Experience Manager

Well the difference there is that they're developers and should know what they're doing. Any code changes by a developer should probably also go through a QA process. Giving an author, whom we have to assume knows nothing about coding/html control over code that gets compiled, in any environment, but especially in Production seems like a really bad idea. A missing single quote, accidentally deleting a curly bracket or even just misspelling something like "context" would bring the site down insta...

1.2K

Re: Loading Sightly templates outside of /apps - Adobe Experience Manager

I have to ask, why on earth would you want to give authors access to something that could potentially take down their site? Seems like a really bad idea.

1.2K