Skip to content
Democratizing Generosity - The best way to accept donations on WordPress
Branch: release/2.5.3
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github chore: update all GitHub urls to new org name Dec 12, 2018
assets/src fix: increase font size for connect banner Jul 15, 2019
blocks fix: pass display_style instead of display_type in shortcode param Jul 3, 2019
includes chore: do no need to convert array to array again Jul 13, 2019
languages chore: add change log for 2.5.1 release Jul 12, 2019
sample-data chore: update sample wordpress.sql Apr 18, 2019
templates Merge branch 'master' into release/2.5.0 May 28, 2019
tests chore: prevent test from failing because of zero payment Jun 25, 2019
.babelrc chore: remove unnecessary `not dead` text Mar 25, 2019
.editorconfig 1. Removing old bower and other unneeded files Dec 27, 2017
.eslintignore Ignore node_module folder for eslint Jan 15, 2018
.eslintrc Fix lint errors for blocks Aug 21, 2018
.gitattributes New .gitattributes file export ignore file - brought over from Woo Apr 10, 2017
.gitignore Removing yarn lock file Jan 10, 2018
.scrutinizer.yml Touched up scrutinizer file Aug 3, 2017
.travis.yml chore: prevent travis failing for PHP 5.4 May 8, 2019 fix: update incorrect email address Oct 25, 2018 chore: update all GitHub urls to new org name Dec 12, 2018 Merge branch 'release/2.5.0' of i… Jun 7, 2019
changelog.txt chore: update all GitHub urls to new org name Dec 12, 2018
composer.json Merge branch 'master' into release/2.5.0 Jun 7, 2019
composer.lock Merge branch 'release/2.5.0' into issue/4076 May 8, 2019
docker-compose.yml fix: mount WordPress folder instead of just plugin Dec 13, 2018
give.php chore: create new 2.5.3 branch Jul 17, 2019
license.txt chore: update copyright text Dec 12, 2018
package-lock.json chore: update package-lock.json Jun 20, 2019
package.json chore: add 2.5.2 branch Jul 12, 2019
phpcs.ruleset.xml fix: php ruleset added for check give text domain Jan 18, 2019
phpunit.xml Update include paths May 17, 2017
readme.txt chore: create new 2.5.3 branch Jul 17, 2019
uninstall.php chore: update copyright text Dec 12, 2018
webpack.config.js Merge branch 'master' into release/2.5.0 Jun 7, 2019
wpml-config.xml Add WPML config file May 15, 2017


WordPress version WordPress Rating WordPress Downloads Build Status Scrutinizer Code Quality License

Welcome to the GiveWP GitHub repository. This is the code source and the center of active development. Here you can browse the source, look at open issues, and contribute to the project. We recommend all developers follow the GiveWP development blog to stay up to date on the latest features and changes.

Getting Started

If you're looking to contribute or actively develop on Give then skip ahead to the Local Development section below. The following is if you're looking to actively use the plugin on your WordPress site.

Minimum Requirements

  • WordPress 4.8 or greater
  • PHP version 7.0 or greater
  • MySQL version 5.6 or greater
  • Some payment gateways require fsockopen support (for IPN access)
  • cURL version 5.40 or higher
  • An SSL certificate -- while this is not strictly required, it is highly recommend. If you are converting your site to use SSL/HTTPS now, we have a detailed guide to help you here.

Development Requirements

  • Node 10 (not compatible with 11+)
  • Composer

Automatic installation

Automatic installation is the easiest option as WordPress handles the file transfers itself and you don't need to leave your web browser. To do an automatic install of Give, log in to your WordPress dashboard, navigate to the Plugins menu and click "Add New".

In the search field type "Give" and click Search Plugins. Once you have found the plugin you can view details about it such as the point release, rating and description. Most importantly of course, you can install it by simply clicking "Install Now".

Manual installation

The manual installation method involves downloading our donation plugin and uploading it to your server via your favorite FTP application. The WordPress codex contains instructions on how to do this here.


This repository is not suitable for support. Please don't use GitHub issues for support requests. To get support please use the following channels:

Local Development

To get started developing on the Give platform you will need to perform the following steps:

  1. Create a new WordPress site with give.test as the URL

  2. cd into your local plugins directory: /path/to/wp-content/plugins/

  3. Clone this repository from GitHub into your plugins directory:

  4. Run composer to set up dependancies: composer install

  5. Run npm install to get the necessary npm packages: npm install

  6. Activate the plugin in WordPress

That's it. You're now ready to start development.

NPM Commands

Give relies on several npm commands to get you started:

  • npm run watch - Live reloads JS and SASS files. Typically you'll run this command before you start development. It's necessary to build the JS/CSS however if you're working strictly within PHP it may not be necessary to run.
  • npm run dev - Runs a one time build for development. No production files are created.
  • npm run production - Builds the minified production files for release.
Note only compatible with Node 10

Development Notes

  • Ensure that you have SCRIPT_DEBUG enabled within your wp-config.php file. Here's a good example of wp-config.php for debugging:
     // Enable WP_DEBUG mode
    define( 'WP_DEBUG', true );
    // Enable Debug logging to the /wp-content/debug.log file
    define( 'WP_DEBUG_LOG', true );
    // Loads unminified core files
    define( 'SCRIPT_DEBUG', true );
  • Commit the package.lock file. Read more about why here.
  • Your editor should recognize the .eslintrc and .editorconfig files within the Repo's root directory. Please only submit PRs following those coding style rulesets.
  • Read - it contains more about contributing to GiveWP.
You can’t perform that action at this time.