This is an expansion of the separating the uc_stock and uc_attribute permissions here:
http://drupal.org/node/279611

While this is the first step in expanding on the privileges for uc_stock and uc_attributes, I believe it needs to go a step further (especially if we want to use this for uc_marketplace).

Say you have two sellers in your store. You've set them up in a role with "Create Product" and "Edit Own Product" permissions only. You've also given them "Edit Product Attributes" and "Edit Product Options" .

Now as I understand it with this patch, these sellers will be able to add existing attributes and options to their products ...but if the store administrator hasn't included all the pre-existing attributes/options that a seller might need, he'll have to contact the site administrator to create them for him, so that he can add them to his product.

Otherwise, you'll have to give both sellers, "administer attributes" permission in which case, they can ruin each others options by editing/removing existing options or attributes.

Ideally attributes will be linked to the users account somehow and permissions will have to be able to distinguish between a user who can edit his own products, attributes and options and a user who can edit all products, attributes and options. User who can only Edit his own products, should be able to create/edit his own attribute sets and options sets, and add them to his products. Then only global administrators who can "edit any products", should be also able to edit them.

Globally created attributes and options, should be available to everyone. You should have an option to keep the attribute/option sets privately to only your user.

Comments

wqmeng’s picture

sub ...

rszrama’s picture

Status: Active » Postponed

Sounds like some good improvements to add needed granularity for marketplace type sites. Right now, though, this is out of scope for a 2.0 release, so I'm going to postpone it for consideration in the 3.0 development cycle.

ellastelter’s picture

Has there been any work on this feature request? I can see how it would be complicated, but it would also be SUPER helpful for the site I am building.

If not I am going to have to put together an awkward work around. Is there a way to make "linked" products?

longwave’s picture

What do you mean by "linked" products?

TR’s picture

Version: 6.x-2.x-dev » 8.x-4.x-dev
Issue summary: View changes

Not going to happen in the 6.x branch. New features will be developed for 8.x-4.x first at this point.