Back to Community
Home / Community / Plugin → Checkout field editor (checkout manager) for woocommerce

Troubleshooting Checkout Field Editor for WooCommerce: Common Issues and Solutions

36 threads Sep 10, 2025 Plugin → Checkout field editor (checkout manager) for woocommerce

Content

If you use the Checkout Field Editor (Checkout Manager) for WooCommerce to customize your checkout experience, you might occasionally run into issues where your custom fields don't appear, behave incorrectly, or conflict with other parts of your site. This guide covers the most common problems and their solutions, based on community reports and resolutions.

1. The Most Common Issue: WooCommerce Blocks Incompatibility

The Problem: Your custom checkout fields do not appear on the checkout page, or changes made in the plugin's settings do not take effect.

Why It Happens: This is by far the most frequently reported issue. The current version of the free Checkout Field Editor plugin is not compatible with checkout pages built using the modern WooCommerce Blocks (e.g., the Checkout Block). WooCommerce Blocks use a different technical framework that lacks the necessary hooks for this plugin to function.

The Solution: You must ensure your checkout page is built using the classic [woocommerce_checkout] shortcode, not a block.

  1. Edit your checkout page in the WordPress editor.
  2. Remove any WooCommerce Checkout Blocks.
  3. Add the shortcode [woocommerce_checkout] to the page.
  4. Update or publish the page.

Once the shortcode is in place, your custom fields should appear correctly. The 'Checkout Field Editor (Checkout Manager) for WooCommerce' team has indicated they are working on block compatibility for a future update.

2. Conflicts with Other Plugins

The Problem: Fields are missing, validation doesn't work, or parts of the checkout form become unresponsive. This is often reported with plugins like PayPal Payments, Stripe, Fluid Checkout, or other checkout add-ons.

Why It Happens: Many plugins modify the checkout process. When two plugins try to control the same part of the form, it can lead to JavaScript conflicts or overriding functions that break expected behavior.

The Solution: A standard troubleshooting step is to identify the conflict.

  1. Temporarily deactivate the Checkout Field Editor plugin.
  2. Check if the problem persists. If it does, the issue is likely with another plugin or your theme.
  3. If the problem is resolved after deactivation, reactivate the Checkout Field Editor.
  4. Begin deactivating other plugins one-by-one, checking the checkout page after each deactivation, until you find the one causing the conflict.
  5. Once the conflicting plugin is identified, you may need to choose between them, look for an alternative, or wait for the developers to address the compatibility issue.

3. Fields Not Saving to Orders or Appearing in Emails/PDFs

The Problem: Customers can fill out a custom field, but the data is not saved to the order and does not appear in order confirmation emails or PDF invoices.

Why It Happens: In the free version of the plugin, the ability to display field data in emails and other documents is a premium feature. Some third-party plugins may also not be designed to read and display these custom field values.

The Solution: For the free plugin, displaying data in emails and PDF invoices is not supported. If this is a critical requirement, you may need to investigate premium alternatives. For other display issues, ensure you are using the classic shortcode checkout page, as data is less likely to save correctly on block-based pages.

4. Styling Issues with Select Fields

The Problem: After installing the plugin, dropdown (select) fields or other form elements look different—often smaller or with altered padding.

Why It Happens: The Checkout Field Editor plugin itself adds minimal CSS and primarily relies on your theme's styles. However, the way it outputs form fields can sometimes interact poorly with a theme's existing CSS rules.

The Solution: This is typically a theme-specific issue. You can use your browser's inspector tool to identify the new CSS rules affecting the element and then add custom CSS to your theme (e.g., in the Customizer) to override them and restore the desired appearance.

5. Advanced Custom Fields (ACF) Conflict

The Problem: The "Custom Fields" metabox disappears from the order details screen when both ACF Pro and Checkout Field Editor are active.

Why It Happens: ACF Pro has a setting that removes the standard WordPress custom fields metabox by default, which also hides the data from the checkout field editor.

The Solution: Add the following code to your child theme's functions.php file. This filter tells ACF to leave the standard metabox intact.

add_filter( 'acf/settings/remove_wp_meta_box', '__return_false' );

By following these troubleshooting steps, you can resolve the majority of issues encountered with the Checkout Field Editor for WooCommerce. Always remember to clear your site and browser cache after making changes, and ensure you are using the classic checkout shortcode for the plugin to work as intended.

Related Support Threads Support