Hello Raymond,

That got me the results I needed to make the above corrections in the "#__social_fields_data" table. Thanks!

#1) However, I see that the list only includes about 1/3 of our users.

I could create a query to append additional rows for missing "uid" (user ids). But I'm not sure if it is okay to just create/append a new "id" in that table (add sequentially) or if the "id" field is pulled from another table?

#2) If I create new rows, the "field_id" is either "226" or "309".

I'm guessing those refer to the #__social_fields table where "id" #226 is "FIELD_CITY" and "id" #309 is FIELD_ADDRESS." But I'm not sure why one or the other is selected for the "#__social_fields_data.uid" field as neither indicates a country name.

Thanks. -- Rik

Hey Rik,

I would strongly suggest not to manually add rows as it may cause the site to break depending on how queries are constructed, or it could introduce some other issues related to incomplete data.

If users are not on the fields_data table, I believe it is because their profiles are not saved on EasySocial yet. So the right way to generate the data is by going into their profiles on EasySocial and saving them.

Hi Raymond,

I ran further queries and we actually do have a 1:1 correspondence in users between #__users and #__social_users.

So the only problem is that on the EasySocial dashboard where the Members Worldwide list only shows the countries for about 1/3 of our users. I suppose that is simply because we don't have country data on all users.

So no further action is required.

Thank you again for helping me get the current country data fixed. -- Rik

Sure Rik. You're most welcome.

Regards.