The command to search a member's posts from a member profile page isn't working. The error messge is "Sorry, the board administrator has enabled search flood control. Please wait at least 3 seconds before trying again."

The same result occurs after waiting 3 seconds, or 20 seconds (the standard wait period for guests), or 3 minutes. I've tested this for several members with the same result.

I'm browsing with the current version of Chrome for Mac, 61.0.3163.100 (Official Build) (64-bit). The same thing happens with Safari, as well as with the Snow Leopard version of Chrome on a different machine.

Perhaps the problem is due to a setting that got mangled in one of the software upgrades that were recently announced?

TTT

Edit: The topic description should read "Search flood control out of control," but I can't seem to edit it.

For what it's worth - I have no such problem here. Chrome on a Mac (and on 'droid and iOS) And those software upgrades haven't started yet.

Caching issue between your browser and ISP I'd have thought.

Working for me as well, Tom--Safari on a Mac.

Doug & Nick, thanks for your replies.

I've discovered that I don't have the problem with an iphone and an android tablet logged into the same wifi/isp network; I don't know enough about caching to say whether that's a clue or not.

And I've found a workaround. After trying the command and getting the error message, I copy the html code (I guess that's what it is) in the address bar, namely http://www.unmannedspaceflight.com/index.p...lluser&mid=[member ID]. I've suppressed the member ID in this example, but the format is "mid=xxxx".

Then I paste the code right back into the address bar in the same window from which it came and hit return. Works like a charm.

I'm guessing that when I use the drop-down menu command for "Find Member's Posts," my browsers and the host software are interacting in a way that makes the host software think that I've submitted the request twice in quick succession, something that they don't do when the same code is pasted into the address bar. This didn't use to happen, so it's a bit of a mystery that it now happens on two different machines running different operating systems and browser versions.

Not important in light of the workaround.

Yup - that's a caching issue.

Or maybe member specific? Are there special characters in the user id? Try it with another username?

I've tested the problem with ~7-8 members, same result for every one. I didn't methodically check the member id for each user, but all the ids that I looked at were simply strings of 1, 2, 3, or 4 numbers.

Irrelevant fact: Doug is the only single-digit member still posting regularly