v0.5.0

First and Last name can be switched off on a form that asks for 英文姓名 and 中文姓名, and the member-detail fields from 0.4.0 now actually fill in.

Run indico db --plugin stsa upgrade after installing. This release adds a column. Until it has been run the plugin reads as nothing configured, the STSA pages in the management area say so, and the server log says so once per process.

Features

• First and Last name can be disabled. Once a form has an English name field, First Name gets the Disable button Indico withholds from it; once it has a Chinese name field, so does Last Name. A switched-off field is drawn with the disabled fields in the editor and is not asked of the participant — on the registration form or in Add registrant. A registrant's name is the English name followed by the Chinese one (Xiao-Ming Wang 王小明), which is what tickets, badges, e-mails and lists print.
  • The English or Chinese name must then be filled in; a registration without it is refused on that field.
  • The fields are not really disabled — Indico's database and core forbid that for a required name — so the switch is the plugin's own and the fields keep working everywhere else. See README §9 for why.
  • Deleting or disabling the English or Chinese field, or giving it a show if, switches the default field back on.

Fixes

• The member-detail fields did not fill in. Indico builds an identity's data through a whitelist of the user fields it synchronizes, so chinese_name, english_name, major and year_of_study were dropped at login. They are now kept, and a field is locked only when its claim arrived. A login that carries none of the four claims now logs the claim names it did carry, to tell a missing scope mapping from claims that are in the wrong half of the response. Members need to sign in again once for their details to be stored.
• The Add field dialog opened with a dead Submit button for the four member-detail types: the title was prefilled in a way that left the form pristine, and Indico keeps Submit disabled until the form changes.
• The draft kept across the login page no longer restores blank answers over the name and affiliation Indico had just filled in from the account.

Docs

README §8 now lists the four things that decide whether the claims arrive, including that Indico reads the ID token rather than the userinfo endpoint when the openid scope is used.