Fixed setting of source_model when adding new attribute and for multiselect. #1293
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description (*)
This PR addresses 2 issues.
Custom
source_model
When adding a new attribute in which the input type is select, the source model is always set to
eav/entity_attribute_source_table
irregardless ifsource_model
has a value or not.Partially fix issue #1096
This PR will set
source_model
when the attribute model is saved, but it cannot do anything for attributes which were updated directly in the database.Related Pull Requests
Fixed Issues (if relevant)
source_model
toeav/entity_attribute_source_table
if it's empty.Manual testing scenarios (*)
To replicate custom
source_model
The output is
eav/entity_attribute_source_table
but we expectcustomer/entity_address_attribute_source_country
.Partially fix issue #1096
$values
is now;Questions or comments
Contribution checklist (*)