Skip to content

Instantly share code, notes, and snippets.

View msulliva's full-sized avatar

Matthew Sullivan msulliva

View GitHub Profile
@msulliva
msulliva / aem-css3pie.md
Last active December 19, 2015 14:49
Silly way to make CSS3 Pie work in CQ5 / AEM - http://css3pie.com

CSS3 Pie in AEM / CQ5

Perhaps this has changed in 5.6 but these were the steps I went through to enable CSS3 Pie pie.htc on the Author, Publish, and Dispatcher when I got it working in 5.4 and still works in 5.6.

The main problem I believe is that IE7 / 8 want the HTC Behavior to be sent with a very specific mime type of text/x-component.

So in order to do that I'm sure there is some way to add a Mime type in Sling, but I couldn't make heads or tails of it at the time, so I just did something silly and turned pie.htc into a component that manually sets the mime type.

In /etc/designs/myapp/pie I have an nt:unstructuered node with:

@msulliva
msulliva / cq54-aem56-upgrade.md
Last active December 18, 2015 02:19
Old Dominion University recently did a 5.4 to 5.6 upgrade (this was our first upgrade) and there was some interest here, and we figured we would share our lessons learned and checklist with the group.

Overview

We upgraded directly from 5.4 to 5.6 with an in place upgrade using the "-unpack" method. We did the Author on a Saturday, and the Publishers on the Sunday, mostly because we ran into the Publisher permissions problem on Saturday night, and stayed on 5.4 publishers while trying to resolve.

Overview of changes that caused us some pain

New Publisher Permissions

Anonymous User Permissions on Publishers are more restrictive, pretty much just has access to /content and /etc on the publishers in 5.6. So any assets that may have been used from /apps even if not through the public interface should probably move under etc. We had XSL transformations that the component couldn't read the .xsl file under /apps. I think this also is the root cause of the ResourceResolver issues.