Matheus Martins

Hi, @llykate2024.

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

What you are likely missing is the ID to embed the form. Can you share the shortcode you are using?

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

Hi, @jgoethel.

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

Warning messages like this display when your site has “Debug Mode” turned on. Debug mode is a method for developers to use to find issues in their code and compatibility problems with different versions of PHP (the server language WordPress uses). Debug mode is usually only used on development sites or non-live sites.

In the meantime while you get the problem resolved, here’s how you can hide those warnings: in your wp-config.php file (which you can get to via SFTP or through your web host’s file manager) look for a line like this:

define(‘WP_DEBUG’, true);

Replace it with the following lines:

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);
@ini_set(‘display_errors’, 0);

Again, this method is normally only used for development, not on live sites.

If you need assistance with that, your web host should be able to help. Also, there is some official documentation on that: https://codex.wordpress.org/WP_DEBUG

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

Hi, @bergenp0.

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

This seems to be a permalink issue. You can navigate to your back end, then to your settings > permalinks and there you can chose a pattern. I suggest post name because it’s more user friendly. After that, test your form again.

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

Hi, @subhashsrs.

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

It depends on the form you are using. If you are using v2 forms (legacy, classic and multi-step forms), you need to disable it under donations > settings > payment gateways > gateways > option-based forms.

On the other hand, if you are using Visual Form Builder (VFB) forms, then you need to disable it under donations > settings > payment gateways > gateways > visual form builder.

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

Hi, @soaracademyandtutoring.

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

Every time a donation is made on your site – or attempted, GiveWP creates a new entry on the logs section on the dashboard that gives us further information on what is happening. Can you send me logs for when you try to make a donation and get the errors below? You can find the logs under Donations > Tools > Logs.

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

Hi, @mexwebmaster.

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

Warning messages like this display when your site has “Debug Mode” turned on. Debug mode is a method for developers to use to find issues in their code and compatibility problems with different versions of PHP (the server language WordPress uses). Debug mode is usually only used on development sites or non-live sites.

In the meantime, while we get the problem resolved, here’s how you can hide those warnings: in your wp-config.php file (which you can get to via SFTP or through your web host’s file manager) look for a line like this:

define(‘WP_DEBUG’, true);

Replace it with the following lines:

define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);
@ini_set(‘display_errors’, 0);

Again, this method is normally only used for development, not on live sites.

If you need assistance with that, your web host should be able to help. Also, there is some official documentation on that: https://codex.wordpress.org/WP_DEBUG. Now, we should check why the page is not working as it should. I noticed that the error you shared with me says: “Cannot modify header information – headers already sent by,” is frequently related to 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.

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.

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

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

Based on the error log you shared with me, it looks like something was blocking the /wp-content/plugins/give/vendor/autoload.php file. Maybe during an update, this file was not carried over.

Before taking any steps for troubleshooting or updating, I highly recommend taking a good backup of the site you can confidently restore from. Having a backup of your site is essential to a solid workflow, and will allow you to restore to a previous version of the site if you run into any issues. You can read more about our top recommendations for taking a backup here: https://givewp.com/backup-for-faster-troubleshooting/.

Now, you might need to ask your host to delete the give folder directly from your server and then you can reinstall GiveWP. Can you give it a try?

Hi, @um324.

3 – can you clarify what error you meant?

4 – Currently, we do not have a way to change the columns on the donation page.

Although we do not have this feature out of the box, it would be exciting and valuable to understand how it would work for you and improve your workflow, so the product development team has some insights into how it would behave.

Also, is there any workaround that you are using? It would be good to hear from you about that too, and what this feature would allow you to do. All ideas are appreciated, and I’m happy to share your insights with the product development team so that they can discuss the feasibility of this feature.

I hope this clarifies, and I look forward to hearing back from you!