Closed (fixed)
Project:
Commerce Core
Version:
8.x-2.x-dev
Component:
Product
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
20 Mar 2016 at 04:16 UTC
Updated:
13 May 2016 at 06:04 UTC
Jump to comment: Most recent
In Commerce 1.x products were shown with a product display node. My understanding is, that this is no longer necessary in Commerce 2.x
An anonymous user does not have access to view a Commerce Product. What is the Commerce 2.x way of displaying products?
Comments
Comment #2
agoradesign commentedThis is the 2.x way, only the permissions are not defined at the moment.
Comment #3
platinum1 commentedThank you. I appreciate the quick feedback!
Comment #4
platinum1 commentedWhat is the planing for creating permissions for Commerce Products?
Comment #5
bojanz commentedNext week or so. We're busy on checkout at the moment.
Comment #6
platinum1 commentedThank you Bojan. That would be very helpful.
Comment #7
agoradesign commentedI plan to work on theming the product page of my current project next week. I may post a patch here which includes the permissions.
Comment #8
bojanz commented@agoradesign
Permissions need to be done in the Entity API module, and then applied to every entity type. There's a pull request in the fago/entity repository already, but it hasn't been finished.
Comment #9
agoradesign commentedI've added a related issue, which fits to general topic of how to display the fields and attributes of variations within the product template
Comment #10
platinum1 commented@bojanz
Do you have an update on the Entity API module regarding the permissions?
Comment #11
agoradesign commented@platinum1
Here's a workaround for you. Implement this in a custom function, if you want to have general access to product entities. For a more fine grain, role-based approach, you'd need to define permissions of course:
Comment #12
bojanz commentedRetitling. Opened #2715273: Implement full permissions for every entity type to track the full fix.
Comment #14
bojanz commentedCommitted a combination of #11 and a variations fix.
Comment #15
platinum1 commentedCool. Temporary works for the project.
Thank you guys!
Comment #16
agoradesign commentedBtw when removing my custom code, I saw that I obviously added the same variation part in the meantime :D
thanks anyway for the fix :)