livesitecs-demo targeting component is returning empty records ($)

Version: 7.2.1
Platform: RH Linux

LiveSite Content Services demo spar is installed and deployed to runtime. The strange behavior with it's targeting/rule component (Display Hero Promotion.component) working on TeamSite preview however not working on Runtime. It is returning with blank record ($). Rest all the components are working fine.

I tried to replicate same pages in new site but now it is failing on both TeamSite and Runtime for the same Display Hero Promotion component.

LSCS url query is building properly like below:
/lscs/v1/document/$?q=(TeamSite/Metadata/ContentCategories:="fyhme1rp")+AND+(TeamSite/Metadata/ContentType=fyhme1ro)&start=0&max=10&project=//domain/default/main/livesitecs/demo&format=json

This query is returning records on Auth while same query is giving empty on Runtime.

In LSCS-RT, if i remove "=" from query then it is returning records:
/lscs/v1/document/$?q=(TeamSite/Metadata/ContentCategories:"fyhme1rp")+AND+(TeamSite/Metadata/ContentType=fyhme1ro)&start=0&max=10&project=//domain/default/main/livesitecs/demo&format=json

I tried to debug various thing, only thing i found difference in "site" between preview and runtime that in LSDS Runtime log showing error at end of page rendering "error- Site not valid" with not exception, but site is running fine and except targeting/rule component everything works properly.

Thanks.

Find more posts tagged with

Comments

Rick Poulin

In LSCS-RT, if i remove "=" from query then it is returning records:
/lscs/v1/document/$?q=(TeamSite/Metadata/ContentCategories:"fyhme1rp")+AND+(TeamSite/Metadata/ContentType=fyhme1ro)&start=0&max=10&project=//domain/default/main/livesitecs/demo&format=json

I'm not familiar with the demo site, and I'm puzzled as to how the query isn't parsed the same on both sides, but that's definitely not the right syntax. Both '=' are wrong in the metadata matching. It should be using this:

/lscs/v1/document/$?q=(TeamSite/Metadata/ContentCategories:"fyhme1rp")+AND+(TeamSite/Metadata/ContentType:fyhme1ro)&start=0&max=10&project=//domain/default/main/livesitecs/demo&format=json

If it's using an OOTB class, well, that's just plain broken. Instead of trying to fix it, you might as well just ignore this part of the demo spar and write your own if/when you need it.

Faizi

I'm not familiar with the demo site, and I'm puzzled as to how the query isn't parsed the same on both sides, but that's definitely not the right syntax. Both '=' are wrong in the metadata matching. It should be using this:

I got information from support site that ":=" operator used for exact match.

If it's using an OOTB class, well, that's just plain broken. Instead of trying to fix it, you might as well just ignore this part of the demo spar and write your own if/when you need it.

Yes, this is OOTB classes for executing "rule-engine" from LSCS context.

Rick Poulin

I got information from support site that ":=" operator used for exact match.

Well that's wonderfully absent from the docs.. nice. It also violates standard URI structure (unless escaped as %3D), so.. yay?

Still doesn't explain the missing colon from the second part of your match though.

Faizi

I found the issue was with metadata deployment to LSCS database. The ContentType and ContentCategory metadata value was not deploying in proper format in "ea" table.
And LSCS indexer index the same thing so when exact match query (:=) was not working.

1.png

2.png