Hi,

How are those users created? From on fresh installation of EasySocial with existing users?

Yes, those are "old users" who signed up before EasySocial has been installed. Then of course I installed a fresh install of ES when I started out last December.

Hi,

It seems like the field data is storing the username instead but the name data is retrieved separately.

Could be a bug from previous release.

I will have to perform a maintenance script on your site to set back the name accordingly. Is that ok with you? if you are ok, please make a backup of the table prefix_social_fields_data, and then I will execute a script to repair this on your site.

Keep in mind that the access is to my test site. (hence why the sub-domain is test) So yes, you have my permission to do that. My test site is made for the sake of trying out stuff to see what breaks what.

The reason I did not give you guys my main site is because I set things up in a very particular way. Changing options and such is no problem on the test site. And of course I can give access to my main site when we are sure we know what the changes will do.

Thanks Jason for looking into this, let me know when the changes are made.

Hey Jason, just giving you a reminder about this issue. No need to apologize, I been busy these days too. In case you wanted a direct answer to your question, yes, perform whatever script you would like. It is my test site after all.

Hi Josh,

Oops missed this thread!

If I were to run a maintenance on your test site, will it get then get copied over to your production site? Because data changes on test site seems useless.

Ah, I see what you mean. My test site is a 100% separate from my main site (both database and files). I take it this is a issue that probably only effects my site due to some scenario? Note that I have made two new users since I've installed ES, when I edit the new profile, it still duplicates from the username still.

So with making a backup of my main site will I need to do both a sql and file backup? Or only one?

Hi,

Ahh I think I've identified where the issue is.

It seems like this is only affected if the user is created through other registration except EasySocial. Can you confirm this for me?

I tested by creating 2 users, 1 through native Joomla, 1 through EasySocial users page. The one that is affected is if a user is created through native Joomla.

Luckily you are using the Single Name settings for Fullname field. To be honest with you if your fullname field is a splitted name format (First, Middle, Last), those data are not recoverable.

I will patch this issue internally.

As for your site's data, I will have to run a diagnostic PHP script to recover the name data (in which I will need your production site's access, and it will take less than 5 minutes to do this). You will only need to back up the table prefix_social_fields_data

You are correct. The issue only seems to happen when the user signs up from Joomla rather than EasySocial (I created both types of users to confirm this).

As for the single name field, I figured it was safer to use Joomla's method for the name. Plus some people have two middle names, some have two first names and zero middle names! I have had friends with both those scenarios which I try to keep things as flexible as possible while attempting to create the fewest amount of issues.

Attached to this post is my production site ftp/admin account access. I give this info only to folks I really trust, the Stacked team has certainly won that. When your done with the script, I would like it removed unless it helps with future scenarios. The reason being that I try to keep as few files as possible, especially when it comes to scripts that do things. I have backed up my jml_social_fields_data table. You now have my permission to use the script and do what you believe is necessary for this issue. Because it's my production site, don't change too many settings. But do please change any that you feel would help solve this.

Any news on the situation Jason?

Hi,

Too many things to do, sorry about that.

Anyway I've found an easier way to do this, by just executing a line of sql to clear out all the invalid names. The field already have a logic to automatically fallback to the native Joomla's name stored in the table. So no maintenance script required.

I've also patched the part where user created through outside of EasySocial gets assigned with Username issue.

Don't sweat it Jason. I know that ES 1.2.8 is a little more than a casual release in terms of things to fix. You guys are doing great, don't let anyone tell otherwise.

Anyways, thanks Jason for solving this. I'm curious if this patch will be included in the future of ES. Not that I personally need it, but it might help others who run into this situation.

Keep rocking, ES is becoming more than just an amazing extension. It really does mean a lot to us.

Hi,

I can't tell you how much I appreciate your support and kind words.

Yeah this patch will be included but the maintenance part however have to be carried out manually so I will do that on per user request basis.