Find a Cartdini checkout field that is not appearing

Use a staging store with the same active theme and checkout extensions. Open WooCommerce → Cartdini and note the field key, answer type, location and enabled status. Keep a screenshot of the current configuration. Do not uninstall Cartdini or erase settings to troubleshoot a missing field.

Confirm the question is enabled and that the editor reports the configuration as saved. Recipes, imports and restored drafts require review and Save questions & fields. Shared address and button controls have their own save action; saving one section does not save the other.

If the editor reports a stale draft or concurrent change, compare the saved configuration before retrying. Do not overwrite another administrator’s work simply to make a warning disappear.

Use Cartdini’s Open checkout or Test saved checkout link and ensure the cart contains a product. Check WooCommerce’s assigned checkout page. A page using the Checkout block is different from one using the Classic checkout shortcode.

Extra questions add new information; Existing checkout fields changes supported native controls. Check Order information, Contact information or Billing + shipping according to the question’s configured location. A billing-and-shipping answer can be absent from shipping when no shipping is needed. Compare Classic and Blocks controls.

Try both a matching and nonmatching state. Check the earlier answer, product or category, shopper role, shipping/payment method or total used by the rule. Earlier questions must be enabled and available in the same supported location. A hidden or invalid source answer does not reveal a dependent question.

A question that stays hidden for an ordinary order may be working correctly. For a gift-message rule, selecting the gift checkbox should reveal the follow-up. Review the conditional gift example. If a Pro control reports paused configuration or activation required, follow that specific message; do not recreate the question in a different edition.

Country-specific address requirements remain controlled by WooCommerce. Some fields are intentionally hidden or required for the selected country. Classic-only placeholder/text overrides do not change Blocks controls. Check the exact compatibility matrix before expecting identical controls.

Place a new staging test order after saving. Existing orders are historical snapshots; editing a question does not backfill answers into them. A blank, unchecked or conditionally hidden answer may have no visible entry.

Review the question’s selected display destinations for order administration, customer views and emails. Email rendering is separate from email delivery: check the generated order content and your mail delivery evidence independently. Pro Orders-list columns must be selected for your administrator account and enabled in Screen Options.

On staging, compare with a representative standard theme and only WooCommerce, Cartdini Free and—when needed—Pro active. Reintroduce checkout extensions one at a time. Review browser errors and WordPress logs without posting private data. Exclude checkout from page caching according to your hosting setup, then test a fresh shopper session.

Contact Cartdini support with the public plugin versions, WordPress/WooCommerce/PHP versions, checkout type, theme, field key, reproduction steps and sanitized screenshots. Say what you expected and where the field disappears. Do not send licence keys, passwords, payment details or real customer answers.