On 6.3.0, version history node is getting created at /content/versionhistory path. My application does not have any custom code which does version purging and does not fetch any value from the nodes under /content/versionhistory.
-------child nodes [same as the site structure] [cq:page]
Versions are also present under /jcr:system/jcr:versionStorage path.
The nodes under /content/versionhistory are getting recreated, does this have something to do with audit logs?. Ex: I deleted /content/versionhistory node. Now, made changes to few pages [modified some components], and I see this /content/versionhistory node got generated again with the entire site structure under it as the child pages.
This is causing issues as are simple redirect rules and vanity urls set for some pages. When these redirects/vanity url's are removed from the actual page, some pages are not editable[blank page, nothing specific in log files] because these redirect/vanity path values are present as a duplicate under /content/versionhistory. Authors are getting blocked frequently.
This is a weird behavior, I dont have this /content/versionhistory path on my local instance, it is happening on higher environments. Can anyone suggest why this node /content/versionhistory is present and how its getting created and a way to get rid of it.
I want to know if anybody was able to solve this issue ? Version history node should get created inside tmp/versionhistory not content/versionhistory. If anyone was able to solve the issue please reply.