Welcome to BuddyDev forum.
Thank you for asking this. There is a catch and that’s why We haven’t implemented it. If we implement it in simple ways, Admins may reset the preference for the existing users(who already updated).
Is that ok? We want to go with all or nothing approach to use simple sql update. If we start checking for user preference and then updating, It will be a very resource consuming operations.
If the all or nothing approach is fine, please let me know and we will have it implemented.
Thanks for the quick reply.
For now it would be great to have the simple option as I am importing all of our users at once and then would be resetting all the preferences to no.
As for the resource intensive variant:
Would it slow the whole site to a crawl, or would it simply take some time to finish?
Thank you. I will have this option today 🙂
About the 2nd option, That depends on the size of the community. If there are 1000 users, It is not too much but if there are 100,000 users, then It will take a lot of time as we will have to check the preference for individual users if it is set or not and then update.
If we plan to implement it in future, It will be all about time as PHP scripts have time limit, the update will be like doing it in batches. So, It is not going to consume all resources but take a lot of time for the larger community.
Regarding the 2nd option, I would very much like this option as well. My community is a intranet site with about 100 users, so it does not sound like there will be much problem with resources or time to check the preferences.
Maybe implement this as well, but warn against using it on very large sites?
If you need betatesting, I am willing to help as I need to get this implemented as soon as possible on my site.
You must be logged in to reply to this topic.