Fundolar
| 开发者 | fundolar |
|---|---|
| 更新时间 | 2026年9月5日 17:11 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Fundolar adds a donation shortcode to WordPress and connects to Fundolar Central for payment processing. Configure Stripe, PayPal, Paystack, Flutterwave, Pesapal, Mobile Money (UG), and more in your Fundolar dashboard, then sync them to your site.
What you get
- Shortcode
[fundolar_donate]— place the donation form on any page or post. - Fundolar Central — connect with your site key to sync payment gateways from a hosted dashboard.
- Appearance — preset amounts, currency, form layouts, and brand colors.
- Dashboard widget and Transactions list with fee breakdown (gross, 3.5% platform fee, net).
- Security — encrypted secret storage, capability checks, and nonces on sensitive actions.
安装:
Before you start
- WordPress 6.0 or newer and PHP 7.4+ (match the headers above; newer versions are recommended).
- TLS — your site should use HTTPS for production donations.
- Fundolar account — register at Fundolar Central and configure the payment methods you want to offer.
- Upload the
fundolarfolder towp-content/plugins/, or upload the ZIP via Plugins → Add New → Upload Plugin. - Activate Fundolar under Plugins.
- Updates are delivered through the WordPress.org plugin directory (Dashboard → Updates).
- In the admin, open Fundolar → Settings (or follow any onboarding links shown).
- Open Fundolar → Settings → Payments.
- Paste your site key from Fundolar Central.
- Click Connect, then Sync gateways.
- Enable payment methods in your Fundolar dashboard if none appear after syncing.
- Add
[fundolar_donate]to a page or post and publish. Run a small test donation.
- For branded logos on the form, add SVG (preferred) or PNG files to
wp-content/plugins/fundolar/resources/images/logos/using the filenames listed in the FAQ.
uninstall.php, which removes plugin options and the custom transactions table — back up data first if you need historical exports.屏幕截图:
常见问题:
Do I need a Fundolar account?
Yes. Create a free account at Fundolar Central, configure payment gateways there, and connect your WordPress site with the site key under Fundolar → Settings → Payments.
Does the plugin collect personal data?
Donation records in your database may include donor email and name when the form collects them. Card data is handled by your payment processor. See Privacy below.
cURL error 6 / Could not resolve host
Your server cannot reach Fundolar Central. Confirm outbound HTTPS is allowed and that DNS resolves app.fundolar.com. Contact your host if the problem persists.
Where do I get payment logos?
Add SVG or PNG files under wp-content/plugins/fundolar/resources/images/logos/ with these filenames:
stripe.svg,paypal.svg,paystack.svg,flutterwave.svg,pesapal.svg,mobile-money-ug.svg,payoneer.svg
更新日志:
1.5.0
- Reliably record successful Stripe and PayPal donations in WordPress and Fundolar Central.
- Preserve platform donation ids when updating PayPal transaction meta.
- Re-create / upsert Central donation records when status sync runs without a prior create.
- Hourly resync of completed donations that never linked to Central.
- Fundolar.com distribution: payments are managed exclusively through Fundolar Central (own API key fields removed from Settings).
- Updated admin UI, how-to guide, form messages, and notices for a Central-only setup.
- WordPress.org review response: explicitly list all external service domains in readme.
- Settings save uses an allowlisted, sanitized field set (no raw $_POST pass-through).
- Donation REST route detection no longer reads $_GET['rest_route'].
- WordPress.org package excludes plugins_api updater code and does not mutate active_plugins.
- Add Payoneer Checkout card payments beside Stripe for donors (embedded card fields + hosted fallback).
- WordPress.org review: document PayPal api-m and MarzPay (wallet.wearemarz.com) with terms/privacy links.
- Remove custom plugins_api update hooks on WordPress.org builds; stop auto-activating/deactivating other plugins.
- Replace WP_PLUGIN_DIR hardcoding with plugin_dir_path-based paths.
- Add nonce checks for gateway return URLs and OAuth returns; tighten MarzPay webhook verification via API re-check.
- Sanitize admin settings POST input and REST route detection inputs.