TOPIC:

Two members joined just recently (Shane and Emanuel). I never sent them an invoice as they paid the renewal when they joined. Both are listed in the Track Payments window as having paid their dues, but the report doesn't reflect this. Even if I change the payment method (and Save again), the method of payment doesn't show up in the report.

My guess is it has to do with not having sent them an invoice.

This is for Quest 4643.

I see them on the report - with method, but no invoice date, as expected.
You might need to close the dues module and open again to have them show up.

I logged out and closed the tab. Then reopened site, logged in as myself (I'm treasurer). The dues report still shows nothing as to payment method for these two. See attached.

I can definitely see the payments (paypal) when I run your report, but to test I've just done a similar exercise for my club, and I have the same issue you are experiencing. I thought it is might be something to do with caching, but even a reload from server doesn't change it.

I'll follow up with our developer

I had something happen that may be related. I had tagged a new member as paid but when I wanted to send an email to duesnotpaid, the system added her to the email.

From memory - it was a few weeks ago now - I needed to logout and close the browser entirely. When I started a new session, the new member's name wasn't included in duesnotpaid.

It might be worth your while to try logging out and re-starting your browser, then logging in again.

Added cache killer parameter to the Javascript to force a different URL every time. Give it another try.

Pam: The reason the reload did not work is that the URL for this report is buried deep in the Javascript. A reload forces an updated copy of the same Javascript to load. in this case the Javascript itself has to vary the URL for the report (by tacking on a dummy time stamp to the end) to fake out the browser into thinking it is a different URL so it does not pull the report from the cache.

Most of the time, the reload will work. However, if the report is being called from in Javascript (vs from the html), then the Javascript itself must handle the cache-busting. Also, the report is not part of the original html that the reload link applies to--if the report had its own reload link, that may work, but just doing something in Javascript is simpler.

I probably could re-implement this in html without the Javascript, but just have not gotten to it yet.

The cache buster (time stamp) is in yellow below:

It works. You're a genius Steve. Don't know what we'd do without you.