I'm working on enabling Adobe Target on our AEM site and I'm getting the following exception when trying to create a Target Activity in a given page.  If I use an admin account it works fine so I'm thinking it's something permission related.  I've granted permissions to the user I'm using when it fa...

Thanks for all the feedback everyone!  Just to summarize and clarify to get a Touch UI component to appear in the side rail and design mode you must have the following:cq:dialog node (if the component is to be editable) [OPTIONAL]cq:editConfig [REQUIRED if you want it to appear in side rail/design m...

Isn't the dialog.xml for the Classic UI and the cq:dialog is for touch ui?  Why would we need a dialog.xml in this case?  It will appear in the side rail with a cq:EditConfig node and no dialog.xml.

When creating a new component in AEM 6.2 I noticed it doesn't appear as an available component in the side rail or in design mode until I add the cq:EditConfig node to the component.  I also noticed if I add a dialog.xml node it will allow it to appear in the side rail and via design mode but my und...

I'm still getting the same error when attempting on a new 6.2 instance with SP1 and CFP4.  I'll use the link lasling​ mentioned but it would be nice if it worked via package share to avoid downloading, then uploading again to package manager.

Should I be able to access package share from my local instance? After entering my credentials I'm getting the following error.  Also, what is the Adobe URL that contains all the cumulative fix packs?HTTP ERROR: 500Problem accessing /crx/packageshare/login.html/content/packageshare/tools/login.html....

That worked.  Thanks Feike!

Yes, I'm referencing a valid object.  It seems like it might have something to do with updating an attribute name, as the other attribute values are working fine.  Let me know if you have any other thoughts.

If I want to output the attribute name via HTL, how do I go about doing this?For example I want to be able to specify the meta tag as either <meta name=.. or <meta property=....When I try this...<meta ${metadata.metaTypeName}="${metadata.metaTypeNameValue}" content="${metadata.metaContentValue}" />I...