B_Stockwell

Re: Improving a query, ordering by multiple items in query--not seeing a difference. - Adobe Experience Manager 03-08-2022

Ok, that clarifies some things. I was hoping this could all be done in the query so I could pass results directly to the front end, but sorting the result set is pretty easy. Thanks.

Re: Improving a query, ordering by multiple items in query--not seeing a difference. - Adobe Experience Manager 03-08-2022

HI Arun, Apologies for not being clear. We want more or less a "best match" that would first sort by # tags matched, then a subsort by display date 1st sort: # of matching tags desc 2nd sort: display date desc For 7 stories: Story A: tags: a,c | displayDate: 4/1/22 Story B: tags: a,b,c | displayDate: 7/1/22 Story C: tags: a,b,c | displayDate: 3/1/22 Story D/: tags: a,b,c | displayDate: 6/1/22 Story E: tags: a,c | displayDate: 8/1/22 Story F: tags: c | displayDate: 5/1/22 Story G: tags: d | displ...

Improving a query, ordering by multiple items in query--not seeing a difference. - Adobe Experience Manager 02-08-2022

Hi Everyone, I am working on a project improving the search results for a "related stories" component in our news system. Here is a simplified query that shows how our current search functions. path=/content/uc/news/articles type=cq:Page tagid.1_value=topics:student-experience tagid.2_value=colleges:nursing tagid.3_value=helpful-marketing:current-bearcats tagid.4_value=helpful-marketing:student-life tagid.property=@jcr:content/cq:tags tagid.property.and=false orderby=@jcr:content/dispDate orderb...

Activating a page with mixed permissions - Adobe Experience Manager 18-04-2019

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, for example, someone in our college of admissions may want to share a document or image managed by our financial aid office that is already live, (such as tuition data, which is determined well in ad...

687

Re: Querybuilder throws stackoverflowerror on very large query (6.4) - Adobe Experience Manager 22-03-2019

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 11:50:02.207 *ERROR* [10.11.54.18 [1553269802169] GET /content/uc/news/articles/2019/01/n2058588/jcr:content/news-bottom/responsive_section_2/par/newslist.html HTTP/1.1] com.day.cq.wcm.core.impl.WCMDeb...

10.7K

Re: Querybuilder throws stackoverflowerror on very large query (6.4) - Adobe Experience Manager 22-03-2019

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.

10.7K

Querybuilder throws stackoverflowerror on very large query (6.4) - Adobe Experience Manager 22-03-2019

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 other queries on 6.2, and I believe the error is coming in the initial processing of the query, and not the running of the query--If I test in 6.2 and copy the generated xpath query, I can then run th...

11.1K

Custom Handling for page name collisions - Adobe Experience Manager 09-11-2018

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 try to create stories at the same time, which would result in a "1" being appended to the end of the node name. But it's not 100% effective, and each time it happens the ID grows b an order of magnitu...

606