Extensions: Support versioned page in side-by-side view


Since AEM 6.3 the side-by-side version comparison works on the following path /content/versionhistory/[<tenant>/]/<userId>/<origininalPagePath> (for the versioned page on the right-hand side). That path should be supported by both ContextPathStrategy s (https://github.com/wcm-io/wcm-io-caconfig/blob/develop/extensions/src/main/java/io/wcm/caconfig/extensions/contextpath/impl/AbsoluteParentContextPathStrategy.java and https://github.com/wcm-io/wcm-io-caconfig/blob/develop/extensions/src/main/java/io/wcm/caconfig/extensions/contextpath/impl/RootTemplateContextPathStrategy.java) by subtracting two or three levels there (depending on whether a tenant is configured), i.e. the part versionhistory/[<tenant>/]/<userId> must be ignored when looking up the related CA configuration.


Stefan Seifert
March 13, 2018, 2:33 AM

my plan was to release it ~mid of this week - is this enough?

Konrad Windszus
March 13, 2018, 2:46 AM

Works for me. Thanks a lot.

Stefan Seifert
February 20, 2019, 11:16 PM

it seems the paths have changed with AEM 6.3 SP3 CFP2 and AEM 6.4 SP3 to /tmp/versionhistory. we'll need to update the implementation, ideally in a way to support both the old and the new URL pattern.

Konrad Windszus
February 20, 2019, 11:32 PM

Is it possible to implement a heuristic based on LanguageUtil.getLanguageRoot()?

Stefan Seifert
February 21, 2019, 2:27 AM

i've implemented a solution in caconfig extension 1.5.0 (currently testable with 1.4.1-SNAPSHOT)

can you cross-check if it works in your context as well? as far as a i see the path unter /tmp/versionhistory is no longer tenant-dependent.
the older path pattern unter /content/versionhistory is still supported, so it does not matter which service pack is installed.



Stefan Seifert


Konrad Windszus




Affects versions