First a little background, then several questions below.  I am a recent convert from the .NET world, so I am still picking up on AEM, Java, Maven, etc.  We are using 6.3 and created our project solution using archetype 12.  Most development is happening on local workstations between AEM and Eclipse....

I did confirm it is now working in our environment. I tried to track down the daycare ticket but I cant for some reason.  If memory serves I think it might have been in SP2 for 6.3?  I do believe this is affected by the 'Publish' line in the Day CQ Link Externalizer configuration at .../system/conso...

In case anyone else runs into this issue, the problem was that when the group template was created our replication agents pointed to another publisher.  So the new publisher did not have record of this template which caused the membership group/role creation to fail when publishing a new community g...

When we publish a new Community Group, using the Group Function of communities it typically will generate 3 permission groups - members, privileged members, and moderators.  These are supposed to be created on the publish instance.  In all of our test environments this is working correctly, but when...

This was submitted as a ticket and ultimately discovered to be a bug.  Adobe provided a patch that will be included in a future release

I have given this a try, but it did not resolve the problem.  What I have noticed is the communities features just don't seem to always leverage the configuration/settings appropriately.  We also architected our solution with a tomcat application server in order to add a contextpath or directory to ...

Using 6.3. After setting up AEM Communities and enabling tunneling we are able to see community users on the author side under Navigation > Communities > Members.  However, the URL to retrieve the users avatar profile picture is being generated incorrectly.  It is pointing to the default http://loca...