Compatibility
Built for current WordPress sites running Cornerstone Forms.
Use this page before purchase and before production deployment. It sets expectations for the supported stack, staging checks, and what support can realistically diagnose.
Technical baseline for release 1.0.7.
The commercial build is a 33-file ZIP for Cornerstone Forms sites. The plugin readme declares WordPress 5.0+, Tested up to WordPress 6.4, PHP 7.4+, and the PHP OpenSSL extension.
| Area | Supported baseline | Why it matters |
|---|---|---|
| WordPress | WordPress 5.0 or newer. Plugin readme: Tested up to WordPress 6.4. | The plugin uses standard admin, option, AJAX, metadata, and update APIs. |
| PHP | PHP 7.4 or newer. | Encryption, JSON handling, and updater requests need a maintained PHP runtime. |
| OpenSSL | OpenSSL extension enabled. | AES-256-GCM encryption and legacy payload handling depend on OpenSSL. |
| Cornerstone Forms | Installed and active on the WordPress site. | The field toggle and submission flow are intentionally tied to Cornerstone Forms. |
| Supported field controls | Input, Textarea, Select, Checkbox List, Date Picker, and Dropzone. | The builder toggle is added only to supported Cornerstone form controls. |
| Action Scheduler | Recommended for delayed encryption and retention jobs. | Larger sites should not rely on a single request to process background work. |
| Browser/admin UI | Current Chrome, Safari, Firefox, or Edge. | Admin screens use ordinary WordPress UI patterns and should be tested by staff who manage submissions. |
What the release artifact proves
- Current commercial release:
1.0.7. - Commercial ZIP: 33 files under
cs-forms-encryption/. - SHA-256 checksum:
c3d05c9575e40c32a342126ff018e4690f806ef3d2745c7fcdd41655a37f2956. - The ZIP excludes the local test suite and root development test PHP file.
- Release files are delivered through the private update/download channel, not as public static assets.
Feeds, payments, and CRM integrations
If another integration needs plaintext during submission processing, use Delay Encryption and test the flow on staging. The plugin can keep selected values readable long enough for email, CRM, payment, or export logic to run, then encrypt the configured fields after the delay.
Staging checklist
- Install the commercial ZIP on staging first.
- Set `CS_FORMS_ENCRYPTION_KEY` outside ordinary support tickets or screenshots.
- Activate the license under Settings > Encryption License.
- Enable Encrypt Field on one low-risk test field.
- Submit one test entry and confirm authorized users can decrypt it.
- Confirm unauthorized users cannot see decrypted values or protected files.
- Test any CRM, email, payment, or export flows before encrypting production fields.
Support expectations
Support can help with activation, update access, installation questions, and plugin settings. Support cannot recover lost encryption keys, inspect private customer submissions, or replace a site-specific legal/security review.
When to wait
Do not deploy directly to production if the site has complex custom submission hooks, critical exports, payment feeds, or client-facing portals that have not been tested with encrypted fields on staging.
What this page does not prove
Compatibility notes are technical notes. They do not mean live checkout is open, legal pages are final, Stripe Tax is configured, or a site-specific compliance review has been completed.
Ready for a staging test?
Review the installation guide, confirm the security model, then buy the plan that matches the number of production sites you will activate.