This tab includes advanced settings intended primarily for developers. These settings control how donors access their information, how data is managed if you delete the GiveWP plugin, disabling the “the_content()” filter on GiveWP single form pages, moving all GiveWP scripts to the footer, and using Akismet SPAM protection. Use these settings with caution and only if you know exactly what to expect and how to reverse it.

Advanced Settings Options overview

Remove Data On Uninstall

Settings Type: Radio buttons
Options: Yes, Remove all data | No, keep my GiveWP settings and donation data
Default: No, keep my GiveWP settings and donation data

This setting is only intended for when you are uninstalling GiveWP from your site. It ensures that data that was generated by GiveWP and is intended only for GiveWP is removed from your site and database completely when you uninstall.

Because this process is irreversible, this setting is off by default and it would be very difficult for users to learn that all their data was unintentionally lost simply because they deleted a plugin and re-installed it again.

Note that this setting also controls GiveWP add-ons which add data. For example, the Recurring add-on adds some recurring-specific data, and if you uninstall Recurring while this setting is selected, you will delete all recurring-specific data.

Default User Role

Settings Type: Drop-down/select
Options: All registered user roles on the site.
Default: GiveWP Donor

This setting allows you to designate the role that donors are assigned when they donate and your form support registration. Read more about enabling registration on your GiveWP forms here.

Read more about GiveWP User Roles here.

the_content Filter

Settings Type: Radio buttons
Options: Enabled | Disabled
Default: Enabled

The GiveWP single form uses the WordPress standard the_content() filter for its content area. This can sometimes have unintended consequences. For example, perhaps you have a social sharing buttons plugin which automatically adds social buttons at the top or bottom of all your posts and pages. You might not want that on your Donation forms. Selecting “disabled” will prevent that from happening.

Script Loading Location

Settings Type: Radio buttons
Options: Head | Footer
Default: Head

Loading javascript files in the footer of your site can often improve the page load time. Other times doing so can cause unintended problems. This setting defaults to “Head” within GiveWP because loading scripts at the top of the page results in more reliable functionality for GiveWP forms across a variety of unpredictable themes and server environments. Selecting to load the scripts in the footer can increase page load times slightly.

Babel Polyfill Script

Settings Type: Radio buttons
Options: Enabled | Disabled
Default: Enabled

We have enabled the Babel Polyfil script by default to support certain Stripe related functionalities in legacy browsers.

If a web console displays a warning message related to duplicate Babel Polyfill scripts loading, it’s likely your site is loading 2 scripts of Babel Polyfill. To resolve this, just set it to disabled which will remove the script loaded from GiveWP and continue to use the other script that is loading elsewhere on your site.

Akismet SPAM Protection

Settings Type: Radio buttons
Options: Enabled | Disabled
Default: Disabled

If your site is experiencing SPAM donations or SPAM donors, this setting integrates your GiveWP form with the Akismet database of known spammers to reduce the amount of SPAM. This setting requires the use of the Akismet plugin. Note that use of Akismet may involve a monthly fee.

GiveWP Cache

Settings Type: Button

Clicking this button will clear GiveWP’s internal cache.

The plugin stores common settings and queries in the cache to optimize performance. Clearing cache will remove and begin rebuilding these saved queries.

To see your refreshed (uncached) site, open your site in a different tab and check that your desired change is now visible. If you already had your site open, you might need to hard refresh as well before it will appear.

Note that this does not affect any caching plugins or server-side caching that you might be using already or in addition. For complete troubleshooting regarding cached items, we suggest clearing and disabling all caching plugins and server-side caching until the issue is resolved.