Adobe CQ5 Upgrade issues

AEM version to others goes smoothly, sometimes it may be quite complex. Even though we might have followed all upgrade pre-procedures like clearing custom code, stopping workflows, etc, still people face some minor issues.

• JS will not be loaded so that the comments or similar buttons get unclickable.
• To get it to work we need to refresh JavaScript(JS) folders by clearing CQ level cache.
• Custom usage of deprecated code may stop us from proceeding.
• We might have used some deprecated APIs in the latest CQ versions like event-related(For E.g ProcessJob) or String vs StringArray. We need to rewrite those classes to get upgrades to work with all existing features.
• Launcher related workflows having issues.
• Even though all workflows disabled before the upgrade, we may have to redo our workflows to get it to work in case of any custom launcher workflows.
• Personalization not loading after the CQ upgrade.

After upgrade some times the personalization does not load. One reason may be Java script does not initialize properly.

To get it work, go to your custom user store,

/apps/ourproject/clientcontext/components/userstore/dialog/items/items/tab1/items/properties/fieldConfig :
property optionsProvider: < refresh this item to get personalization loading(Using a java script refresh or alert)

Personalization Segments folder gets deleted after upgrade. So all created segments may go off after upgrade. So always take a backup of segments before the upgrade.

In some cases, Client context may go to default with all options enabled, like geolocation, browser details, user's location request enabled, etc. Once done with the upgrade you can go and revert it to its previous settings.

Product limitations.
There are cases of the behavior of AEM for particular feature changes. In such cases, we may have to contact Adobe to get a proper resolution. If this is a product issue, Adobe gives a patch to help licensed users.