Matheus Martins

Hi, @wtnhistwebmaster.

Based on your description of your site remembering who you are when you access it, it smells like a cache.

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 not familiar with caching, it’s a method of saving 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 just get the copy that was saved. Basically instead of the site needing to recreate the page from scratch, it sends up a copy which allows 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 really well for speeding up sites, but when a saved copy of the site has sensitive information in it (like donor info) it’s important that GiveWP not share that with the next visitor. If GiveWP is not convinced that the browser requesting the data is the correct one, 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 caching at the server level, 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

Your host or the caching plugin/solution you are using can help with that. Some of them may require what’s called 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 cases like those, 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 include options for caching as well, so be sure to give those settings a look.

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

I know 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, @dartford5.

Glad you reached out.

We try our best to “stay in our lane” with Give’s CSS, and let the theme do the bulk of the work of styling.

Here’s a short CSS snippet that can be your starting point:

.give-embed-form-wrapper iframe {
    width: 50% !important;
}

If you need assistance implementing custom CSS on your WordPress website, we have this guide for you:
https://givewp.com/documentation/resources/handling-custom-css-in-wordpress/

Please note that this code snippet is provided as an example of how you can extend GiveWP with code. It’s up to you to implement and customize to your liking. We cannot provide support for custom code on your website, only the code that we create and distribute.

Thanks for using GiveWP! Have a great day.

Hi, @wtnhistwebmaster.

When I access your site and start a donation, I’m redirected to PayPal without problems: https://imgur.com/vGEgW7U.

For me to test, I need either a staging site where I can donate without using real money OR you need to enable test mode on your site under donations > settings > payment gateways > gateways > test mode.

Looking forward to helping you get to the bottom of this!

Hi, @monicaamb12.

Glad you reached out.

At the moment, GiveWP doesn’t have an integration for Redsys, but it is a feature request we are tracking here: https://feedback.givewp.com/feature-requests/p/redsys-payment-gateway. You can use this post to add comments of your own and follow our progress. I’ve also linked your ticket here so we can reach back out to update you once we have a resolution for this.

If you are a developer or have access to one, you can also create your own integration using our documentation here https://givewp.com/documentation/developers/how-to-build-a-gateway-add-on-for-givewp/.

I’ll go ahead and mark this as resolved for now, but if you have any questions, you can create a new ticket right here and we’ll be happy to give things a look. Have a great day!

I understand, @davidanderson. If you decide to use GiveWP again, we will be happy to help.

Have a great day! 🙂

Hi, @tiotrom.

Glad you reached out. I can help you with that.

Typically, this error means some broken code is causing your site to crash. It is a WordPress system-generated message that means something has caused a PHP fatal error. Whenever you see that message, a more detailed error log has been sent to the main admin email address (which you can configure at Settings > General in the main WordPress settings).

Check that email, and then pass along any error messages you are receiving so we can help. Every time you see that error, it sends another email. If you need to, you can trigger a new email to be able to see the error message again.

If you don’t see that error in your email (WordPress emails are notoriously unreliable that way), you’ll need to ask your host for the error logs. They will be able to send you a complete record of the errors on your site. Once they provide you with this file, send it to us, and we will be able to identify the issue and move toward a resolution for you.

Your success with online donations is our number one priority. Looking forward to helping you get to the bottom of this!

Hi, @mbio86.

I need a place where I can test it without using real money. It can be your live site with test mode enabled OR a staging site.

For option one, enable the test mode under donations > settings > payment gateways > gateways.

For the second one, you need to create a staging site, enable test mode there and share the link here.

Looking forward to helping you get to the bottom of this!