Thalia 8de5b4e1aa Improve workflow for protecting filters with protected variables ... Why: * Protected variables were introduced to support temporary accounts so that temporary users could be filtered based on their IP address. * Filters that use protected variables are protected in order to preserve privacy. This can't be undone. * The current workflow for protecting filters is to have a 'protect' checkbox that can be checked for any filter, even one without protected variables, to the discretion of the editor. This has led to mistakes (see T37765). What: * Do not show the 'protect' checkbox on the form by default. Instead, show it when saving a filter with protected variables, after form submission. The user must check it to save the filter. * Still show the checkbox in a disabled state with a warning message if a filter is already protected, so that the editor can easily see it is protected. Bug: T377765 Change-Id: Ie5c94ac1399860ccdca4482508dd37ff07309764		2024-11-14 18:24:27 +00:00
..
parserTests	Support named capturing groups in get_matches()	2024-09-07 11:25:48 +00:00
parserTestsEquivset	Move parser tests to /unit	2019-08-28 16:36:37 +00:00
phpunit	Improve workflow for protecting filters with protected variables	2024-11-14 18:24:27 +00:00
selenium	Update Selenium tests to obtain correctly element	2024-09-20 14:40:46 -07:00