Skip to content

Instantly share code, notes, and snippets.

View sergeimuller's full-sized avatar

Sergei Müller sergeimuller

View GitHub Profile
@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.

/*
---
name: guilloche
script: guilloche.js
description: guilloche
provides: [Guilloche]
...
*/