Why not focus on useful things?

[iconnor]

I can reproduce it.

We have tried many things to make this work, and none have worked. I think in the past the issue was actually in the bootstrap-table code. I just retried though and it seems to be working.

@Igor100 FYI in the past, we set the data-page-size attribute. This reset the value on every page load. So then we tried setting the cookie ahead of time. That seemed to work at the time, but in today's testing, it didn't.

[IgorA100]

If I change the dropdown to 100 events per page, the cookie zmEventsTable.bs.table.pageList with the value 100 appears.

That's right.
The next time you visit the Events page, you should see 100 events on the page.

[IgorA100]

I can reproduce it.

How can I reproduce this problem?
I can't

[iconnor]

Please note that the cookie is wrong, it should be zmEventsTable.bs.table.pageSize but that doesn't work either.

@Igor100, got events, check the cookies, etc.
Clear cookies, hit reload. It should ask you to re-login, then go right back to events list, and it should default to 10. Or today's build should default correctly to 50.

[Detlef Paschke]

... Or today's build should default correctly to 50.

Hello,

I just updated and tested it.
If I come with "washed feet" (cookies, browser cache all empty and therefore no cookies on the PC), the configuration under WEB_EVENTS_PER_PAGE is first applied. I think that's exactly right.

If this were also the case for Log (where you still start with 10 entries), it would be perfect.