02-05-2016, 08:16 AM
Hi, I've just recently upgraded from usercake to userspice. Outstanding job! Looking forward to the next development (where are those snazzy looking graphs by the way - are they hidden somewhere?).
I'm glad about the move to PDO and keeping userspice files clearly separate (my project already has a custom.css and font-awesome library which forced me to think during the last upgrade). These seem to be the most important to me personally.
Keeping in mind that usercake/userspice started as a 'base-level' that developers could modify, there are only a few things I could think of to suggest:
(1) configuring when recaptcha should be/shouldn't be applied: everyone seems to ask for disabling recaptcha, but there may be parts of a project that needed, and parts that don't. In my own circumstance, I have two forms for signing-up users. One is public, and the other is private (only available to a type of authenticated user). I would like to enable recaptcha on the public pages (public login and public sign-up) and disable on selected private pages (the private sign-up page).
(2) some easy configuration of the email activation or some more documentation on it. At the moment people need to hunt around for info how that works.
(3) allow administrator to trigger a password reset. I'd like the ability to prompt a selected user to change their password on their next login. This would be handy for a number of scenarios. In my case, my system has an 'executive teacher' that makes their class lists for 2016 in Dec 2015. They need to add a new teacher to the system before the teacher starts working at the school (they may only be starting in the school in 2016). So the executive teacher signs-up the new teacher in advance and then configures information about that new teacher's class. It would be great if the first login of the new teacher triggers a request for a password reset. (or some other solution to that long-winded problem)
(4) a nice upgrade experience: upgrading to userspice was ok, but two things stood out.
(a) The password strengthening experience. For a future release, could there be the option of a staged approach? E.g. stage 1: make 1 modification that prompts a password reset among the userbase (get the stronger password into the system), stage 2: administrator deals with those who have not strengthened their password with a manual process, stage 3: upgrade the rest.
(b) Integration into existing systems. The userspice system is great for the lovely styling with bootstrap and fontaweome. For existing projects that don't use these frameworks, integrating upgrades would be easier if a few 'bare bones' templates (sign-up, login) and the success/error messaging system was totally independent of the presentation/styles (e.g. currently funcs resultBlock is echoing out div tags).
5. Admin option to use email address instead of username (or allow username to be an email address?).
6. Adding, removing fields. Its not too hard right now, and I can understand why some hard coding is required.
Just some thoughts to help with your dev process. Great work and good luck.
T
I'm glad about the move to PDO and keeping userspice files clearly separate (my project already has a custom.css and font-awesome library which forced me to think during the last upgrade). These seem to be the most important to me personally.
Keeping in mind that usercake/userspice started as a 'base-level' that developers could modify, there are only a few things I could think of to suggest:
(1) configuring when recaptcha should be/shouldn't be applied: everyone seems to ask for disabling recaptcha, but there may be parts of a project that needed, and parts that don't. In my own circumstance, I have two forms for signing-up users. One is public, and the other is private (only available to a type of authenticated user). I would like to enable recaptcha on the public pages (public login and public sign-up) and disable on selected private pages (the private sign-up page).
(2) some easy configuration of the email activation or some more documentation on it. At the moment people need to hunt around for info how that works.
(3) allow administrator to trigger a password reset. I'd like the ability to prompt a selected user to change their password on their next login. This would be handy for a number of scenarios. In my case, my system has an 'executive teacher' that makes their class lists for 2016 in Dec 2015. They need to add a new teacher to the system before the teacher starts working at the school (they may only be starting in the school in 2016). So the executive teacher signs-up the new teacher in advance and then configures information about that new teacher's class. It would be great if the first login of the new teacher triggers a request for a password reset. (or some other solution to that long-winded problem)
(4) a nice upgrade experience: upgrading to userspice was ok, but two things stood out.
(a) The password strengthening experience. For a future release, could there be the option of a staged approach? E.g. stage 1: make 1 modification that prompts a password reset among the userbase (get the stronger password into the system), stage 2: administrator deals with those who have not strengthened their password with a manual process, stage 3: upgrade the rest.
(b) Integration into existing systems. The userspice system is great for the lovely styling with bootstrap and fontaweome. For existing projects that don't use these frameworks, integrating upgrades would be easier if a few 'bare bones' templates (sign-up, login) and the success/error messaging system was totally independent of the presentation/styles (e.g. currently funcs resultBlock is echoing out div tags).
5. Admin option to use email address instead of username (or allow username to be an email address?).
6. Adding, removing fields. Its not too hard right now, and I can understand why some hard coding is required.
Just some thoughts to help with your dev process. Great work and good luck.
T