There are a ton of variables in play when it comes to caching, and the Seamless Donation plugin is way at the bottom of that list. There’s nothing particularly interesting in the SD code that would cause it to behave poorly (or well, for that matter) with a caching system.
I did this search on Google and started to dig in to see if there was anything that stood out:
W3 total cache cache-Control: no-store, no-cache, must-revalidate
The most obvious answer was this one, and it would make sense for you to try different browsers and reset your cache:
I actually had to clear the browser cache of my main browser to
eliminate this:
Page cache:
Caching: enabled
Status: not cached
The not cached status was cached in my browser because of
Expires Headers I have set I guess.
So you might want to clear your browser’s cache, reboot, etc. and see if that helps. Sorry about not being more specific. I spent a few days two weeks ago trying to set up caching on the zatzlabs.com site and got so annoyed with it that I just pulled it out.
I constantly had to go back into the CPanel and my Cache control panel to flush the cash to see results of development changes I made. Caching does have its purpose and I’m not recommending you do what I did, but just be aware it adds a substantial layer of complexity that’s both unique to your own site and configuration and a true pain to trace down.
Now, if I were you and I was releasing a new site tomorrow, I wouldn’t add caching to the mix. But I’m not you and don’t know what your specific needs are. That said, chocolate always helps, no matter what the situation.
Good luck!
–David
Ok thanks for this. I will try it. I have another problem now. First is that I am not getting any donor log at all nor automatic emails. The second is that I want to redirect to a custom thank you page that I made at http://www.educacess.org/donation-thank-you. It has been working for a week now using the following:
header(‘Location: http://www.educaccess.org/donation-thank-you’);
But then today all of a sudden when I make a donation I get a message saying can’t write header because it’s already being called from a different php file. Any idea on this one???
I have a good idea about the header, and that might also be what’s causing some of your other problems.
Only one header can exist for any given Web page. It’s very likely either your theme or another plugin is fiddling with the header as well, causing breakage. But if you’re getting header-level breakage, it’s bound to hurt other code.
I hate to send you to the old “turn one thing off at a time” debugging procedure, but that’s most likely what you’ll need to do to see what’s happening.
