Changes between Version 3 and Version 4 of AppFiltering


Ignore:
Timestamp:
Dec 24, 2007, 1:31:51 PM (17 years ago)
Author:
davea
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • AppFiltering

    v3 v4  
    1 [[T(Incomplete)]]
    21= Application filtering =
    32
    43You can allow users to select which applications they will receive work for
    5 (by default, they may receive work for any or all applications).
     4(by default, they may receive work for any application).
    65
    7 This information is stored in the [ProjectSpecificPrefs project-specific preferences],
    8 and you must provide your own interface for editing it.
     6This information is stored in the [ProjectSpecificPrefs project-specific preferences].
    97Each 'allowed' application is represented by an element {{{<app_id>N</app_id>}}},
    108where N is the database ID of the application.
    119If no {{{<app_id>}}} elements are present, the user may be sent work for any application.
     10
     11The sample PHP file for project-specific preferences
     12supports application selection, but it is commented out by default:
     13{{{
     14if (false) {
     15    $app_array = array(
     16        array(1, "Application one"),
     17        array(2, "Application two"),
     18    );
     19} else {
     20    $app_array = null;
     21}
     22}}}
     23
     24To enable it, change the 'false' to 'true',
     25and add your own list of application IDs and names.
     26
     27If you use application filtering,
     28be aware that currently there is no easy way to cancel it:
     29users who have non-empty app lists will continue to
     30be filtered even if you remove app filtering from your PHP code.
     31The only ways to fully undo app filtering are:
     32
     33 * write a script to remove all <app_id> elements from the XML in the database
     34 * modify the scheduler so that it takes a configuration flag turning off app filtering.