Hi Mark,

Here's a minor display bug.  When one is in the Admin-Members screen and enters a search term and go into "Search" mode, after they select a member and edit their membership settings, the member list contents won't refresh when they are returned back to the search results member list, so it still shows the previous member attributes before editing. (DisplayName, EmailAddy, DeliveryMethod)

F5-refreshing the page refreshes the list contents and they now agree with the changes.  Not doing so, and continuing to (test-) edit that member (thinking one must have not made the change, so go back to check/redo it), results in a "one-page behind in display results" scenario, where the underlying code correctly does its thing, but the list display code seems to display the next to the last changes.

I tested this under Members-(regular) and Members-Mods, but I suspect the same also happens in the rest (Bouncing, Pending, etc), when there is a search term entered; it does not happen when there is no search term entered, it correctly refreshes the list contents in that case.

Not a biggie but it can be somewhat confusing/bewildering if one is not paying full attention and can result in unnecessary time & mouse clicks to figure out what just happened.

Cheers,
Christos

On Tue, Oct 6, 2020 at 01:49 PM, Christos G. Psarras wrote:

F5-refreshing the page refreshes the list contents and they now agree with the changes.  Not doing so, and continuing to (test-) edit that member (thinking one must have not made the change, so go back to check/redo it), results in a "one-page behind in display results" scenario, where the underlying code correctly does its thing, but the list display code seems to display the next to the last changes.

This is something of an insidious problem for a handful of groups.io operations. Deleting photos from a photo album does the same thing...the photos in the album are renumbered, but the thumbnails served from the browser cache are not.

I've gotten into the habit of doing a Ctrl-F5 whenever something doesn't "look right," but I suspect many others have yet to learn that trick. If the reload can be forced from the server side under such circumstances that would be a good thing (yes, I know it's been asked for before).

Regards,
Bruce