Unexpected results

[Tony-Thompson]

Hello Matt,

I have been using EZsearch successfully in various Umbraco deployments using the Text2 starter kit. Since upgrading to 7.2.6 with the Fanoe starter kit, the PreviewFields parameter in EZsearch no longer displays any content like it used to. Now it only displays the title of the pages it has found.

I tried changing the parameter from BodyText to Content but now it just shows layout code with the body text I am after embedded in it. Here's an example of what I see now as a search result:

Council Services
{ "name": "1 column layout", "sections": [ { "grid": 12, "rows": [ { "name": "Image w. text", "areas": [ { "grid": 12, "allowAll": false,

Do you know what the parameter would need to be to bring back the correct body text?

Thanks
Tony

[mattbrailsford]

Unfortunately the grid stores its value as json, rather than individual
properties on a node like in previous versions. Right now, there is no easy
way to extract content from the grid in a generic way so the grid (and any
other prop editor storing json) is not currently supported.
On 17 Jul 2015 4:04 pm, "Tony Thompson" [email protected] wrote:

Hello Matt,

I have been using EZsearch successfully in various Umbraco deployments
using the Text2 starter kit. Since upgrading to 7.2.6 with the Fanoe
starter kit, the PreviewFields parameter in EZsearch no longer displays any
content like it used to. Now it only displays the title of the pages it has
found.

I tried changing the parameter from BodyText to Content but now it just
shows layout code with the body text I am after embedded in it. Here's an
example of what I see now as a search result:

Council Services
{ "name": "1 column layout", "sections": [ { "grid": 12, "rows": [ {
"name": "Image w. text", "areas": [ { "grid": 12, "allowAll": false,

Do you know what the parameter would need to be to bring back the correct
body text?

Thanks
Tony

—
Reply to this email directly or view it on GitHub
#8.

[Tony-Thompson]

Thanks for the lightening response Matt. I'll have to think of another approach.

[mattbrailsford]

If you know the exact structure (or at least the grid editors used in your
grid) you good extend the bootstrapper in the App_Code folder to flatten
out the json into a more index friendly manor. Its just that's not easy to
do in a generic way within ezSearch.
On 17 Jul 2015 4:12 pm, "Tony Thompson" [email protected] wrote:

Thanks for the lightening response Matt. I'll have to think of another
approach.

—
Reply to this email directly or view it on GitHub
#8 (comment)
.

[SDmorgan]

I know this is an old post; however, the workaround that I made was simply to add a "summary" field to the doc type, places a summary of the article when posting, and then user this field in the previewFields property.

Hopefully this will make sense.