WorldServer - The "Search" button has disappeared from my "Users" page or other pages and/or I cannot sort by column anymore

In the Users page in WorldServer I cannot perform a Search or create a filter because the Search button has disappeared or my Search filter does not bring up on visible results.
The same behavior might appear on other pages such as Projects, Quotes, Issues, Project Types, Translation Memories etc.

Another symptom could be that you are not able to sort certain columns corresponding to custom project attributes.

Resolution #1:

1- On the server where WorldServer is installed, go to WS_CONFIG/ws-legacy and open the general.properties file.
2- Change/uncomment this setting in the general.properties file on the server where WorldServer is installed. The default setting is 300 and is commented out. For example, change the default to the number of rows that you want to be visible on one page, for instance, 500 or 1000. In this example, change:

#page_row_limit=300
to
page_row_limit=1000

If you do not find this property in the general.properties file, just add it.

Note: this change is global and will be applied to all pages.

This will change the number of visible rows from 300 to 1000 (following the example above). You can change this to a lower or higher number as well.
3- After the change, save general.properties and restart WorldServer (Idiom Service).

Important: if you are working in a clustered server environment, make sure that the changed value is the same on all general.properties files under the WS_CONFIG/ws-legacy folder present on all servers where the WorldServer (or Idiom) Service is running.

If the change still does not help for certain users, ask the user to go to Tools > Personal Preferences and change the value set next to Number of rows per page in tables to match the one from the page_row_limit or a value as high as needed. But it should not be higher than the one in page_row_limit because it would not make any difference. 



Number of rows per page in tables: 999

Click Save to save your change.

Note: Although making the change under the ws-legacy folder should be sufficient, for one of our customers, for the page_row_limit value to work successfully, the general.properties file needed the changed entry in all the locations below:
 

WS_CONFIG\general.properties
WS_CONFIG\ws-legacy\general.properties
WS_CONFIG\ws\general.properties
tomcat\webapps\ws-legacy\WEB-INF\classes\config\general.properties
tomcat\webapps\ws\WEB-INF\classes\config\general.properties

Resolution #2

This change can also be done on the fly in the browser via ws_gate without needing to restart the WorldServer/Idiom service. However, remember that with this method, if a WorldServer restart is done, this change will be reverted to the default value. If you want this change to be permanent, change the value as described above in resolution #1. Here is an example of making this change on the fly:

1- Go to the Assignments page and check the URL, for example:
 

The default page row setting is too low for the number objects associated with the page, i.e. the number of users or Translation Memories exceeds the set page row limit and needs to be changed in general.properties or using ws_gate method.

This article might be relevant:

WorldServer - How to display more than 1000 rows in any page (Projects, Tasks, Browser Workbench, Translation Memories etc)