Cartdini administrator notes

Detailed recovery, privacy and setup behavior. See readme.txt for the current introduction and installation steps.

== Local editor recovery ==
Cartdini keeps an unfinished editor configuration in this browser tab, scoped to the current site and signed-in administrator. It stores field settings and, separately, native Blocks settings; it does not store preview answers, shopper information, file contents or license credentials. Recovery is available for 24 hours. Closing the tab or clearing browser storage can remove the copy. Expired or unreadable copies can be cleared in the editor. Browser storage may be unavailable; the editor explains when recovery cannot be saved.

Resume only loads a draft. It checks the saved configuration revision again and never publishes automatically. When saved settings have changed, review the saved and recovered values and explicitly select what to recover into a fresh draft. Newer-only fields remain present; recovery does not publish or bypass the latest saved revision. Custom fields and native Blocks settings retain their separate save actions. A remembered Pro task is optional and does not install anything. After you explicitly choose a task or open its Pro plans, its minimal task reference can be kept in WordPress user metadata for this administrator and store for seven days. You can clear it or resume it after setup; current fields, permissions and compatibility are checked again. Preview navigation preferences are also local to this administrator and store. Existing contextual suggestion dismissals remain browser-scoped. No draft or preference data is transmitted to Cartdini.


A pending configuration change can retain one bounded recovery record until its history is finalized. Unchanged saves and failed attempts do not consume older history entries. If settings were saved but history is still pending, the editor says so: reload before retrying. Unrecognized recovery records are preserved and stop further configuration changes; contact support rather than deleting them. These records contain field configuration, not shopper answers. Deactivation and deletion retain this configuration recovery data.

== Installation ==

Current matched release: Free 1.8.5 and Pro 1.8.5. Pro 1.8.5 requires Free 1.8.4 or newer. Existing Pro 1.8.4 remains compatible while you update Free first.

1. Install and activate WooCommerce 9.9 or newer.
2. Upload this ZIP through Plugins > Add New > Upload Plugin.
3. Activate Cartdini.
4. Open WooCommerce > Cartdini, configure and save fields.
5. Test complete checkout flows before production.

To upgrade an existing installation, back up the site, then upload this ZIP and choose Replace current with uploaded. Saved fields, settings and order answers are retained. If you use Pro, update Free first, then update Cartdini Pro to 1.8.5. Older incompatible add-ons pause safely until updated; their saved definitions remain retained during the update. Test your saved configurations and complete checkout flows on staging before updating the live store.

Free 1.8.0 and newer require Pro extension API 6. When upgrading an older pair, complete both plugin replacements together during a maintenance window: older Pro versions pause until updated so they cannot silently ignore new date restrictions. Pro license and update access remain available between replacements. An existing Pro 1.8.2 installation can remain in place when updating Free to 1.8.5.

Configurations that use the expanded 1.3.0 format are saved separately. Cartdini preserves the previous compatible configuration and a recovery copy. An older plugin pair uses that older configuration; it cannot use the new controls. If an older version changes settings, the editor asks you to review both copies before choosing one. Back up the whole site before a downgrade, including orders and customer data.

== Frequently Asked Questions ==
= Does activation change my checkout? =
A new installation enables no sample fields. After you save your configuration, it applies while Cartdini is active. Reactivating the plugin resumes the saved configuration.
= Does it support Checkout Blocks? =
Yes. All nine Free custom field types support Checkout Blocks. Company, Phone and Address line 2 use shared WooCommerce visibility and requirement controls. Ten shared address labels/order and the default Place Order button text can also be edited. Address placeholders and contact email remain native controls; Classic has additional text overrides.
= Does uninstall delete order data? =
No. Deactivating or deleting Cartdini retains settings and saved answers. While Cartdini and WooCommerce are active, WordPress personal-data exports include Cartdini answers stored in customer accounts and matching orders. Confirmed erasure requests remove account answers; order erasure follows the store's WooCommerce retention settings. Removing a field from the editor does not erase historical answers. If an order has retained private upload records and the compatible upload eraser is unavailable, Cartdini retains order identity and checkout answers and reports that the request needs attention. Reinstall and activate a compatible Pro, then retry; privacy erasure does not require a license. Damaged or unreadable storage records also require attention. Keep Free active during these requests; removing both plugins leaves retained data outside their privacy tools.

== Privacy ==
Checkout answers are stored in the store's WordPress/WooCommerce database, with orders and, for supported contact/address fields, customer accounts. Display settings control where answers appear on orders and supported emails; they do not delete the answers. Cartdini Free does not send data to Cartdini or another external service. Store owners should request only necessary information and explain its purpose, recipients and retention in their privacy policy. Suggested text is available in WordPress Settings > Privacy.


== Local Pro guidance preferences ==
Pro preview navigation, a chosen task and optional local usage counts belong to the signed-in WordPress administrator on this store. A chosen task expires after seven days. Usage counts are off by default; if enabled, counts of preview opens, pricing-link clicks and matching workflow saves expire after 90 days. Expired task and count records are scheduled for removal through WordPress cron while the plugin is active; they are included in personal-data export and erasure. Counts contain no shopper answers, checkout content or license keys and are not sent to Cartdini. Turning counts off clears them. These counts describe local plugin actions, not purchases or a paid upgrade rate. Browsing an example does not consent to tracking or publish checkout settings.

== Source code ==
All executable PHP, JavaScript and CSS source is included in this plugin. The shipped assets are the maintained readable source; no compilation step or external library download is required. JavaScript translations use WordPress wp-i18n.

== Pro setup ==
The separately installed Pro 1.8.5 add-on requires an initial license activation for its editing and tools. Free functionality remains available without a license. A compatible active add-on can link an authorized administrator to its license setup; Free itself makes no license request. Saved Pro checkout behavior remains active while its editing is locked.

The local setup view distinguishes absent, inactive and incompatible Pro installations. With the required permissions, it opens WordPress's native ZIP upload screen or the current site's Plugins screen. Use WordPress's Activate Plugin or Activate control to activate Pro. A successful single manual activation opens license settings for an administrator with license-management permissions; connect explicitly if needed, then return to Cartdini. The separate Return to Cartdini link remains available and never activates Pro. WordPress handles package installation, compatibility checks and activation errors. Browser draft recovery must succeed before leaving with unfinished work. After returning, review and resume any recovered draft, then continue your task and save explicitly. Activation does not publish the draft. Network installation screens require a manual return to the originating site; inaccessible network screens use a manual administrator handoff. This setup view performs no purchase, remote download, network activation or license connection.

== Workspace appearance ==
On first use, the editor keeps WordPress navigation visible. Choose Full screen when you want a wider workspace. Full screen and Exit full screen remember your choice in this browser for the current site and signed-in administrator, and reuse it on later visits. Exit full screen restores WordPress navigation; Back to WordPress leaves the editor. Clearing browser storage removes the saved preference. If storage is unavailable, WordPress navigation stays visible initially and the layout toggle still works for the current page. Layout controls do not save checkout settings. Locally bundled fonts make no external request. Without JavaScript, the existing editor requirement notice and WordPress navigation remain available.

