When I have more than 50 keywords and want to assign them from different
pages in the keyword picker window, the list of keywords gets cleared
whenever I switch to a different page. So, I end up with the ability to
choose only keywords from one page, which is of course inappropriate.

I am experiencing the same issue. Was a solution found?

James, thanks for pinging here.
You are using the latest version of roundup I assume?
Do you expect the problem to be web browser specific?

Bernhard

I can recreate the problem with rev4645
and chromium v13.0.752.0 .

The problem is also there with the item list of the superceder,
so it is a more generic problem with the javascript classhelp windows.
The more complex one for the users works, though.

A dirty and limited workaround would be to raise the pagesize in the 
template in the classhelp link to over 50, so someone always gets all 
entries on one page.

However this javascript issue should be fixed of course
and the user dialog shows that it is possible.

Bernhard, I have just returned from my Summer holiday so sorry for not
responding earlier. I inherited responsibility for a Roundup Issue
tracker which was customised approximately 2 years ago for our company.
The Issue tracker is deployed in 2 sites, with only one site having so
far exceeded 50 keywords. I came to similar conclusions as you in 
msg4409, and have already increased the pagesize for keywords as a
temporary measure.

I am a beginner with respect to Roundup. I assume that it would be a
good idea for me to obtain the latest Roundup source code and to bring
our Issue Trackers up to date.

James, in general it is always a good idea to upgrade roundup
to the latest stable version. If you need help for considering this, I 
would ask on the roundup-users list.

For this particular issue an upgrade would not help of course
as it is still persistent within the current version. :)

Still an issue with Roundup 1.5

As a workaround we increased the page size from 50 to 500 in our local
installation, but of course this is not a real solution.

This is the same as: issue933936 opened by richard, so this has been
around for a while. Closing that issue with this issue as the superseder.

This is still an issue for the 1.6.0 release.

We have a user specific solution for the selection problem in
fast-decomposed. It seems that it can be used for generic with small changes (removing the search part).
Perhaps this is useful for the main branch templates.

Hi Ludwig:

I took a look it seems the major change is to _generic.help.html.

at the top of that file I see this inside tal:define:

  qs request/env/QUERY_STRING;
  qs python:'&'.join([a for a in qs.split('&') if not 
a.startswith('@template=')]);

I assume the first qs is incorrect? I think the last definition is the 
one that's used.

I hope to have some more time to look at it this weekend.

Thanks for your suggestion.

-- rouilj

* John Rouillard <issues@roundup-tracker.org> [20191116 02:56]:
> I took a look it seems the major change is to _generic.help.html.

This is user.help.html with minimal changes.

> at the top of that file I see this inside tal:define:
> 
>   qs request/env/QUERY_STRING;
>   qs python:'&'.join([a for a in qs.split('&') if not 
> a.startswith('@template=')]);
> 
> I assume the first qs is incorrect? I think the last definition is the 
> one that's used.

This is the same in user.help.html, the second line inclused "qs" on
the right side of the assignment.

Both lines could probably (=untested) be combined into a long one:

   qs python:'&'.join([a for a in path('request/env/QUERY_STRING').split('&') if not a.startswith('@template=')]);

but I'm not sure that this is better :)

Just a note that I have students in a graduate software engineering capstone
project class working on a web component to wrap/replace the classhelper. It uses
the REST interface to allow paging through multiple blocks while keeping
the currently selected items.

The github repo is: https://github.com/UMB-CS-682-Team-03/tracker