Flooding is still a problem

[dhbookds]

Got it this morning...........  just for info............I copy/pasted from a previous post.............

[eburtonlab]

I think there is an additional "time" component to the flooding error in many cases, specifically the time between pasting and posting -- not just between successive post attempts (though there is that, too).

Once you paste your text, try counting to ten before viewing the preview. If the preview works, then try posting. If the preview fails, open a duplicate tab and try again.

[coffeebean832]

That's one of the most ridiculous things I've heard lately. I'm not balking at your suggestion because if it helps people then great and thanks for sharing what you've figured out with timing. The part that's ridiculous is that the system would make us wait between the time we copy/paste something and the time we can post without an error.

[pburn]

@dhbookds 

Was it the post-flooding error or the HTML error?

[dhbookds]

---

@pburn wrote:

@dhbookds 

Was it the post-flooding error or the HTML error?

---

"Can't have one without the other".......lol........at least I haven't......... tried to post,including a copy/paste from a previous message, got the HTML warning....which has sometimes disappeared lately and the post has posted........but not this time, got html warning again and ..hit reply again and got the flooding message.

[dhbookds]

Once you paste your text, try counting to ten before viewing the preview.

ok, let's see what happens......above/copied, pasted

[dhbookds]

so I didn't count to 10, and it posted fine...............sigh..............  may be it's the reverse..........too much time

Once you paste your text, try counting to ten before viewing the preview.

edit: no problem there either............

[eburtonlab]

@coffeebean832 

The part that's ridiculous is that the system would make us wait between the time we copy/paste something and the time we can post without an error.

I think the intent may be to prevent bots from posting messages in rapid-fire succession -- or at least to slow them down. The designers of such a system may not have considered how fast a human can cut and paste a response, or may not have considered that such pasted posts might actually be wanted posts as opposed to spam.

Either that or the software that is attempting to strip out html from the text is very slow.

I do notice that there is a new "html" button to show the html formatting in messages -- and that the typical pasted text contains quite a lot of formatting information that can be stripped out without losing any actual information.

[nobody*s_perfect]

But the "post flooding" issue about quotes/html is new within the past few  months.   For years, all we needed to do was hit "post" twice.  These workarounds are annoying, I'm gonna just stick to inserting the whole quote, and highlighting th relevant part.

[eburtonlab]

@nobody*s_perfect 

But the "post flooding" issue about quotes/html is new within the past few months. For years, all we needed to do was hit "post" twice.

Agreed. Khoros has changed the posting process in such a way that once an error has been generated, a second immediate attempt at posting is very likely to result in another error -- either the same error (because the html has not actually been removed, or because the error is mistaken to begin with), or else a new error (flooding).

Delaying, rather than immediately attempting a re-post, seems to avoid an error in some (but not all) cases. And using the preview can be a useful indicator -- if the preview fails to load properly, the message most likely will not post, in my experience.

[a_c_green]

---

@dhbookds wrote:

Got it this morning...........  just for info............I copy/pasted from a previous post.............

---

I get stuck in this issue if I bring in a lengthy quote from a previous post, and attempt to remove part of the quoted material that either begins the quoted section or ends it. Evidently I'm taking out some hidden begin or end tags that cause the quoted section to become unbalanced, and when I try to post my reply, I get a bad HTML warning.

At this point, the message claims to have fixed the problem and that I should try to submit it again, but if I do, I get the post flooding error.

The workaround I've found is to cancel that attempt and post my reply (only), with no quoted material. Once that's up successfully (and that much works every time), I then go back in to edit it, pushing the first line down and then bringing in the quoted material. If I'm feeling nervous about it (depending on how much I plan to remove from the quoted section, such as images), I'll save (post) the updated reply with the whole quote at that point, and then go back in again to edit out what I don't want. (It takes longer for me to write about it here than to do it; it's pretty quick really.)

My take on this is that the software doesn't like quoted material that's missing certain key tags, but doesn't parse updated posts as much as it scrutinizes new ones. Thus I use the first post to bring in my text only, and use the edit ability (at least for 5 minutes or however long you get) to bring in the quoted stuff afterward.