Matheus Martins

Hi, @ladydev.

Glad you reached out.

Currently, we do not have a way to add a class parameter to our shortcodes. However, GiveWP is flexible and you can extend the shortcode functionality by adding your own code to it.

We have a tutorial for it here https://givewp.com/documentation/developers/customizing-give-shortcode-templates/.

If you need assistance implementing custom PHP code on your website we have this guide:https://givewp.com/documentation/resources/adding-custom-functions-to-your-wordpress-website/.

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, @noheed.

Glad you reached out. I can explain what you are seeing here.

You’ve uncovered an issue that we are investigating here: https://feedback.givewp.com/bug-reports/p/paypal-order-id-missing-error-should-not-prevent-donations-using-paypal-donation. You can use the link to check in for updates, and I’ve also linked your ticket internally, so when the issue is resolved we can reach back out to update you.

This particular error has been a bit of a white whale for our teams, in part because it is generated by PayPal, and in part because we are unable to reliably replicate it. The PayPal order id is sent as a part of the response to the call to PayPal, so it’s sent by PayPal itself. We’ve made repeated efforts to reach out to PayPal to get more information from their side, but they haven’t responded to those attempts thus far. With this being the case, it leaves us unable to troubleshoot, because it become an issue they need to correct from their side of things. We never like to send our users to other support folks, but in this case we are left with very little information and an inability to replicate the problem in a way that will lead us to a fix.

That doesn’t mean we are ignoring this issue! Our teams are continuing our investigation in an attempt to make that necessary forward progress. At the moment, our best recommendation is for PayPal Donations users who are experiencing this error to switch to PayPal Standard. This error isn’t present there, and PayPal Standard is a great option for non-profits. We also highly recommend Stripe as an alternative gateway whenever possible.

I know this was quite a bit of unhappy information to share, and I wish that weren’t the case. My goal is to make online donations as successful and seamless as possible for you, so please let me know if you have any questions about this, I’m happy to help as much as I possibly can. If you’d like more information or a walkthrough for the workarounds I mentioned, I’m happy to field any questions you have about those as well.

Hi, @srd75.

Glad you reached out.

You can use our Manual Donations add-on when you collect donations from other channels. This add-on allows you to add donations from the admin side of the site.

The important reason is that GiveWP uses session data to store donations made from the same timeframe and computer to a single donor, so even unique email addresses added into the front end of the site can get mixed together. Manual Donations prevents that.

You can learn more about it here https://givewp.com/documentation/add-ons/manual-donations/

If you’re interested in maximizing your use of GiveWP, reach out to our Customer Success team here to demo our premium features and receive an exclusive discount on our plans!

Thanks for using GiveWP! Have a great day.

I’m glad to hear it is working!

We’d love to get a public review about what you think of GiveWP both from a product standpoint as well as how it is to deal with our team. Here are some options:

https://reviews.capterra.com/new/286934/89e00484-d257-4f08-ad39-f8f2ab7461d7?lang=en
https://wordpress.org/support/view/plugin-reviews/give
https://g.page/givewp/review?rc
https://www.facebook.com/pg/wpgive/reviews/

The reviews help others to decide if it’s worth doing business with us!

Have a great day!

Hi, @pmcagamboa.

​Glad you reached out. I can help you fix your credit card fields.

What is happening here is that there is a plugin minifying some scripts, including the ones responsible for GiveWP. We need them to load in a certain order, and when they are minified, they break the donation form.

To fix it, you need to make sure that the GiveWP JS scripts are not minified at all.

In addition, since you are using minification, there are chances you are also caching your site.

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, @oozaar1.

Glad you reached out. I can explain what you are seeing here.

You’ve uncovered an issue that we are investigating here: https://feedback.givewp.com/bug-reports/p/paypal-order-id-missing-error-should-not-prevent-donations-using-paypal-donation. You can use the link to check in for updates, and I’ve also linked your ticket internally, so when the issue is resolved we can reach back out to update you.

This particular error has been a bit of a white whale for our teams, in part because it is generated by PayPal, and in part because we are unable to reliably replicate it. The PayPal order id is sent as a part of the response to the call to PayPal, so it’s sent by PayPal itself. We’ve made repeated efforts to reach out to PayPal to get more information from their side, but they haven’t responded to those attempts thus far. With this being the case, it leaves us unable to troubleshoot, because it become an issue they need to correct from their side of things. We never like to send our users to other support folks, but in this case we are left with very little information and an inability to replicate the problem in a way that will lead us to a fix.

That doesn’t mean we are ignoring this issue! Our teams are continuing our investigation in an attempt to make that necessary forward progress. At the moment, our best recommendation is for PayPal Donations users who are experiencing this error to switch to PayPal Standard. This error isn’t present there, and PayPal Standard is a great option for non-profits. We also highly recommend Stripe as an alternative gateway whenever possible.

I know this was quite a bit of unhappy information to share, and I wish that weren’t the case. My goal is to make online donations as successful and seamless as possible for you, so please let me know if you have any questions about this, I’m happy to help as much as I possibly can. If you’d like more information or a walkthrough for the workarounds I mentioned, I’m happy to field any questions you have about those as well.

Hi, @mbio86.

Sure we can help you. We wrote a detailed article covering step by step how to translate GiveWP using Loco Translate here https://givewp.com/documentation/resources/translating-give/translating-givewp-with-loco-translate/.

Let us know if it works for you.

Hi, @jadpm.

We’ve got a spot where you can ask this question directly to our development team, but the question will need to be more fleshed out there than it is here. I’d recommend passing along the exact code snippet you are attempting to use and what results from that snippet. The more focused the question is, the more likely our development team will be able to step away from their busy schedules to help with this sort of custom code.

You can reach out to them here https://github.com/impress-org/givewp/discussions.

Thanks for using GiveWP! Have a great day.