Matheus Martins

Hi, @prillou28.

I’m glad you reached out. We can certainly guide you while you learn how to take advantage of GiveWP’s features.

For that reason, we created a getting started guide that you can find here: https://givewp.com/getting-started/. With the information there, you should be able to set GiveWP up and accept donations. Also, you can check our documentation here: https://givewp.com/documentation/. It full of examples and ideas about how you can configure GiveWP.

If you need any further clarification, you can drop us a message and we’ll happily help you!

Have a great day! 🙂

Hey, @jwesbeek.

Thank you for taking the time to write this review, it really makes us happy. Should you face any other issues with our tools, drop us a message and we’ll happily help you.

Thanks for using GiveWP! Have a great day.

Hi, @bhwebworks.

I’m glad you reached out.

Indeed, the code snippet you use is for the option-based forms only. However, I have good news!

Our development team is working on a solution for the visual donation form builder, and it passed dev, QA, and we are getting closer and closed to a release. You can subscribe to our newsletter here https://givewp.com/subscribe/ and when it’s released, you you get an email from us.

I still cannot promise a date, but I know it’s close – pretty close!

Feel free to reach out to us if you have any further inquiries or require additional assistance. We’re always happy to help!

Hi, @christopherdl.

It’s been a while since we’ve heard back, and I know troubleshooting needs a little extra time. I’m marking this as resolved for now, but if you still have questions, you can send them along right here, and I’ll be happy to hop back in.

Have a great day!

Hi, @shaunwingrin.

I’m glad you reached out.

As the add-on is a premium feature, we’re unable to provide support here. However, you can reach out to our dedicated support team via https://givewp.com/priority-support/, and they will be more than happy to assist you.

We’re looking forward to helping you get to the bottom of this issue!

Hi, @ojasya.

It’s been a while since we’ve heard back, and I know troubleshooting needs a little extra time. I’m marking this as resolved for now, but if you still have questions, you can send them along right here, and I’ll be happy to hop back in.

Have a great day!

Hi, @logitem.

I have some recommendations that will help with that issue you are seeing.

The fix here is a bit technical, so I’ll include as much detail as possible, but you may need to reach out to your web developer or web support person to implement these recommendations.

Your issue here is caused by some caching happening somewhere in the process. If you’re unfamiliar with caching, it saves server resources by storing copies of a page, resource, query, or site so that the next visitor’s visit doesn’t trigger a call to the server at all; they get the saved copy. Instead of the site needing to recreate the page from scratch, it sends a copy, allowing it to load faster.

We put together this deep dive into what caching is and how it can cause problems: https://givewp.com/documentation/resources/caching/

Caching works well for speeding up sites, but when a saved copy of the site has sensitive information (like donor info), it’s essential that GiveWP not share that with the next visitor. If GiveWP is not convinced that the browser requesting the data is correct, it defaults to not showing the data.

Caching is handled differently on various sites and web hosts. This could mean a caching plugin, or caching could be in a security solution. Hosting providers also have settings for server-level caching settings, and they can help make adjustments for you there. Most caching solutions have a setting or section for excluding specific URLs or parts of URLs (called “slugs”) from caching. At the very least, you should exclude the following slugs from caching:

/donations/
/donation-confirmation/
/donor-dashboard/*
any page with a donation form on it

Also, the following query strings (if your caching solution has a setting for them):

give-embed=donor-dashboard
giveDonationFormInIframe=1
give-listener=paypal-commerce
give-listener=ipn
give-listener=stripe

Your host or the caching plugin/solution can help with that. Some may require a “wildcard” like /donations/* to capture all subdirectories under the /donations/ folder.

Some folks prefer to customize the URLs to their site pages, so you may find that your URLs don’t have the slugs mentioned above, even though they contain the same content. In such cases, we recommend whitelisting the page, not just the slug; that way, the pages with those essential pieces of information are still excluded from caching. This is especially important for URLs of pages with donation forms on them.

One helpful tip: Check in with your hosting provider. Most hosts have caching at the server level, and they will be able to adjust this for you. You can also temporarily disable caching on the site to confirm that the uncached site isn’t showing the problem.

Many security solutions also include caching options, so be sure to give those settings a look.

While fine-tuning the cache falls outside the scope of the support we can provide, your success with online donations is our number one priority, and we’re happy to provide any tips.

Also, please disconnect and connect your PayPal Donations account.

This was quite a bit of information to share. If you have any questions about this, let me know. I’m happy to help.

Hi, @html5wp.

I’m glad you reached out. I can certainly help you.

Please reach out our dedicated support team via https://givewp.com/priority-support/, and they will be more than happy to assist you.

We’re looking forward to helping you get to the bottom of this issue!