The page for adjusting the SKU for a product based on its attributes is broadly called the "Adjustments" tab, which can be confusing to newer users; the title doesn't convey to the user that they should expect to find the settings for SKUs.
The attached patch fixes this broad use of terminology by renaming the tab to "SKU Adjustments".
As always, you will need to clear caches after applying the patch because it contains a menu item name change.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 825016_sku_adjustments.6.x-2.x-dev.patch | 4.74 KB | guypaddock |
| sku_adjustments.patch | 3.87 KB | guypaddock |
Comments
Comment #1
guypaddock commentedAttached is the same patch, re-rolled with the correct character encoding for 6.x-2.x-dev.
Comment #2
subcomandante commentedIn my opinion the adjustment tab naming is correct because it can be extended by other modules to "adjust" other things.
e.g. I use uc_dependent_attributes to take control over available options combinations.
Actually I'd like to see a "Price adjustment" also, not only SKU, because I could have some combination which change the price, for example:
Single -> Entry -> Primary : price_a
Single -> Entry -> Secondary : price_b
Single -> Top -> Primary : price_c (which is not linear combination of Entry, Top, Primary)
etc..
Comment #3
tr commentedI agree that the UI could be better, but I'm inclined to agree with @subcomandante.
Comment #4
fehin commentedWhile I understand @subcomandante point, I'm wondering if I change the name of the tabs (attributes, options, adjustments) with a hook and not in the core, will this affect other modules that may be extending them? Thanks.
Comment #5
longwaveChanging just the labels on the tabs using string overrides, locale or a custom module shouldn't affect core or contrib.
Back to 'won't fix' as this still won't be changed in Ubercart itself.