When something looks wrong

The things that most often look wrong, why they happen, and what to do. If yours is not here, write to me with the product page’s address and what you expected to see.

• The configurator does not show on a product
• There is no Add to basket button
• “Saved, but not live yet”
• “The prices on this page were just updated”
• An old basket line stops the checkout
• A page cache, and changes that do not show
• Files: “Too many files for now”

The configurator does not show on a product

• It is a variable product. ConfigKit works on simple products only. Change the product type to Simple product, and put the choices in the configurator.
• The configurator is a draft. In ConfigKit, Configurators its card must say Live. A template stays a draft until “These are my own prices” is on.
• The product says None. Under Product data, General, Configurator set to None keeps the normal Add to cart, whatever the categories say.
• Another rule wins. A configurator named on the product beats a category, and a deeper category beats its parent. See Which one wins.

There is no Add to basket button

With the Steps layout, the buy button waits for the last step: use Next. With “Ask for a quote (no basket)” there is no buy button at all, only Ask for a quote.

“Saved, but not live yet”

The builder found something a customer could not buy: an option without a price type it knows, a formula that cannot be read, a size limit where the smallest is above the largest, or, for a template, example prices not yet confirmed as yours. Each is marked in red on its block and counted at the bottom; click one in the list there to go to it. Fix them, then save again.

If the configurator was already live, it stays live exactly as it was: the builder says “Not live yet”, keeps your changes, and customers go on buying the live version until the changes can go live.

“The prices on this page were just updated”

A customer sees this when the page they had open was drawn before you saved a change to the configurator, for example because a page cache kept the old page, or the tab was open for hours. Nothing is added, the page now shows the new prices, and the customer makes their choices again. It stops anyone paying a price that differs from the one they saw.

An old basket line stops the checkout

If you take a configurator down, or move a product to another one, lines already in customers’ baskets can no longer be priced, so the checkout asks the customer to remove them. Lines that still fit the saved configurator are simply priced again with your current prices.

A page cache, and changes that do not show

ConfigKit works behind page caches: nothing on the page is personal, prices and dates are worked out in the visitor’s browser, and files and quote requests go to your server directly. Keep your cache’s usual WooCommerce setting that never caches the basket, checkout and account pages.

After you change a configurator, clear your cache (or just that product’s page) so visitors get the new prices straight away. If you forget, customers on an old page are told the prices were updated, as above, rather than being charged something they did not see.

Files: “Too many files for now”

One visitor’s address can send 200 files or 2,000 MB an hour. A shop behind one office network shares one address, so a busy team testing uploads can reach it. It clears by itself within the hour. See Let customers send files.