Change Details

In the traditional skin, the available amounts when becoming a member are dependent on the address type (privat or company). Should this be the case with the new skin, too (not so in the delivery)?

In the traditional skin, the available amounts when becoming a member are dependent on the address type (privat or company). Should this be the case with the new skin, too (not so in the delivery)? The membership carries an inconsistency between the new UX concept and existing business logic (`FeeOptionSwitcher`) - formerly we had a component enforcing (indicating and only allowing select of valid) minimum membership fee depending on address type (private or company), amount, and payment interval. For these limitations of possible amounts to be logical to the user, address type and payment interval have to be selected before the amount (only valid amounts would be selectable). In the new layout [0], the form orders the fields as address type, amount, payment interval, which leaves the user in the situation that he/she involuntarily overrides his/her own values by choosing an invalid combination of payment interval & amount. How should we proceed T180941? - let use select payment interval before amount? - indicate to and let user only check valid payment intervals (depending on address type and amount chosen)? - other options? [0] http://artesansatwork.com/wikimedia/membership-index.html [1] https://github.com/wmde/FundraisingFrontend/commit/1451b96379a6d50cc25e913b13a8a4a00d8a5d06

In the traditional skin, the available amounts when becoming a member are dependent on the address type (privat or company). Should this be the case with the new skin, too (not so in the delivery)? The membership carries an inconsistency between the new UX concept and existing business logic (`FeeOptionSwitcher`) - formerly we had a component enforcing (indicating and only allowing select of valid) minimum membership fee depending on address type (private or company), amount, and payment interval. For these limitations of possible amounts to be logical to the user, address type and payment interval have to be selected before the amount (only valid amounts would be selectable). In the new layout [0], the form orders the fields as address type, amount, payment interval, which leaves the user in the situation that he/she involuntarily overrides his/her own values by choosing an invalid combination of payment interval & amount. How should we proceed T180941? - let use select payment interval before amount? - indicate to and let user only check valid payment intervals (depending on address type and amount chosen)? - other options? [0] http://artesansatwork.com/wikimedia/membership-index.html [1] https://github.com/wmde/FundraisingFrontend/commit/1451b96379a6d50cc25e913b13a8a4a00d8a5d06