Self-Hosted Latest Rev WP Showing My REAL NAME Rather Than My 'Display Name As'

Broken Link Checker PASSED (is good without the issue resurfacing)

I use Better WP Security and it probably wouldn’t cause the issue you are having. Keep investigating. ??

Aaaaaaaaaaaaaaaaaaaaaah…. I FOUND IT !

Jetpack by WordPress.com Version 2.7 | By Automattic

I JUST ENABLED IT AND boom, THERE’S MY ISSUE!

Man, and I really love that one… OK, it’s time to go through my JetPack settings…. (crap) I would REALLY HATE to lose this one….

If you really want to keep Jetpack, contact the plugin author and explain your issue.

Ok, it looks like maybe my best and most efficient way to solve this issue is to make a new www.ads-software.com account being very careful about the information I’m giving and then disconnect all my blogs from jetpack and reconnect them to the new account. Let me try that. I’ll report back here my results.

Ok, as soon as I disconnected jetpack from wordpress.com then my name went back from my real full name back to what it is set at and should be on my blog (just for added information)

Now I’m going to make a new wordpress.com profile as I mentioned in the above post.

Ok, I made a completely and entirely new wordpress.com account and then connected jetpack on my self-hosted blog to the new wordpress profile and it immediately made my issue reappear.

The only things I can think of are 1) it’s an unintended JetPack bug, 2) it’s an intended JetPack feature, 3) it’s a setting in one of the various features built into JetPack, or 4) it may have something to do with my IP address or cookies that is ‘remembering’ my former wordpress.com settings.

So, I’m going to clear my browser cache, run ccleaner for good measure, change my IP address, reboot, and start at the issue all over again.

It’s however becoming painfully clear that I may end up having to ditch jetpack altogether to keep things the way I want them. I’ll continue my notes here (if anyone is interested.) Is anyone listening? ..does anyone out there care about this issue? Please let me know ??

The odd thing is that in making my new wordpress.com account it NEVER asked me my real name – so jetpack must be getting my real name by some other means? (odd)

Hey, I normally wouldn’t care if my real name is out there but my problem is that I occasionally have to report by posting on scam sites out there and I don’t like my real name attached to such negative (though entirely true) posts (best not to paint a huge bulls eye on my arse – I might as well just post my address, directions to my house (for scam site running ‘have shotgun will travel’ types – lol), and phone number if my real name is out there attached to these posts as well (lol))

Cleared my browser cache, ran ccleaner for good measure, changed my IP address, rebooted, and same issue still there (good grief!)

I also browsed my database in MySQL and tried to see if my full name appeared anywhere in that database – it doesn’t! So it’s all having to do with jetpack importing it from one of the accounts it’s interacting with… I guess I’m going to have to start deactivating each of jetpack’s features one by one until (if) I find the problem.

I’m also going to report my issues to jetpack and point them to this thread to see what they have to tell me (us)

OK, I FOUND THE ISSUE AND SOLVED IT!

Under JetPack > Publicize I had it connected to my Google+ account under my real name. The second I disconnected that Google+ account then all my WordPress posts went back to ‘FreeCashPro’ as the author. Ahhhhhhh….

Problem Identified / Issue Solved ! Case Closed !

Thank you all for your support and suggestions.

FURTHER:

Ok, after much editing of my Google+ settings and profile I was able to reconnect my wordpress jetpack to google plus and the happy medium I achieved was that in my wordpress posts on my blog it now shows the author of my posts as my first name and last initial and in parenthesis (FreeCashPro) which is much better that just my full first and full last name It just needed some tweaking.

That’s great your issue is resolved! ??