Comments

heddn created an issue. See original summary.

heddn’s picture

Title: Release Commerce 2.0-rc2 » Release Commerce 2.0-rc3
bojanz’s picture

Issue summary: View changes
neograph734’s picture

Forgive me for being pushy, but I would really like to propose #2890081: Add translation context for order/promotion/store once more.

Adding this asap would give translators some time to make sure 'order' is actually translated to order in a shopping context and not to order in a sorting context. It would make sure that commerce is released with some sensible translations.

megachriz’s picture

+1 for having #2890081: Add translation context for order/promotion/store in before the final 8.x-2.0 release of Commerce. In Dutch 'Order' is translated in a sorting context.

heddn’s picture

Status: Active » Fixed

2.0 was released. This can be fixed now.

bojanz’s picture

We had a tight deadline. It is not too late for any issue to land after 2.0.

The three issues that were worked on leading up to the release but didn't land are:
#2499645: Start using the entity query access API on orders, products and stores
#2844920: Allow customer profiles to be reused
#2805549: Expand the "Calculated price" formatter with the ability to show prices with promotions/taxes/fees
They are our immediate focus in the upcoming days.

One important issue that did land, which is locking related, is #2906563: Provide a way to explicitly lock the order

agoradesign’s picture

When I look at the "Issues of interest" in the issue summary, I'd also vote for #2876977: Taxes are calculated on non-discounted unit prices because that sounds like a serious bug/problem, meaning that you actually can't use taxes + discounts atm without custom intervention

bojanz’s picture

@agoradesign
It is serious, but I haven't worked on it yet. The three issues above have been singled out cause I've already spent time on them.

Status: Fixed » Closed (fixed)

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