Brought the app. Got a message from Makoto thanking me, and offering help if I ran into problems. Me being me; I ran into problems which Makoto fixed (Monkey Error, as in a misconfiguration I made) the issue within minutes. Their support is top class and they're very friendly to boot. I actually feel like a valued customer. I fully recommend this app to other people if you're looking at giving members more control over their account. Giving members the control to deactivate an account was a trick I felt IPS had missed, this is a very useful application and I couldn't be happier. $35 well spent in my honest opinion. Big thanks to Makoto!
https://community.invisionpower.com/topic/190749-vectura-webmail/ 10 years ago. xP I remember a modification on the marketplace for IPB2 or early IPB3 (Can't remember) that basically allowed certain usergroups access to email from the site, I can't for the life of me find it though. Edit: Yeah here it is - https://community.invisionpower.com/topic/286682-bouncy-mail/
Excellent support, excellent application for excellent sites! xP I don't think I can recommend this application highly enough. $15 is well worth every penny for this application. If you do run into any issues the support given by the developer is top-class. I've had my major issues resolved within ten minutes.
That's completely blowing it out of proportion, oh and congratz on necro'ing a dead thread. I'm willing to bet that the majority of IPS's customers don't change their domain name every week; so how this is "Controlling the masses" and why does this need to change? What because you say so?
Google Chrome as primary. Firefox as secondary. IE when I am using the British Gas home topup for my Pay&Go meter. Because for some reason British Gas only supports IE (and even then only certain versions of it).
Dumb it down? In a few words... Wait for IPS. xP In seriousness; you're basically putting Emoji into a field that (in the database) can't support it. Instead of stripping the incompatible character out - it blanks the whole field. DO NOT FOLLOW MY STEPS IN "FIXING IT" because (and I only found this out this morning) it will lockout the other accounts saying it's not in the database. I will look at how a clean install of IPS4 does it and see if I can come up with a working solution, although I don't recommend doing anything until IPS Support tells you to, as I am still learning about all of this stuff myself and just sharing what I find out. At the moment I get the following error "The Display Name you entered does not belong to any account. Make sure that it is typed correctly." In the converter (the thing we had to run before upgrading) I did select utf8mb4_unicoode_ci. For some reason the converter didn't work properly. I'm going to go out on a limb here and say @Dorian Gray used the UTF8 converter before updating from 3.4.x to 4.0.x which would make sense because we had to. I have no idea if s/he used utf8mb4_unicoode_ci or utf8_unicoode_ci but I know for sure I picked the former, definitely not the latter - because it was conscious decision that had to be debated with my fellow administrators for our site. For example: utf8mb4_unicoode_ci: Slower Speed + Emoji Support <--- Which we wanted utf8_unicoode_ci: Faster Speed + No Emoji Support My guess is for whatever reason the converter failed, and whilst I did make a backup; I did the conversion way before Christmas and I was only told to back up incase it didn't work and after it did work I wouldn't need the backup. If this is a bug that was fixed in the converter that I will need to convert my old database again I'd be rolling back to before September 2014; which is unacceptable, or... I can restart my forums which is outrageously unacceptable. My only choice is to hope that the converter can do it properly or manually change the types and collations myself; or wait and see if IPS can suggest anything better. I sort of did this whilst I was waiting, in the hopes that it could help locate and track down where the problem was and what was causing it. I also tried to see in what circumstance would it cause one's account to be deleted; I can't answer that because I don't know. I wasn't able to get an account to be deleted, just their username. Edit: A fresh install has all tables set to utf8mb4_unicode_ci and the display name table is set to varchar(255) utf8mb4_unicode_ci not blob utf8mb4_unicode_ci which didn't work for me when I played around with it yesterday from a converted one. I should have known it wasn't that simple.
Okay; yep. It seems to be upgraded installations that it's reproducible on. I wonder if this is why it couldn't be reproduced by staff...
This happened after setting username to: ?A Username It still didn't "Delete" the account though, so I suspect (and hope) the account is still there, somewhere, Dorian. I have my fingers crossed for you. BUT... I had a look at my database; more specifically Collation's. Take a peak at this noise:
Now I would like to say Collation doesn't imply causation... xP But then I remembered what @Ralf H. said earlier: An emoji is a 4byte character, right? So I looked into it and found that it was utf8_unicode_ci which I changed to utf8mb4_unicoode_ci. This didn't fix it, and I found that the actual name was also stuck on this collation, so I changed that to utf8mb4_unicoode_ci and all. This didn't work either. But silly me, it's also varchar(255) -> Which I changed to BLOB, (As a type)... Low and behold:
Do they have anything in common like did they all use Facebook/Twitter/Google/Steam or something to sign in? I had a problem like this in the past; it turned out it was a malformed Facebook Connect request or something. I'm just guessing here; but I try to look for something they all have in common between the accounts. --- Okay, so I just installed a fresh copy of IPS4 as a Dev (Not upgraded 3.4.7) and I can no longer reproduce this:
Next I will be trying upgrading from 3.4.8 to 126.96.36.199 directly and seeing if I can reproduce it.
I find it very curious that IPS couldn't reproduce it yet we could. I'm actually quite interested in testing this out on a fresh installation. =/ I think I will use their downtime over the weekend to do some more tests with it, but I suspect @Ralf H. is absolutely spot on with his assessment.
Then your best bet is waiting for IPS, I'm afraid. All the posts should be tied to a User ID not a Display Name. I've asked them in my ticket to give yours priority over mine (I have no idea if that was the plan) purely because your board is live at the moment, where as mine is private and a test. The only other thing I can think of (And just tested) is going into the ACP and go to edit a user (doesn't matter which because you just need the URL). If you have the affected account's User ID you can edit the URL so where it says: app=core&module=members&controller=members&do=edit&id=XXXyou change XXX to the user ID of the affected account. That way it's all done through the IPS software, like it was done to change it in the first place. You shouldn't need to do anything with the posts but then this bug could be affecting you in a different way. I'd happily look into it for you right now, but I think it's most certainly better to let IPS take a crack at it in all honesty.
I would imagine you are confused seeing as this missing email (I assume on Update) issue is something else completely, and has nothing to do with this topic =/ Although I fixed mine through PHPMyAdmin too.
The Red Arrow is pointing to the field that is causing the problems, this just needs a name in it. Nothing else needs to be done. You can search core_members for the members email address and set the username to her username and put "(OLD)" next to it. As I have already said you don't need to remake an account, just edit the one in the database that has no username anymore. If you don't know how to do it, I suggest opening a support ticket to IPS. If she's already made a new account, you can simply name the account something else, for a temporary measure and "Merge" the two accounts together, in the ACP. This should merge the two accounts back into one.
Be very careful here, make sure to read properly as if you do it wrong you will lose track of what you've done. Everything at the end of it should all be back on "A Username (OLD)" and the new "A Username" should be merged with the old one, then it'd just be a simple case of resetting "A Username (OLD)" back to "A Username". This will require DB Access for the initial bit, so again, if you are going in there to mess around - Make a Backup of your Database First! If you have literally no idea what I'm talking about (Which I'm starting to suspect) then open a support ticket like many have requested you to do already. =/ Done. Has anyone else got a ticket open about this specific issue?