| 开发者 | drplugin |
|---|---|
| 更新时间 | 2026年11月6日 04:22 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
localhost or staging.example.com, do not count toward the activation limit.
Your plugin talks to the store through a public REST API to activate, validate and deactivate a key.
Updates for licensed sites
Upload a release with its version number and changelog. Sites with a valid license see it on their Plugins screen, read the changelog under View details and update like any other plugin. Every download goes through a signed link that expires, and the license key never appears in it.
Add the free update client to the plugin you sell to connect it to your store.
Store features
--releasecart-* CSS custom properties.
Documentation
Guides for setup, license keys, the update client and the licensing REST API are in the ReleaseCart documentation.
ReleaseCart Pro
ReleaseCart Pro is a separate plugin that adds to this one, so both stay active. It adds subscriptions through Stripe and PayPal, plan changes for Stripe subscribers, failed payment reminders, abandoned cart emails, EU and UK VAT on one-time sales, PDF invoices, signed license answers, offline and team licenses, release channels, an analytics dashboard, an affiliate program and imports from other stores.
External services
ReleaseCart connects to Stripe, and to webhook endpoints you add yourself. It makes no other outbound requests and sends no telemetry.
Stripe (payments). When you connect a Stripe account, your server calls the Stripe API at api.stripe.com to read the account's country, save each buyer as a Stripe customer, and create and refund payments. It sends the buyer's name, email and billing address, the products bought, the amount, the currency and ReleaseCart's order and customer identifiers. On checkout pages the buyer's browser loads Stripe.js from js.stripe.com, so Stripe collects the card details directly. This happens only after you add Stripe keys: when you save them, at checkout or for a refund. See the Stripe terms of service and privacy policy.
Your webhook endpoints (optional). If you add endpoints under ReleaseCart > Settings > Webhooks, ReleaseCart sends signed JSON notifications about orders, refunds, licenses and new customers to those URLs. They include customer email addresses and full license keys. Nothing is sent until you add an endpoint.
Source code
The JavaScript and CSS in assets/admin/build and the JavaScript in assets/blocks/build are compiled with @wordpress/scripts. The source and build setup are at github.com/drplugin-projects/releasecart. To rebuild, run npm install, then npm run build.
Bundled libraries: Action Scheduler 4.2.0 (GPLv3 or later), installed by Composer in vendor/woocommerce/action-scheduler, and TanStack Query 5.101.2 (MIT), compiled into the admin JavaScript.
https://your-site/wp-json/releasecart/v1/webhooks/stripe with the events payment_intent.succeeded, payment_intent.payment_failed and charge.refunded. Then open ReleaseCart > Settings > Payments, add your Stripe keys and the endpoint's signing secret, and leave Stripe mode on Test.No. You pay only Stripe's own fees.
Add the ReleaseCart update client to each plugin you sell. It asks your store for new versions, and WordPress shows them on the Plugins screen like any other update. A site with an expired or unknown license still sees the new version, but gets no download link.
Yes. Leave Licensed product off for files that need no key. A theme can carry a license key, but the update client delivers plugin updates only.
No. localhost, hosts that end in .test, .local or .dev, hosts that start with staging. or dev., and private or reserved IP addresses never count. They still show in the license's activations.
The update client keeps using its last good answer for up to 72 hours. After that it shows no update until your store answers again. The customer's site keeps working.
Yes, for card payments. Stripe handles 3D Secure. ReleaseCart Pro adds PayPal.
Yes, it is on by default. When a guest later registers or signs in with the same email, ReleaseCart links their orders and licenses to the account.
Yes, with ReleaseCart Pro. It imports products, customers, orders, license keys and activations from Easy Digital Downloads 3.x, License Manager for WooCommerce and SureCart. Subscriptions, discount codes and download files are not imported.
Only on its own admin screens, and only while Pro is not active: a ReleaseCart Pro menu item and the screen it opens, a ReleaseCart Pro tab under Settings, and a one-line note you can dismiss. Nothing shows on other admin screens or on your site.
ReleaseCart keeps it unless you turn on Delete all data on uninstall under ReleaseCart > Settings > General before you delete the plugin. That setting removes its tables, options, capabilities, package files and the pages it created, and data that add-ons keep under the ReleaseCart name. On multisite, each site's own setting decides.
Its data is in the WordPress Export Personal Data and Erase Personal Data tools. Erasing anonymizes the customer and their orders, which stay for your accounts, and disables their licenses.
Yes, under releasecart/v1. The licensing routes are public and take the license key. The management routes need a capability and accept a session, an Application Password or a ReleaseCart API key.