Solved! Go to Solution.
Views
Replies
Total Likes
Adobe can not cover each and every scenarios, that we faced in our day to day development activity, in its official documents because it is not known to them so most of the time we need to be dependent on some so called unofficial sites. But in unofficial sites if implementations are based on logic we must go for it.
Some time it is recommended to overlay the stuff from libs to the desired path so based on this logic, I don't see any issue in the multieditor enhancement, done in the above blog. If it meets your requirement you should use it.
Hope this helps
Umesh Thakur
Adobe can not cover each and every scenarios, that we faced in our day to day development activity, in its official documents because it is not known to them so most of the time we need to be dependent on some so called unofficial sites. But in unofficial sites if implementations are based on logic we must go for it.
Some time it is recommended to overlay the stuff from libs to the desired path so based on this logic, I don't see any issue in the multieditor enhancement, done in the above blog. If it meets your requirement you should use it.
Hope this helps
Umesh Thakur
Thanks for your reply. I mostly agree with you comment apart from the fact that RTE documentation is being deemed as a corner case, when it is NOT. RTE is as old as AEM and something tells me there might be a reason behind Adobe not exposing all plugins OR maybe it is on their roadmap. My question was also to check if someone knows about any official documentation I might have missed while searching, so I will wait for more comments on that.
Views
Replies
Total Likes