|
Hi Dan,
well... main problem with those fields is that they are required fields... so IMO it isn't possible to keep them out (unless for some sort of anonymous backup ). IMO, by default, teachers shouldn't be able to backup/restore users by default. Or/and we can seed the password or... not really sure. I agree we must address that in some way, 100%. But backupping without password or email... sounds "incomplete" to be functional. Ciao fair enough - I wrote a custom hack to remove password/e-mail and a couple of other fields for OU's incremental backups - they want to ship out course backups to people to install locally and want to keep forum posts etc, but don't want the local installs to contain "private" information..... hence the removal of password and e-mail. - might need to keep it as a hack instead of getting something in core to handle this.
This will completed in 1.9.8, with caps to control creation of users and so on... moving...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
eg to allow users to be backed up, but to remove "email" fields from backups - probably also the "password" field?