Well, somehow it seems to be only a Firefox issue. With Chrome it works...

Thanks for the recording. Unfortunately it is not working and stops fully at 0:41 Can you please check?  

Sorry, but I doubt that this feedback process in the case is really exsiting. At least from the past the original case was NOT updated once the fix was out. And also, the suppoer answer that I gave you as an example does not fit to your statement - why I should I monitor the CQ-number although I get...

Yes, but that's not the point. From my ticket I get such unswers "... I would request you to please monitor the CQ-4298048 inclusion of the fix for your issue on the future release notes of the coming versions or service packs/CFPs on our official online documentation/ release document. " And here, ...

I don't know it is the correct place, but customer care recommended to post this here. Basically I have an enhancement request regarding the new Support portal (former daycare.day.com) within Admin Console. I often have the case that a reported issue was confirmed as a bug, got a internal Adobe CQ-n...

Hi,we have also raised a support ticket to get an answer how to break inheritance on field level within the component. Re: Field Level Inheritance - MSM For Classic UI (AEM 6.1) it seems there is a "hidden" property but I don't know about touch UI so far.From Business perspective breaking the inheri...

Hi, I'm trying to find someone that can help with a question which relates to question 22) here. It's about the property "fieldEditLockMode"I would appreciate if someone could help to answer this question here:Re: Field Level Inheritance - MSM Thx!

Hi,I having the same challenge: I need a field level based inheritance of a component since I need to avoid cancelling the whole component inheritance and therefore all fields.I found the property "fieldEditLockMode" in this article: aem - CQ5 - Cancel individual property inheritance of a Live Copy ...

Thanks, well an inplace upgrade is possible, of course. Our consideration was that since we did always inplace upgrade starting with CQ 5.4, it might be a good idea to start from scratch and maybe leave old stuff from older versions that is not in use anymore behind us...

Hi,we are also planning to migrate from AEM 6.1 SP1 to AEM 6.3. We are thinking of setting up fresh AEM 6.3 and migrate content then. But we have the need to keep and migrate the versions. Is this possible? Does anyone have experience with this scenario?Thx