With something that affects all users in that respects, I tend to house that logic in a DB install script, version controlled, and walked through our testing process. Not saying your idea is bad, but we've had these requirements as well, and found that the DB rollback has been helpful to shield from mishaps.
What would the plugin do if a user already had a value, or would this only be for newly created profile attributes. Perhaps a default this value on the create profile attribute screen?
We have a specific problem in that we need to set the 'jiveLocale' user
property for each user to 'de_DE' because of a locale bug that exists.
I think the feature could easily be implemented as a checkbox in the
property form that states 'for all users'.
Or alternatively add user filtering and selection methods to which an
action can be applied. Latter process is the more standard
implementation with most applications.
One can always store a 'reverse script' for this and since these only
concerns properties and not records it is not a fatal impact if
something does 'go wrong'.
I think that such a feature would be helpful especially in larger
networks as I can't imagine managing single user accounts in a community
of 100,000+. That would mean 1,000 people pages. I would need direct DB
access to issue queries and manage data.
Thanks for the clarity. I totally agree with the need to have tools to manage communities of 10-100k+, and think that your suggestion of a user-selection criteria search would be the missing piece. One other consideration, if the use-case is a "bug" that is driving this needs, perhaps you can create a filter to do on-demand updating/processing of User properties as they log in to the site. This might be just as easy in one-off scenarios such as this.
Best of luck, =)
well we are utilizing a fully hosted solution of yours so we have no
access to the database etc. if that is what you mean.