Displaying more than 200 assets with asset publisher ADT?

RE: Displaying more than 200 assets with asset publisher ADT?

2019-02-24T10:28:07Z

Thanks David. We finally decided to rewrite the ADT as a portlet.

Fernando

RE: Displaying more than 200 assets with asset publisher ADT?

2019-02-14T21:02:09Z

The problem is that asset publisher can have performance issues; unlike most others, it generally relies on the asset publisher, ADTs and interpreted templates necessary to render itself.

The limit on 200 is used to prevent against bugs opening on slow performance when trying to render, for example, 600 assets.

It tends not to work well on mobile browsers, some desktop browsers w/ so much content, ...

200 limit is there to protect you.

Displaying more than 200 assets with asset publisher ADT?

2019-02-14T18:28:25Z

Hi all,

I'm in Liferay 7 CE ga7 and we have use case where we have aprox. 600 assets needing to be displayed at the same time (points in a map, if you want to know).

We're trying to do this with a structure, asset publisher and an ADT. It stops at 200.

Looked around, there's a parameter called search.container.page.default.deltaand another called asset.filter.search.limit but they're being ignored for more than 200.

Apparently it might be because of this piece of code in SearchContainer.java, where MAX_DELTA is hardcoded to 200:

&nbsp;&nbsp; &nbsp;public void setDelta(int delta) {
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;if (delta &lt;= 0) {
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;_delta = DEFAULT_DELTA;
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;}
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;else if (delta &gt; MAX_DELTA) {
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;_delta = MAX_DELTA;
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;}
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;else {
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;_delta = delta;
&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;}

&nbsp;&nbsp; &nbsp;&nbsp;&nbsp; &nbsp;_calculateStartAndEnd();
&nbsp;&nbsp; &nbsp;}

Anybody has a workaround for this? (besides abandoning asset publisher and creating a portlet?) Something like fetching the next page in the ADT?

TIA

Fernando

P.S.: if someone could explain why the hard-coded value set at 200 it would also be interesting. ;-)