Page 2 of 2

Re: Prev/next page links do not adapt to filtered results

PostPosted: Thu Aug 14, 2014 1:52 pm
by wmoore
Yes, I was thinking the same thing.

Unfortunately there's no setting to enable this via the command line at the moment (seems we never got beyond a placeholder for PAGE), but you can go to
Code: Select all
lib/python/omeroweb/settings.py
and edit this:

Code: Select all
# PAGE: Used in varous locations where large number of data is retrieved from the server.
try:
    PAGE  # noqa
except:
    PAGE = 200


to something like:

Code: Select all
try:
    PAGE = 1000
except:
    PAGE = 200


then you'll need to restart web:

Code: Select all
$ bin/omero web stop
$ bin/omero web start


I've just tried this with PAGE = 1000 on my local laptop server and it seemed OK. PAGE = 2000 was a fair bit slower, but still loaded OK and filtering and search worked fine.
I guess the optimal size will depend on a bunch of factors.

Re: Prev/next page links do not adapt to filtered results

PostPosted: Mon Aug 18, 2014 8:55 am
by Sethur
Thanks Will, I changed the respective code section, I think this will temporarily alleviate our user confusion until a real fix is out.

Re: Prev/next page links do not adapt to filtered results

PostPosted: Thu Sep 11, 2014 1:16 pm
by wmoore
Just an update: Once OMERO 5.1 is released and you upgrade, you will be able to set page size in web via:

Code: Select all
$ bin/omero config set omero.web.page_size 500


Will.