We have recently upgraded (via migration) to 6.4 from 6.2 and are getting some new nodetransition emails when users who have replicate rights to a page that contains assets that they don't have replicate rights to try to activate. In many cases, the assets on the page have been previously activated,...

Here's the only error that I'm seeing. "com.day.cq.search" and "org.apache.jackrabbit.oak.query" both remain empty, which suggests to me that it doesn't get to generating the xpath query. This is also suggersted by the fact that the querybuilder debugger doesn't generate an xpath query..22.03.2019 1...

This doesn't address the problem, which I think has more to do with the processing and transformation of the querybuilder version of the query into xpath or something else--updating those values (doubling them) did not solve the problem.The query never gets to run, as far as I can tell.

We recently updated to 6.4 and I'm working on making our systems forward compatible. For the most part I've been successful, but it seems that the query builder can not handle large, complicated queries such as the one below, typical of a search in our news system.I've found that I can run this and ...

Our news system uses the normal page creation wizard, but removes the "name" field and adds an hidden input containing an numeric ID that is autogenerated--some random ID that is within the next 100 numbers of the last page. The randomness generally prevents collisions, which might occur if 2 users ...

Thanks. I don't know why I didn't think this worked. In my defense it was late.

I should also mention we're on 6.2

I have an index at /oak:index/newsSearch that works great, however, I can't figure out how to get it up on my publishers.I don't have direct access to the publishers and don't trust my sysadmins to configure the index there (especially over multiple publishers)--they also don't trust me with credent...

I'm stuck on a permissions issue.I have a folder for news stories, at /content/news/articles[year]/[month] that I need to be able to programmatically control access to. Each news page has an "author" property on the jcr:content node associated with a user, authors should only be able to edit their o...

You're right, the config was set to look for "person" but the actual value of the object class was "Person"