>Points to consider (mostly AEM specific):
>- CACs can be problematic with MSM
>- CACs can be problematic with replication
>- CACs can be problematic with translations (if CAC contents need to
>be translated)
>- CACs are unintuitive for content-editors
if these problem are still unsolved it may
hello nicolas.
last time i looked the implementation of template editor/content policies does
not seem to fully use the caconfig api and concepts for its functionality. it
also stores it's configuration in /conf in a caconfig-like structure, but does
not fully work this way (esp. concerning
