Here's my use case: I have a product display that requires one or more products, which can be added via Inline entity form - Multiple values. I want these products to be new products, so I've left "Allow users to add existing products" unchecked. There are multiple possible product types which can be associated with the product display.

If the user makes a mistake when they choose the product type, it's impossible to cancel the product entry. The user must complete a dummy entry, save it, and then remove it to correct his/her mistake.

I would argue that even without this use case, hiding the cancel button is unnecessary and pointless, as the same effect can be achieved by removing the added product.

Comments

bojanz’s picture

bojanz commented
Title: Cancel button should not be hidden on IEF Add form » Cancel button should not be hidden on IEF Add form if multiple bundles are allowed
Status: Active » Fixed

Committed a fix for your use case, that was a bug.

When there's only 1 bundle allowed, the field is required and empty, and "reference existing" is disabled, the add form is always opened, which means that the Cancel button would do nothing in that case. So for that case the Cancel hiding will only be removed when the automatic opening of the add form is removed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.