@doekia Does this help ? https://stackoverflow.com/questions/38883285/error-the-update-operation-document-must-contain-atomic-operators-when-running

@julian basically the question popped while thinking of installing plugin-adsense (which does not worked at all for me btw - 1.11.2)

Hi, Due a massive reorganisation of my category tree I'd like to reset all user to be automatically subscribed to all categories. I have an adminMongo to manipulate the db Unfortunately my mongodb skill is close to nothing. Is there anyone kind enough to share the proper mongodb snippet to achieve such (either adminMongo or cli based. Thank you

@PitaJ said in How to the annoucements widget is done?: @The-Worms https://community.nodebb.org/post/64258 yes it's for the tags ;), But doekia's request is this view for recent topics : [image: btZ8Uyf.png]

@doekia Glad to hear the upgrade was completed with minimal issues

Thanks, it worked flawlessly

It happens that I setup the minimum password complexity to 2 and user are not able to use password like Ulllll#n Where: U mean an uppercase l mean lowercase # a special char n a number I managed to get the green flag at 16 characters. Sounds like the 2 complexity level is a bit overkill

I finally found the issue, it is related to the timestamp (score) when the user get registered. I did not realized that my import was generating wrong type of time stamp {score":{"$numberLong":"1454992330000"}} rather than {score":1.509408313172e+12} I finally run this fixup to cope with my issue: db.objects.find({_key:"group:registered-users:members"}).forEach( function(e){ db.objects.update( {"_id": e._id}, {"$set": {"score": 0+e.score}} ) } ); I hate this mongojs thingy

Thanks Julian. I was not too complicated but not having any data model made the process longer. I still have faced an issue with my converted users not been able to view the categories. I have manually addressed the issue by creating a "legacy" group, add the necessary group/priv to my categories and manually adding my users to the legacy group (fortunatly was having no more than 150 legacy users). I presume it has something to do with group association but haven't been able to figure out what exactly