In Inline Editing with WLP 10.3.2 Content Templates, I concluded that if something else came up I would blog it. Well, it did, so I will.
The shared library part went nice and smooth. To note the (semi-)obvious, the wlp-template-config.xml changes noted in the post must be done in the consuming application, not the shared application, as the consuming application always over-rides.
The part I forgot about was that you must create a role for editing the content or else only Admins will be able to do the inline editing. I created an enterprise role named “homePageContentAdmin” for my first test, then granted that role update privelages on the content item. Once I did that, it worked properly.
As another sort-of-obvious note, this requires granting view privelages for anonymous or authenticated roles for other users to view the content.
© Scott S. Nelson