You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 19, 2024. It is now read-only.
## Step 2 Create an InstallData script {#CreateProductAttributeByUpgradeScript}
91
91
92
92
Next, we need to create the InstallData script.
93
93
Because adding an attribute technically adds records into several tables, such as `eav_attribute` and `catalog_eav_attribute,` this is data manipulation, not a schema change.
@@ -196,7 +196,7 @@ For now, we’ll just quickly go through most important ones:
196
196
***visible_on_front:** A flag that defines whether an attribute should be shown on the “More Information” tab on the frontend
197
197
***is_html_allowed_on_front:** Defines whether an attribute value may contain HTML
198
198
199
-
## Step 3: Add a source model
199
+
## Step 3: Add a source model {#AddSourceModel}
200
200
201
201
Next, we need to create the source model:
202
202
@@ -337,3 +337,54 @@ backend model has executed successfully, so now we’ll set it to Wool and save
337
337
338
338
Having saved the product, we’ll now move to the frontend.
339
339
It should be visible and in bold text.
340
+
341
+
## Product Attribute Option Creation
342
+
343
+
A product attribute of type multiselect or select will present selectable options to the user. These options may be added manually through the admin panel or by upgrade script. The script process is slightly different depending on whether the options are being added at the moment of attribute creation or whether the options are being added at a later time to an existing attribute.
344
+
345
+
### Add options to a new prouduct attribute {#AddOptionsAlongNewProductAttribute}
346
+
347
+
Basic instructions for creating a product attribute by setup or upgrade script can be found [above](#CreateProductAttributeByUpgradeScript). Before scripting the attribute creation, pick one of these two use cases for your options:
348
+
349
+
1. You want a set of options which cannot be modified by a user through the admin panel and which can only be changed through a future code push.
350
+
1. You want a set of options which can be modified, added or deleted through the admin panel.
351
+
352
+
For use case `1` (an 'immutable' set of options), follow the above instructions ["Add a source model"](#AddSourceModel). You will create a model that contains and dynamically returns the attribute's selectable options to the client.
353
+
354
+
For use case `2` (a 'mutable' set of options), see ["EAV and extension attributes"]({{ site.baseurl }}/guides/v2.4/extension-dev-guide/attributes.html). Make sure to declare 'Magento\Eav\Model\Entity\Attribute\Source\Table' as the value for the 'source' attribute option. This ensures that Magento will store options in the appropriate database table.
355
+
356
+
With `\Magento\Eav\Setup\EavSetup.php::addAttribute()` and `\Magento\Eav\Setup\EavSetup.php::addAttributeOptions()` you can add a series of options with the following array:
* To add options to an 'immutable' set of options, modify the custom source model with the additional options you wish to provide.
371
+
372
+
* Adding options to a 'mutable' set of options leverages the same `EavSetup` object as you use when creating an attribute with options, but requires an additional step because `EavSetup` needs to know to which attribute you want to assign new options.
0 commit comments