I found database and can say, values are still existing in database xxxxx_social_fields_data, but options itself are totally gone from Database xxxxx_social_fields_options. So if i am adding a new value in backend with the old option name that shows in xxxxx_social_fields_data, it is showing before added user values.

So there is n loss of data, but it is a lot of work to re-add these field options and however this is a really strange behavior, because you don't know what field will disappear next…

I've tested several times and look for the code, it seems like the only possibilities I can think of is someone accidentally delete that checkbox field from the user workflow then click save.

What happen when it click save after remove one of the custom field from user workflow, it will remove that checkbox options value from this table #__social_fields_options but those user profile field value will still remain under this table #__social_fields_data .

And currently that is difficult to trace where went wrong since there do not have any proper step to replicate this issue, and I would suggest you that do the full backup on your current data from your database, if those checkbox options value missing, you still can able to import back manually into this #__social_fields_options table and update that `parent_id` column value to field id.

Hello Arlex, thank you for checking this. A good luck, that data remains, so i am a little bit more relaxed. But i am really sure, that nobody could have deleted these fields, because there is nobody working in backend than me… However i will keep an eye on this and come back to you, if i nee further help or can say something more accurate…

Best regards

Sure, keep us update then.