Download the PHP package digitalduz/slswc-client without Composer
On this page you can find all versions of the php package digitalduz/slswc-client. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download digitalduz/slswc-client
More information about digitalduz/slswc-client
Files in digitalduz/slswc-client
Package slswc-client
Short Description SDK for WordPress plugins and themes to check updates, manage licenses, and enforce DRM against an SLSWC-powered license server.
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package slswc-client
SLSWC Client SDK
PHP SDK for WordPress plugins and themes to check for updates, manage licenses, and enforce DRM against an SLSWC-powered license server.
Installation
Usage
Plugin Integration
Theme Integration
Plugin Headers
Add SLSWC headers to your plugin's main file:
DRM (Optional)
Multi-consumer safety
Multiple plugins and themes on the same WordPress install can embed this SDK independently. Each consumer receives its own isolated Plugin / Theme / ApiClient instance, keyed internally by:
Plugin::get_instance( $url, $base_file, $args )— keyed by$base_file(the consumer's main plugin file path).Theme::get_instance( $url, $base_file, $args )— keyed by$base_file(the consumer's theme directory path).ApiClient::get_instance( $url, $text_domain )— keyed by$text_domain.
text_domain, DRM option keys (<text_domain>_drm_*), LicenseDetails option key (<text_domain>_license_details), DRM admin notice hooks, and scheduled license-check cron events therefore stay isolated across consumers. There is no shared mutable state between two consumers on the same site.
Consumers are expected to pass a stable $base_file (a plugin's main __FILE__ is ideal) and a unique text_domain per product. Reusing the same text_domain across two consumers will share a registry slot and is unsupported.
Documentation
Full integration guides: licenseserver.io/documentation
License
GPL-2.0-or-later
