We are facing the same issue, this is a huge change for us as we don't allow direct Image upload and while using a path browser could be a work around, authors will no longer be able to search for their asset on the left asset finder and drag and drop onto page props as with the 6.2 popup dialog.Any...

I'm getting the same errors as OP on Publisher - hitting publish URL directly...Anything with etc.clientlibs is throwing a 404 on the browser and AEM is generating the same ClientLibraryProxyServlet "not supported" It seems to happen when adding a URL mapping in the Apache Sling Resource Resolver Fa...

Has anyone been experiencing this issue with 6.1 and Communities FP4? We are including cq/personalization/components/clientcontext component which seems to be the cause of these calls being made. However, in order to user the CQ.ProfileDataMgr this needs to be included in our pages. Why is it making...

Bump! Anyone have a hint or a fix for this? 

Has anyone found a solution for this? I tweeted the Adobe guys who said they ran a quick test and could not reproduce. It's a pretty big issue as it renders the page incorrectly in edit mode! Would be great if someone from Adobe could reproduce and provide support. 

The drag & drop an image inside a dialog feature instead of directly into the component is crucial for things like carousels. To create a decent author experience, we now have to show the 4 slides (in a carousel for example) so the author can drag & drop the images into each slide, then once in prev...

I have a component that has a parsys inside of it.If the parsys is included in the sightly html component file; afterinsert is not fired. As soon as I remove the parsys from the component it fires. Please help! 

This issue is fixed with SP1 for AEM 6