General architecture is author for write & publish is read only copy of author with exception of social module. In your setup that is not true. Any reason?Anyhow For your use case you do not have to get vanity path from publish instead configure flush at publish instance rather than at author.  Alte...

File daycare and ask for patch CUI-438  After installing the patch Should resolve the issue.

Confused with your posting. You want new registration Plus validating against database.  In case user already exists is ldap then use ldap authentication http://dev.day.com/docs/en/cq/5-6/core/administering/ldap_authentication.htmlIf user no where exists then start with exploring from [1].   Note [1...

en, it in my example was referred to language preference  more details athttp://dev.day.com/docs/en/cq/current/administering/security.html#Setting%20User%20and%20Group%20Preferences

OOB should be already doing it.  Change language preference for Calender component on a Toolbar page and adding a date seems to be coming fine [03/12/2013-en, 12/03/2013 - it].by default, the format used for the date display is "m/d/y". Then it translates the messages using i18n nodes.Take a look at...

Till your account is setup as a workaround delete all nodes below /var/classes/org/apache/jsp/*  & then restart Apache Sling Dynamic Class Loader Support bundle to force them to recompile.

De-ponds on your cq version. File daycare & get required hotfix.http://helpx.adobe.com/experience-manager/kb/CQ5JSPsNotRecompilingOnPackageInstallation.html

When you activate the page. You should get an option that all the reference image need to be activated. Are you getting that Dialog?   If not then might be custom implementation or hotfix might breaking it.  File a daycare with CQ version & list of hotfix installed.

It will behave consistently otherwise it is bug & you might not have required hotfix deponding on aem version.  But for your usecase be it oob or custom always create under right runmode config

Symptoms indicates changes didn't picked by osgi even exists in repo. Verify*    If there is any config already exists in repo in someother location.*    Make sure if you have custom run mode create the config under right run mode.