09-22-2016, 05:59 PM
What about forms? What are people doing with the forms? I'm trying to think of how we can handle forms better in US5. Ideally, we could supply forms with the minimal required information on the join form. This would be things like username, first name, last name, email, password, etc. What if we made the join form fields and processing a 2 step process? The first step would input and process the minimal required information above. The second step (if needed) would be 100{3bc1fe685386cc4c3ab89a3f76566d8931e181ad17f08aed9ad73b30bf28114d} customizable by you. You would provide the set of fields for the form, as well as the PHP processing for said form. This would allow us to maintain a "hands off" UserSpice core, while still integrating your customizations into a non-awkward flow.
The problem this is trying to solve is the following: We supply UserSpice with a set number of form inputs and PHP processing. You want to add 1 or more fields to the join form. Right now, you have two options...modify the users/join.php form directly, along with the processing, or our presently preferred approach of copying it to usersc/ folder and modifying that one. The issue is that when we issue an update, that perhaps impacts the join.php page, and it means that we go through our own update, and then on top of that you need to then go through and update your copy of the form in usersc/.
The new approach described in the first paragraph would mean that our updates would only impact the UserSpice provide forms, and your forms remain untouched. When we issue an update, there is no need for you to change anything, it will execute and display your code as you defined it.
So what say the masses?
The problem this is trying to solve is the following: We supply UserSpice with a set number of form inputs and PHP processing. You want to add 1 or more fields to the join form. Right now, you have two options...modify the users/join.php form directly, along with the processing, or our presently preferred approach of copying it to usersc/ folder and modifying that one. The issue is that when we issue an update, that perhaps impacts the join.php page, and it means that we go through our own update, and then on top of that you need to then go through and update your copy of the form in usersc/.
The new approach described in the first paragraph would mean that our updates would only impact the UserSpice provide forms, and your forms remain untouched. When we issue an update, there is no need for you to change anything, it will execute and display your code as you defined it.
So what say the masses?