Since you got your hands full already, I thought I would throw another idea pass ya.
If you use the ®Type=`verify` option, your thought is that for someone to register to your app, is that they have to have a valid email address in order to receive the password. We also eliminate the email address validation process. Why do we show this new registration as a member before they actually receive this password and login to make sure they are an actual person? My thought is that we should not even acknowledge this registration until they login with the correct password.
Why am I bringing this up? Do a test registration and do not complete the registration, then click your members link.
This snippet will make MODx something it needed a long time ago, lol! Keep up the good work mate!
Mark
Some features I´d like to see (perhaps it´s already possible)...
Userlist:
- Possibility to sort by request (Click on table header sorts the clicked column e.g.) - For example ...userlist.html?sortBy=username&sortDir=ASC sorts by username in ascending order
- Pagination
- Search form for custom fields (like TV-Explorer) and generated userlist. E.g. usersearch.html?searchby1=username&result1=john&searchby2=city&result2=chicago finds all users with name "john" in Chicago.
Is this understandable?
Would be great!
@marc:
Those are all good ideas and all will be considered for the next release.
-sD-
Dr. Scotty Delicious, DFPA.
ScottyD,
One feature I think would be great is to allow the user to add additional items.
I am working on my churches site and one field that we want is to be able to list the children’s first name and age. Some families don’t have kids, some have three, some 6...see where I am going with this?
It would be nice to allow a default field of "Child name" and then be able to enter the birthdate for that particular child. Then give the user the option of adding another "Child and b-date" field.
Is this possible? I’m sure it could be extended into multiple other fields too...
THanks for all the work!
-
☆ A M B ☆
- 24,524 Posts
I was working on a similar site, and I must say that the idea of having such potentially sensitive information on a Web server, especially a commercial shared hosting server, made my hair stand on end. I convinced my client that such information would be much better kept in a local database with no Net access, or a proper firewall to keep the local database secure. Web servers do get cracked, and I will never store credit card or children’s information on one, unless it’s a private dedicated server and the server admin knows what he’s doing about securing the server. And even then, look how often major business servers get cracked and user data gets posted on the Web!
@Susan,
There would be no personal information such as SSN or identity numbers, as this would just have their first name of the child and DOB possibly, maybe even just allow for the month and year of birth without the actual date in order to calculate the age.
Would you still recommend that they do that, or what information can I relay to them that they should and shouldn’t put into a private members directory? Some help here would be great as they already have this information in a db on their current site.
