Gravatar for kevin.bernaerts@amplexor.com

Question by kevin bernaerts, Jun 6, 2014 8:27 AM

omnibox excerptLength seems to get ignored

When I set the excerptLength property, I can see the parameter being sent over to the backend (using firebug), however the server doesn't seem to take it into account. I still get excerpts of 200 chars.

var builder = new Coveo.Ui.QueryBuilder();
builder.expression.add(q);
builder.excerptLength = 100; // gets ignored
var query = builder.build();
query.excerptLength = 100; // gets ignored

var searchDeferred = Coveo.Rest.SearchEndpoint.endpoints["default"].search(query);

populateOmniBoxObject.rows.push({ deferred: deferred });
searchDeferred && searchDeferred.done(function (data, status, jqXHR) {
if (data.results.length > 0) {
    for (var i = 0 ; i < data.results.length ; i++) {
         data.results[i].excerpt // still 200 chars long !
    }
}

Is there some additional configuration to be done in the backend too ?

1 Reply
Gravatar for olamothe@coveo.com

Answer by olamothe, Jun 6, 2014 10:17 AM

I'm guessing you are using the REST API that is installed with the Front End .NET/standard install kit ? (Meaning: not the standalone java service)

Can you tell me which version of the Front End.NET you have installed ? Looks like a bug that was fixed in the March release (12.0.664).

The excerpt length property was not properly passed when using the REST API bundled with the Front End .NET

Gravatar for kevin.bernaerts@amplexor.com

Comment by kevin bernaerts, Jun 6, 2014 11:59 AM

I know we will soon be using version 12.0.777 (an upgrade has been scheduled) but I'm not sure which version we are using now. Let me come back to you about that.

Gravatar for kevin.bernaerts@amplexor.com

Comment by kevin bernaerts, Jun 11, 2014 3:13 AM

I've just verified and indeed we're currently using a version prior to .664 --> .614

Ask a question