When modifying a user via the api I wanted to use users.updated_at as criteria for the last update. Now I noticed that it is not set anew upon all actions. Eg, when changing watched categories or watch 1st post categories, it is not. Why not? I do add new users put users to groups delete users …

Watched categories are in their own table, so you’d need to check there, I think.

That would be category_users and there is no updated_at. Or is the category itself altered when a user sets it on watched?

It looks like you’re right and that there is no updated_at for the category_users table. I’m not sure how to solve your problem, you could create a user_custom_field that you updated via the API, I think.

Thank you Jay, that seems to be a workaround.

Users.updated_at no se renovó en todas las actualizaciones

Desarrollador

DDo (Dorothea Dorsch) 7 Mayo, 2020 12:49 3

Eso sería category_users y no hay updated_at. ¿O es la categoría en sí la que se modifica cuando un usuario la marca como vigilada?

Tema		Respuestas	Vistas
Change user registration date (created_at) via API Development rest-api	7	1475	28 Julio 2021
How to update Watched First Post Categories for all users? Support	3	952	8 Agosto 2019
User group 'muted categories' not updating members category notifications Support	1	306	1 Enero 2024
User profile watch/track/mute options not persisted Bug	11	1367	29 Septiembre 2017
Creating a topic or a post sends the user_updated webhook Bug	10	2172	23 Octubre 2017

Users.updated_at no se renovó en todas las actualizaciones

Temas relacionados