This property is available in AEM6.1, need to check in AEM6.2, will revert you back

Hi Bala, you mean, you want user to use Twitter credentials to login and create the profile in the AEM accordingly ?Have you checked this url ?https://docs.adobe.com/docs/en/aem/6-2/administer/communities/social-login.html

Can someone confirm from Adobe, is AEM6.3 available to use ? i was under the impression that only beta is available and actual version would be released in May.

i see only a property where latest publish datetime is storing for Dam Assets which is "dam:lastInvalidateCache", not sure if this is the right one to use for dam assets.Thanks ~Sandeep

Nitin, you need to check the jcr:created property which is inside jcr:content of the page in publish. This property update every time when page get activated from author. I guess, you are checking jcr:created property directly inside the page node which remains same when the page first time replicat...

Have you looked into below forum thread and article ?http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__4tfa-hi_i_have_setup.htmlhttps://blog.rackspace.com/enabling-vanity-urls-with-adobe-experience-manager

look into this thread and check @kautuk replyhttp://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manager.topic.html/forum__vdub-all_i_have_this.html

As far i know, there are just the number to identify each row as unique. Yes these entries should be unique but not necessary in any specific order.

Sounds like the real issue with AEM while replicating content through package manager from Author to Publish, deactivated pages shows up on the Publish because they still exist in the environment. I would suggest to raise a daycare ticket if it is urgent issue otherwise you can live with alternate m...

You probably need to allow permissions for /apps and /etc under /filter section. Can you please check if these filters are set properly ?