[SOLVED] Idea of improvement

Hi Nant,

Here is an idea of improvement/stuff that you guys need to clarify so that not knowledgeable people like me can understand it/use it easier.

I have over 200 different fields (on different conditionals). I am using userlists extensively and I have over 30 different of them. The sorting tab is ANNOYING since there is no "search" or data imput to search fields that one wants to sort about. I have to go through my 200 fields that are positioned at random to find the 2 fields that I am putting in sorting.

Would be great to know which value we should put into sorting. The one that is in DB or the translated one?

Field creation: the conditional tab under integration uses the translated names. A bit bad luck if you have several different cells named TYPE since you cannot differentiate between them (the database name is different but the translated name is the same... there are not many variations of "type" that users would understand)

Otherwise, only thing I have to more is that it would be great to have in the user list an option that the user can decide how they want to sort the userlists eg: munich.international-friends.net/useful-stuff/marketplace/clothes2

I have over 200 different fields (on different conditionals). I am using userlists extensively and I have over 30 different of them. The sorting tab is ANNOYING since there is no "search" or data imput to search fields that one wants to sort about. I have to go through my 200 fields that are positioned at random to find the 2 fields that I am putting in sorting.

It would be a select2 with searching if you didn't have so many fields. We disable the select2 if there's too many options, because it causes the JS from it to crash browsers. Until we can improve on the performance of our select2 usage it's how things have to function for now to avoid breaking backend usage entirely.

Would be great to know which value we should put into sorting. The one that is in DB or the translated one?

Sorting is extending the query directly. So it only sees the raw value stored in the database. We do not store translated strings, but always their untranslated.

Field creation: the conditional tab under integration uses the translated names. A bit bad luck if you have several different cells named TYPE since you cannot differentiate between them (the database name is different but the translated name is the same... there are not many variations of "type" that users would understand)

Install latest nightly CB Conditional and it'll display the field name instead of field title. Field name is always unique making it easier to find fields.

Otherwise, only thing I have to more is that it would be great to have in the user list an option that the user can decide how they want to sort the userlists eg: munich.international-friends.net/useful-...marketplace/clothes2

Sorting is planned in a later release, but you can accomplish that usage by having 2 userlists with 2 different sorting and displaying the userlist dropdown select.

krileon wrote:

I have over 200 different fields (on different conditionals). I am using userlists extensively and I have over 30 different of them. The sorting tab is ANNOYING since there is no "search" or data imput to search fields that one wants to sort about. I have to go through my 200 fields that are positioned at random to find the 2 fields that I am putting in sorting.

It would be a select2 with searching if you didn't have so many fields. We disable the select2 if there's too many options, because it causes the JS from it to crash browsers. Until we can improve on the performance of our select2 usage it's how things have to function for now to avoid breaking backend usage entirely.

Would be great to know which value we should put into sorting. The one that is in DB or the translated one?

Sorting is extending the query directly. So it only sees the raw value stored in the database. We do not store translated strings, but always their untranslated.

Field creation: the conditional tab under integration uses the translated names. A bit bad luck if you have several different cells named TYPE since you cannot differentiate between them (the database name is different but the translated name is the same... there are not many variations of "type" that users would understand)

Install latest nightly CB Conditional and it'll display the field name instead of field title. Field name is always unique making it easier to find fields.

Otherwise, only thing I have to more is that it would be great to have in the user list an option that the user can decide how they want to sort the userlists eg: munich.international-friends.net/useful-...marketplace/clothes2

Sorting is planned in a later release, but you can accomplish that usage by having 2 userlists with 2 different sorting and displaying the userlist dropdown select.

OK understood. Nightly will help greatly (was just trying to explain my frustrations that I experienced during the last 3 weeks and this will solve a great deal). Regarding the Sorting bit, would be great to have this in the tooltip or Nants video tutorials (too late for that I guess).

Still have the same problem. The list of 200 fields and I need to find the ONE that I need to put into that field. Would it be possible to sort alphabetically at least? That would make the job already loads easier since at least I would know where abouts I have to search for the field in the drop down table...

ie when select2 is switched off, could select1 at least be sortable alphabetically? I have spent my morning reading about 20 times through the list of fields and i have 200-300 more times to read through the whole list...

select2 is a jQuery powered dropdown select. There is no such thing as select1. select2 allows filtering because it entirely replaces the select with a custom HTML structure. You simply have too many options for jQuery to parse quickly. There is no solution except to reduce the number of fields you have or just use the dropdown as is until we can somehow improve the JS to handle such large selects.

You can quick jump in a select by clicking the select and pressing a letter (standard browser behavior, may vary depending on browser). It should jump to the first field with that letter. This maybe able to help you somewhat. The ordering is based off the fields actual ordering; there are no plans to change this.

I'm sorry, but for now it's go through your standard select options or lock your entire browser window. I believe going through your standard select options is better than it not working at all. I've added a bug ticket for this issue to investigate for a later release.

forge.joomlapolis.com/issues/5778

Yeah OK, shame. I have found a workaround and am hoping that it will serve other persons from this community. Here is the solution:

_I needed to do 30 different user lists and for those user lists I have 200 different fields.
_I needed about 8 to 10 different fields for each list.
_Using the field filters on Field management I UNPUBLISHED all the fields which I needed for the user lists.
_I then went userlist by userlist and only published the fields that I needed for that userlist using the Field management search to find the precise fields (instead of the drop down box).
_I was then able to use the search on the userlist fields (which was not available beforehand).
_After having done the userlist, I unpublished all the fields that I had previously published. IMPORTANT: Do not touch the userlists you have done already. They will show loads of empty fields. These fields will get populated again once you publish all the fields at the end.
_When you are finished: Publish all the fields that you have previously unpublished.

Timesaving in my case (estimated): 16-20 hours
Screams at computer saved: roughly 100

EDIT: Method works like an absolute dream. It takes me less than 3 min per userlist (instead of 30 min). I wish I had found this workaround beforehand.