Post edit error: "More than one character required

Lately, I’ve been running into this annoying little hiccup where I try to update one of my posts, only to have the system throw a fit and tell me there aren't enough characters in the edit to actually save it.
The thing is—and this is what drives me crazy—I’m not just swapping out a single comma or adding a tiny typo fix... I’m actually deleting whole phrases and rewriting sections entirely.

So, is this just one of those classic Reddit glitches that everyone complains about, or am I somehow missing something obvious here?...

I actually flagged this earlier today, along with a few other glitches I ran into. To be fair, though, nobody else seems to have mentioned the specific issue you brought up. It looks like they were working on some fixes because things seemed to smooth out on my end, so if you get a chance, could you double-check if you're still running into those headaches while trying to edit? 🙂

Thanks, rustydrifter10, for getting back to me. Everything seems to be holding up for now—I actually went ahead and made one quick edit, and surprisingly, the system didn't throw any errors my way this time. I'll definitely give you a shout if things start acting up again...

I just ran into the exact same headache. I was trying to go back and tweak a few sentences on my philosophy thread on Reddit, and out of nowhere, it hits me with this: The message you entered is too short. Please lengthen your message to at least 1 characters.

I went ahead and filed the report. Just let me know if any other issues pop up, or if you notice this one has vanished entirely.

rustydrifter10 said:I've escalated this. Let me know if anything else pops up or if you notice this one has vanished...

Is this a Dejav move? I got the exact same runaround last time...

Jacob Cooper5 said:Is this just the Dejav experience? Honestly, I got the exact same answer last time we spoke.

Well, yeah, and it actually worked out fine last time! I’m honestly not sure why you were expecting anything else from me here. Look, this is really in the hands of our technicians; I’ve already flagged everything you're going through to them, and now it's their job to get it fixed. If you notice that things are back to normal, would you mind letting us know? It helps us confirm that everything is running smoothly again. If this pops up again in a few months, there's a pretty good chance you'll hear the same thing from me—mostly because I'll be passing the info along to those same technicians and then circling back to let you know I've done my part. Just please, do me a favor and reach out if the issue persists so I can tell them right away that we still haven't cleared it up.🤷

rustydrifter10 said:Yeah, and it got fixed last time too. I don't know why you'd expect anything else this time around. This falls under the technicians' jurisdiction—I've reported what's happening to them, and they’re the ones who need to fix it. If you see the issue resolve itself, it would be great if you let us know so we can confirm everything is back on track. If this pops up again in a few months, there's a huge chance you'll get the exact same answer... because it'll still be up to those same techs that I report to, and then I'll just notify you once I've done my part. Please just reach out if the problem persists so I can tell them it isn't actually resolved. 🤷

I don't think the problem is you, rustydrifter10. Honestly, I have my doubts about tech support... because, first and foremost, when a tech team actually handles things, they should be looking for feedback during the troubleshooting process. They're supposed to ask the person reporting the issue for details about the circumstances surrounding the glitch—it's the only way to actually pin down the root cause.
You did your job perfectly fine. But since the technical department didn't even bother asking the basic questions that any standard US IT service asks by default (operating system? drivers? browser and add-ons?), I've got serious suspicions that this crew isn't actually interested in solving anything... which is why these issues keep looping back around.

Man, I really hate that this is falling on your shoulders when you're just trying to do your job honestly...

@Jacob Cooper5/">@@Jacob Cooper5

You might want to verify whether you accidentally hit quote instead of edit... It is a frequent blunder, much like those glitches you see in an app's response.
The process goes like this: you open the quote, make your adjustments within the quote "window," but fail to actually compose a reply. Consequently, the system informs you that there is no response message. It is quite simple enough to verify...

Jerry Robinson56 said:@Jacob Cooper5/">@@Jacob Cooper5

Just double-check that you didn't accidentally hit quote instead of edit... honestly, it’s the same kind of glitchy nonsense you get from some of these mobile apps.
You open up the quote box, tweak something inside that little window, but then don't actually type any new response—and boom, that's it. The system just flags it saying there's no message to reply with... It's pretty easy to verify if you actually look at what you're doing...

I don't even bother using the quote function, but even if I did, there's zero logic to it—the software would have to register an edit of at least one single character for it to count, but right now, it won't even recognize when you swap out entire words...

Jacob Cooper5 said:I don't even bother using the quote function, but honestly, if I did, there’d be no point anyway. The software doesn't even register an edit if you change a single character, let alone swap out entire words.

Been there. Personally, I think the issue was some glitchy syntax with the brackets around the QUOTE or /QUOTE tags.

Here we go again. I’ve tweaked a bunch of the wording, tossed in some extra bits, and added "The message you have entered is too short. Please lengthen your message to at least 1 characters."

Take a screenshot so we can actually see what's going on here.

A screenshot isn't going to do squat because the only time I can actually grab one is after the damage is already done.
A screen grab would just show me the notification and the post text—hardly useful info for any tech support guy looking to fix a bug.
The only way this works, at least in my book, is if I had some kind of specialized software running specifically when I log onto Reddit, though even that’s a headache since the program would have to distinguish Reddit from every other site in my browser...

Despite how much effort the moderators clearly put into trying to sort out my mess, I think I'm just going to have to accept that these glitches are part of the deal now.

I will say one thing, though—in my case, the mods reacted instantly . Cheers to rustydrifter10 and dubiti.

That’s exactly what I need to see—the notification and the actual text. Just take a screenshot and drop the link here, or if you'd rather, you can just DM it to rustydrifter10 or me.

Jacob Cooper5 said:I don't bother using the quote function at all. Even if I did, there’s really no point; the software would just end up registering an unnecessary edit every single time. It is fundamentally flawed. The system fails to register even a single character change, let alone a complete modification of terms.

It all depends on how the application was architected. Technically, it isn't a requirement, though it would certainly be beneficial to implement such a feature. When you encounter an issue, try navigating backward—using that back arrow in the top left corner, if you can forgive my stating the obvious—to review the text. Once you have a clear understanding of what you are actually looking at, you can then forward it to those women who have already expressed their willingness to assist you.
The message you submitted is insufficient in length. Please expand upon your thoughts to meet the required minimum word count. At least one character..
It’s quite obvious what happened here. You clearly hit the "quote" button instead of "edit" on your own post. You end up typing your response inside someone else's quotation block, leaving absolutely nothing written in the main body of the post itself... or so it seems. That's my professional assessment.

It seems quite clear—you possess absolutely no discernible character whatsoever. 😁

Besides, you might as well give it a shot.

Linda Young38 said:I’ve run into this myself; I suspect there was some sort of syntax error involving the brackets surrounding the QUOTE or /QUOTE tags.

It only functions correctly if you are typing within the {[Qxxxx]*.*[/Qxxxx]} parameters.
self-belief

Casey Bennett said:That’s actually what I'm trying to figure out—the notification itself and the actual message. Just grab a screenshot and drop the link here, or you can just DM it to rustydrifter10 or me... doesn't matter.

Fine. I'll deal with it when the next glitch actually pops up.

Here we go again! This time I am 100% certain—absolutely positive—that I used the exact same edit function as I did before.
I’m asking my dear moderator here not to try and convince me that I accidentally hit the quote button instead of edit... again. Thanks.

I’m not trying to convince you of anything. You sent me a screenshot that makes it crystal clear you were replying in a quote rather than actually editing the post 🤷

I’m staying out of this from here on out; let the admins decide if they want to look further into how this was handled.