In order for a user to see results in the Orders view (admin/commerce/orders) they must have both of these permissions: "View any Billing information customer profile" (under Customer) and "View own orders of any type" (under Order). In version 1.8 they only needed the "View own orders of any type" permission.

If "View any Billing information customer profile" is not assigned, the user can see the Orders view, but they get the "No orders have been created yet. Create an order" message. (They can access an order's details (admin/commerce/orders/1) if they could figure out the path, which I think they are supposed to see.)

Looks like the View is doing what it is supposed to do, but Commerce's permissions stop the fields from being seen. I can't quite figure out what changed from 1.9 to 1.9. Is this a bug?

Comments

rszrama’s picture

rszrama CreditAttribution: rszrama commented
Category: Bug report » Support request
Status: Active » Fixed

This is working as designed; in fact it's an artifact of the previous method we used to determine access to fields via relationships. It was basing access on the first table in a View's list as opposed to the table you were joining to, which in the case of Commerce was inconsequential (order access governs access to related entities) but is now necessarily explicit. Grant the relevant customer profile related permissions or just disable SQL rewriting if you know you won't need it for the View.

cknoebel’s picture

cknoebel CreditAttribution: cknoebel commented

OK, thanks for the clarification.

Status: Fixed » Closed (fixed)

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