Hi, This is more of a feedback thing than anything, but the default setting of Auto-assign new items to a site being checked is, in my opinion, a poor decision. When managing lots of sites, inevitably someone fails to turn it off, and their site gets polluted with unintended items. It’s at the point where I’m considering writing a module or a patch with the singular purpose of changing this setting. That said, I get the feeling I’m not alone here; if this is a common sentiment among the community, I wonder if, in a future version, the default could be changed…
2 Likes
So, this default is there to cater to the significant portion of users who don’t really use multiple sites, to make it so they don’t have to interact with the assignment system and all that. I don’t think we’re likely to completely drop this default behavior.
For people who are making sites more regularly, I can think of a few options. There could be a “default default” kind of setting, so a global setting that controls whether new sites from that point on have auto-assign enabled by default. There could also be something more automatic, like the auto-assign only get auto-enabled for the first site, though I’d be concerned that would lead to some confusion and not really be a great idea.
The global setting approach seems the most likely to me. It would be a little bit of a cousin to the existing settings that control whether new items and other resources default to public.