I am wondering why the product title field is required by Drupal Commerce. Neither do I understand why the product title field uses its own template functions and formatters for what is essentially a plan text field.

This is bothering me in my case because I am trying to use the EditableFields module to use an alternative "editable" formatter for the product title. I can also imagine that in a similar way, other contributed modules would be prevented from working their intended magic on the field in terms of custom widgets, formatters and so on. Heck, some products might not even need a title at all.

So my feature request is remove the product title field as a Commerce-specific field. I suggest that we just add a standard (deletable) text field to the default installation of the product type for UX reasons. Not a big job I expect....

Am I overlooking something? I'd love to hear your views.

[EDIT] Related issue here: #1416458: Title as an optional field (or completely ignored, if desired)? - I am being a little bolder....

Comments

rszrama’s picture

rszrama commented
Status: Active » Closed (won't fix)

heh, well, this certainly won't happen in Commerce 1.x (and I'm not sore about 2.x, though it could possibly be changed to a field). We depend on the product having a title in too many places, and for most stores it actually does make sense to have. It is a bummer that we don't have automatic Editablefields integration, but one thing you could do is simply hide the default Title field and use custom code or some sort of auto-title module to set the title of the entity to the contents of an additional textfield for now. This can at least give you the behavior you need with minimal overhead. We can put it on a list of things to consider for 2.x.

tommy kaneko’s picture

tommy kaneko commented

Yes, I can see that such a change can break a lot of things if implemented with 1.x, maybe even 2.x. I think it would still be a good idea to push for a change to a field in 2.x.

In 1.x, do you think it is still possible to use the standard widgets and formatters for a standard textfield? I wonder if this will break things too. Also, it probably wouldn't help in my situation anyway.

For now, I will use the workarounds as you suggest.

rszrama’s picture

rszrama commented

Hmm, yeah, I don't know that we can really put widgets on the textfield as an extra field instead of a "field" field. One thought that occurred to me was maybe we figure out a way to default the "Title" to the SKU, much like we do for the Order Number (defaults to the Order ID).

rszrama’s picture

rszrama commented
Issue summary: View changes

Added related issue