VersionManagerImpl Refuse to create new version on page activation
Hi,
I've a few pages that have been rolled out using MSM and then manually activated/published. The problem is that some of them don't have any versions created on publication.
Looking at a page with versions I see:
{
"jcr:primaryType": "cq:Page",
"jcr:createdBy": "...",
"jcr:created": "Tue Aug 15 2017 22:55:32 GMT+0000",
"jcr:content": {
"jcr:primaryType": "cq:PageContent",
"jcr:mixinTypes": [
"mix:versionable",
"cq:LiveRelationship"
],
"jcr:createdBy": "162738",
"jcr:title": "Visa and health",
"cq:lastReplicationAction": "Activate",
"jcr:versionHistory": "5a9ba82c-1853-4ff8-8e5d-2ba6156d072b",
"cq:template": "/apps/xxx/global/templates/full-width",
"cq:lastReplicatedBy": "320432",
"redirectTarget": "/content/...",
"cq:lastRolledout": "Wed Aug 16 2017 06:38:12 GMT+0000",
"jcr:predecessors": [
"1484877d-47e8-410d-ba23-46cb1c58bf72"
],
"jcr:created": "Tue Aug 15 2017 22:55:32 GMT+0000",
"cq:lastReplicated": "Wed Aug 16 2017 02:08:05 GMT+0000",
"cq:lastModified": "Wed Aug 16 2017 01:18:52 GMT+0000",
"showInFooter@Delete": "true",
"cq:cloudserviceconfigs": [
"/etc/cloudservices/dynamictagmanagement/xxx"
],
"jcr:description": "......",
"jcr:baseVersion": "1484877d-47e8-410d-ba23-46cb1c58bf72",
"jcr:isCheckedOut": true,
"pageTitle": "....",
"jcr:uuid": "4b0fbf6a-7be3-43e2-820f-6d8a4ef95f80",
"sling:resourceType": "xxx/global/components/pages/full-width",
"textIsRich": "true",
"cq:lastRolledoutBy": "...",
"cq:lastModifiedBy": "..."
}
}
Without the versions I see:
{
"jcr:primaryType": "cq:Page",
"jcr:createdBy": "...",
"jcr:created": "Tue Aug 15 2017 23:02:34 GMT+0000",
"jcr:content": {
"jcr:primaryType": "cq:PageContent",
"jcr:mixinTypes": [
"cq:LiveRelationship"
],
"jcr:createdBy": "162738",
"jcr:title": "...",
"cq:lastReplicationAction": "Activate",
"cq:template": "/apps/xxx/global/templates/full-width",
"cq:lastReplicatedBy": "...",
"cq:lastRolledout": "Wed Aug 16 2017 06:36:31 GMT+0000",
"jcr:created": "Tue Aug 15 2017 23:02:34 GMT+0000",
"cq:lastReplicated": "Wed Aug 16 2017 01:44:46 GMT+0000",
"cq:lastModified": "Wed Aug 16 2017 00:08:53 GMT+0000",
"showInFooter@Delete": "true",
"jcr:description": "......",
"pageTitle": "......",
"sling:resourceType": "xxx/global/components/pages/full-width",
"textIsRich": "true",
"cq:lastRolledoutBy": "...",
"cq:lastModifiedBy": "..."
}
}
Notably differences include the cq:LiveRelationship mixin and associated version properties. In testing I determined that the mixin is added when the page is versioned (when publishing), not before.
The most interesting thing I've seen in the logs is
16.08.2017 02:04:41.374 *INFO* [127.0.0.1 [1502849081372] POST /bin/replicate HTTP/1.1] com.day.cq.wcm.core.impl.VersionManagerImpl Refuse to create new version for unmodified page /content/xxx/...
which seems the key to the issue. Why would aem refuse to create a new version for a page that wasn't even published before?
Looking in detail at both pages I see some differences in the sequence of the dates (modified, rolled out, activated), but still, I think the previous question stands.
Any ideas?
Thx,
Federico
PS: aem 6.1 SP2