Is there something I’m missing in regards to controlling how an item’s options appear in the cart?

From what I can tell, there’s no way to just list whatever options might be available ... I instead have to specifically include tags for all potential item options?  And if this is the case, do I then have to do a conditional check for each one to include some surrounding markup?

i.e.

Would be great to have an item_options iterator, like:

Or something?

This is something I hadn’t thought of, but it makes total sense. The challenge is coming up with a clean solution. Let us think about this for a while and get back to you.

For now, yes, you’ll have to specifically enumerate each potential item option with conditionals, like in your code sample there.

I love that suggestion. It sounds so simple (it won’t be but I love it. Rob and I will talk in the morning of the realities of doing something like this. This particular issue has been something that I’ve considered time to time, but I think we’re in a position where we could deliver this, and I think most people will really want this feature.

Any update on this one guys?

We have it on our list, but no ETA. The next major item we have is site wide discounts. After that we’ll reevaluate, and see what’s highest on the list.

We discussed this previously, but came to the conclusion that it’s not a quick / easy change, so we have to hold off for now.

Ping. 

Discounts are done now. BUT we’re working on the EE 2.1 version of CartThrob.

That said, this issue has been personally bugging me for a LONG time. I’ll see if I have a few minutes tonight. I think it’d need, at a minimum a weblog_id parameter, or we could glean the item_options from the entry id as well. Thoughts?

Hey Chris—I know 2.1 compatibility is top priority, but thanks for taking a minute to think about this.

I think an entry_id parameter makes the most sense for a standalone tag, which could be useful, but thinking about this now, wouldn’t a tag pair within cart_items_info make more sense?. e.g.

Same goes for the {order_items} tag pair, for displaying on invoices, etc (though I can imagine a tag pair within a tag pair within a weblog:entries loop might be a nightmare).

Another quick ping here. I know you guys are busy. But I just went through a project where I had to write a plugin for two separate places (one in the cart using the session data, the other for grabbing and deserializing data from the Orders weblog) for this very purpose.

Any chance this is making it into the EE2 version?

It will be included in the EE2 version. And I might also include it in the current version…. because other than the lack of reorderable tax and shipping settings in the current version this is one of the things I’m most annoyed by myself.

I’d like to simplify item options / price modifiers and shipping as much as possible. We’ll be doing ongoing refinements in this area. Rob is off on paternity leave this week, so I’m totally swamped… but if I’m thinking about it, I’ll see about porting some code back to EE1 for this.