I have setup reCAPTCHA checks on form submissions but in the reCAPTCHA documentation it seems (if I read it right) to suggest also associating them with at least some page GET requests for the site, so that reCAPTCHA has "context" to inform its scoring of whether requests are suspicious or not.

The "Support our Charity" page has two forms on it, the "Donate" form and the "Join Us" form. Both have reCAPTCHA v3 protection on them. This seems to have disabled the submit on the second form. An Internet search suggest that this is a known limitation of reCAPTCHA v3, it can't be applied to more than one form on the same page.

The current donation amounts are all fixed, with choices of £5, £10, £20, £30.

Instead we want £5, £10, £20, £50 and specify an amount yourself options.

Use a human message rather than the HTTP return code and also provide a handy, in-place link to the home page.

We haven't included pagination when news items are listed on the "Latest News" page. Check for the "Upcoming Events" too, though at any one time there should be a limited number of those.

A link to the current donate page is distributed via QR code so when the redesign website goes live put in place a redirect to the equivalent path in the new website.

There's an intermittent bug in the flow out to PayPal in the redesign website. Sometimes when we arrive at the PayPal landing page it would appear that no order has been passed through.

This seems to happen on the second pass, when testing for example donations, multiple times. If you come back to the redesign and force a refresh without caching, then the bug doesn't occur on the next run through.

We don't want a payment reference to be reused. It's stored in the session so unless it is cleared at the relevant point it will be reused. The completion of the Gift Aid step is when notifications are sent and, if the payment method is online, we flow to PayPal. Both these use the current payment reference, so completion of that step is the right place to clear it.

Instead we should put somewhere under the payment options that will remain supported (cheque, bank transfer and online) something to say that if you're struggling to use one of those options you should "Contact Us".

Once we've gone live with the redesign site, create a new test site based on the now live redesign site and put a page in that with the within page PayPal integration using their Javascript SDK in it. I'll also need to supply details of the SSL certificate implications for the decision on whether to move to this mode of integration to be taken.

If the website visitor makes a Gift Aid declaration then they must provide their address. If they're paying online and are directed through to PayPal to handle the payment, they must again provide their address. Can we pass through the address in the Gift Aid declaration to PayPal?

Went live using wp-bootstrap-starter parent theme. Would be better now to theme from scratch.

These are the settings that produce a 404 response for a page that is downstream in a dialogue flow unless that page is reached via that flow, i.e. if somebody just navigates to the page's location directly rather than as a result of going through the relevant process.

We've sought to disable comments on the site and mostly succeeded. However, very occasionally we're receiving a candidate comment seeking moderator approval on an image. Clearly we've missed a route in for comments that we need to close.

This needs to be both for flow-forward (no errors) to the next step in a process dialogue and flow-back (errors) for the previous step in a process dialogue.

Increase the size of the section menus that appear just below the headers. While we're at it, I think perhaps the main menu could do with a size increase or some other way to improve the clarify of the options.

Work out some way within the theme to give quick access to "Contact Us" and "Donate" on every page.

We want to retain this integration and the Mailchimp list is still segmented with the different approaches to doing this in live and test.