The configuration parameter "componentType" is a required for "advanced_pricing_button" component. #5645
Comments
|
I had to change the |
|
I am getting the same issue not sure what to change... Cane someone help please.
|
|
@malaiselvan did you added an attribute to the Advanced Pricing Group?, I also added the group from the admin panel, did you create the Advanced Pricing from the panel or directly on the database? FYI on my database the |
|
SQL: UPDATE Do not copy paste code! {PRICE} - is attribute group where exists all attributes, like price, special_price, group_price etc... That code help me solve problem after import from Magento 1.x - to Magento 2.x. After SQL code, run magento indexer:reindex in console, and cache:flush(not sure that last one needed) |
|
This fix (https://github.com/SwiftOtter/AdvancedPricingBug) may solve the problem for you. Per this issue thread (#5236), others suggested the code update as the solution. Give it a whirl and let me know. |
|
It's not fixed after install AdvancedPricingBug module. |
|
@sumanparihar The fix worked for me. Did you activate the module, deleted static assets, re-compiled the system, cleared the cache? Do you run developer or production mode? |
|
Hi @j1nx3d. |
veloraven
added
the
Issue: Ready for Work
|
fwiw my issue, not being able to edit certain products, is rooted in the use of a Migration_Default attribute set that i still have lingering around from a db importation made a really really long time ago. probably 1.9.2 -> 2.0.0 Only my products with attribute set of one of the migration ones are having the editting issue. This is not the first and surely wont be the last that this old migrated dataset has caused me issues with some new edition of Magento. It would be nice if you guys could include in a new release a script that would clean up this old and possibly improper migration, or at least keep in mind that some of us have been with you guys for a while, and we will still have artifacts from earlier upgrades.... As soon as I updated all my items with Migration_Default attribute set id to Default attribute set id, I can edit all products again. So if your issue is not being able to edit products on the back end this fixed it for me, although I do have to say my Migration_Default attribute set, doesnt contain anything that the Default doesnt contain, idk. I have tinkered with it for a few hours now to see what the difference is and i cant find the culprit just yet... |
|
Ok so I have honed down where my issue arises from again reminding that this is happening in my migration default attribute set id items, and that this prevents me from editting the product in the back end resulting in this output in the report log a:4:{i:0;s:98:"The configuration parameter "componentType" is a required for "advanced_pricing_button" component.";i:1;s:7067:"#0 /var/www/magento2/vendor/magento/framework/View/Element/UiComponentFactory.php(361): Magento\Framework\View\Element\UiComponentFactory->mergeMetadataItem(Array, Array, false) This is cured by having the product attribute tier_price in a sub group that can have any name for whatever attribute set that you are experiencing this issue with. at least this solves the issue for me, but have converted all my migration_default attribute id items to the normal default. |
magento-engcom-team
added
bug report
Issue: Format is not valid
|
@j1nx3d, thank you for your report. |
magento-engcom-team
added
2.2.x
Issue: Confirmed
|
Any updates on this one? |
|
Pretty sure this isn't a Magento issue per se as most people experiencing this problem are people who have updated and don't have the now required attribute of tier_price in their adv pricing group. There may be another attribute that you need to add into your attribute_set for whatever attribute_set_id is the one the products causing you issues are using... I posted this just up there "This is cured by having the product attribute tier_price in a sub group that can have any name for whatever attribute set that you are experiencing this issue with." |
1 similar comment
|
Pretty sure this isn't a Magento issue per se as most people experiencing this problem are people who have updated and don't have the now required attribute of tier_price in their adv pricing group. There may be another attribute that you need to add into your attribute_set for whatever attribute_set_id is the one the products causing you issues are using... I posted this just up there "This is cured by having the product attribute tier_price in a sub group that can have any name for whatever attribute set that you are experiencing this issue with." |
|
I am experiencing a similar issue, which I thought was related to this. When I try to create a bundle product on 2.1.9, magento throws an exception: Exception #0 (Magento\Framework\Exception\LocalizedException): The configuration parameter "componentType" is a required for "special_price" component. This happens when I click on create product, not when I save. I don't even get to see the product_form. So, do you think this is maybe another problem? |
|
It is the same general error, being that there is a value that is required
in the MySQL database. That value that is required to have a value is
specifically required by the special price group in attribute set. it's
entity (the missing value) is described by the attribute that is missing in
whatever attribute set you are using for the item that is failing like
this.
What you can do is go look in the default attribute set for what attributes
are under the "special price" subgroup, find the ones missing in your
attribute set for the failing item.
Or you can delete the special price subject group from the attribute set
for the item that is failing assuming you don't need it.
Chris
…On Feb 22, 2018 10:16 AM, "Jan Brinkmann" ***@***.***> wrote:
I am experiencing a similar issue, which I thought was related to this.
When I try to create a bundle product on 2.1.9, magento throws an exception:
Exception #0 (Magento\Framework\Exception\LocalizedException): The
configuration parameter "componentType" is a required for "special_price"
component.
So, do you think this is maybe another problem?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5645 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJ0VcqdVNxGUtJAy7SUGuripGr638Hmrks5tXZK5gaJpZM4JMsQh>
.
|
magento-engcom-team
removed
the
Event: distributed-cd
magento-engcom-team
removed
the
Reproduced on 2.3.x
|
Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily. Please feel free to comment or reopen according to the Issue reporting guidelines |
|
I experience the same issue on migrated database from 1.9.2.3 to 2.3.3. This issue should be fixed because a user can freely cause an integrity violation and have no feedback from the application as to why the error happens and that making changes will cause exceptions. This is an immature problem to happen in an evolved enterprise platform. IMO it is bad programming practice to have the backend depend on attributes existing in a specific group and allow the user to break the ability to view/update a product. At the very least, add a caught exception to explain to the user that the attributes cannot be loaded instead of displaying a generic error which doesn't have meaning to a user. |
|
You have an attribute that is not defined somewhere. If you read this
entire thread there is a how to to fix this issue.
…On Wed, Oct 23, 2019, 5:25 PM Kyle Waid ***@***.***> wrote:
I experience the same issue on migrated database from 1.9.2.3 to 2.3.3.
I have a lot of trouble with this kind of issue. The reason being because
the error is not clear in explaining the problem, and because in my opinion
the problem is stupid. An uncaught programming exception happens because
specific attributes are not a part of a specific attribute group. The
application freely allows you to move the attributes without any warning
that doing so will cause an error. It wastes my time. In my opinion this is
a poorly programmed function and still years later it is not fixed. I am
glad that I was able to find the bug report and resolve the issue myself,
however am not happy that this software app at this stage of development
has this kind of problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5645?email_source=notifications&email_token=ACORK4RX2JCJPZ4PAXS3EV3QQDFLXA5CNFSM4CJSYQQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECDCDSI#issuecomment-545661385>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACORK4V7JGVOJWZ23QYCBZLQQDFLXANCNFSM4CJSYQQQ>
.
|
If you see in my post, I did fix the issue myself and I no longer face the issue. The exact resolution for me was to ensure that all attributes that were in the default attribute set advanced pricing group were also in my custom attribute group. During migration the attribute set is Migrated_Pricing. I renamed it to Advanced Pricing. I verified that the attribute group code in the table others mentioned said advanced-pricing, then added special price, tier_price, etc to the group. After I saved I was able to save the product. |
|
My bad, I inherently did what I was accusing you of doing... Not reading.
This error has to do with migration, and you may or may not have migrated
that database from an earlier version of 1.9 or earlier as this is what I
did. I also am pretty sure I had used an external migrator at first, and
am pretty sure this caused the issue.
…On Wed, Oct 23, 2019, 5:31 PM Kyle Waid ***@***.***> wrote:
You have an attribute that is not defined somewhere. If you read this
entire thread there is a how to to fix this issue.
…
<#m_5972759734758175268_m_-6382041113184493955_m_1086082175875859333_m_-5562447832338273496_>
On Wed, Oct 23, 2019, 5:25 PM Kyle Waid *@*.***> wrote: I experience the
same issue on migrated database from 1.9.2.3 to 2.3.3. I have a lot of
trouble with this kind of issue. The reason being because the error is not
clear in explaining the problem, and because in my opinion the problem is
stupid. An uncaught programming exception happens because specific
attributes are not a part of a specific attribute group. The application
freely allows you to move the attributes without any warning that doing so
will cause an error. It wastes my time. In my opinion this is a poorly
programmed function and still years later it is not fixed. I am glad that I
was able to find the bug report and resolve the issue myself, however am
not happy that this software app at this stage of development has this kind
of problem. — You are receiving this because you commented. Reply to this
email directly, view it on GitHub <#5645
<#5645>?email_source=notifications&email_token=ACORK4RX2JCJPZ4PAXS3EV3QQDFLXA5CNFSM4CJSYQQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECDCDSI#issuecomment-545661385>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACORK4V7JGVOJWZ23QYCBZLQQDFLXANCNFSM4CJSYQQQ
.
If you see in my post, I did fix the issue myself and I no longer face the
issue. The exact resolution for me was to ensure that all attributes that
were in the default attribute set advanced pricing group were also in my
custom attribute group. During migration the attribute set is
Migrated_Pricing. I renamed it to Advanced Pricing. I verified that the
attribute group code in the table others mentioned said advanced-pricing,
then added special price, tier_price, etc to the group. After I saved I was
able to save the product.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5645?email_source=notifications&email_token=ACORK4UNMQPX6E5HLVM5MC3QQDGDJA5CNFSM4CJSYQQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECDCRQQ#issuecomment-545663170>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACORK4VJV5BD6P2OPW6D5FDQQDGDJANCNFSM4CJSYQQQ>
.
|
|
Might I also add that while learning the Magento table structure and it's
foreign keys and/or dependencies can be a chore, understanding the finer
points of it however, makes fixing issues like this one ezpz.
…On Wed, Oct 23, 2019, 5:35 PM Chris Clark ***@***.***> wrote:
My bad, I inherently did what I was accusing you of doing... Not reading.
This error has to do with migration, and you may or may not have migrated
that database from an earlier version of 1.9 or earlier as this is what I
did. I also am pretty sure I had used an external migrator at first, and
am pretty sure this caused the issue.
On Wed, Oct 23, 2019, 5:31 PM Kyle Waid ***@***.***> wrote:
> You have an attribute that is not defined somewhere. If you read this
> entire thread there is a how to to fix this issue.
> …
> <#m_7752724294676349965_m_5972759734758175268_m_-6382041113184493955_m_1086082175875859333_m_-5562447832338273496_>
> On Wed, Oct 23, 2019, 5:25 PM Kyle Waid *@*.***> wrote: I experience the
> same issue on migrated database from 1.9.2.3 to 2.3.3. I have a lot of
> trouble with this kind of issue. The reason being because the error is not
> clear in explaining the problem, and because in my opinion the problem is
> stupid. An uncaught programming exception happens because specific
> attributes are not a part of a specific attribute group. The application
> freely allows you to move the attributes without any warning that doing so
> will cause an error. It wastes my time. In my opinion this is a poorly
> programmed function and still years later it is not fixed. I am glad that I
> was able to find the bug report and resolve the issue myself, however am
> not happy that this software app at this stage of development has this kind
> of problem. — You are receiving this because you commented. Reply to this
> email directly, view it on GitHub <#5645
> <#5645>?email_source=notifications&email_token=ACORK4RX2JCJPZ4PAXS3EV3QQDFLXA5CNFSM4CJSYQQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECDCDSI#issuecomment-545661385>,
> or unsubscribe
> https://github.com/notifications/unsubscribe-auth/ACORK4V7JGVOJWZ23QYCBZLQQDFLXANCNFSM4CJSYQQQ
> .
>
> If you see in my post, I did fix the issue myself and I no longer face
> the issue. The exact resolution for me was to ensure that all attributes
> that were in the default attribute set advanced pricing group were also in
> my custom attribute group. During migration the attribute set is
> Migrated_Pricing. I renamed it to Advanced Pricing. I verified that the
> attribute group code in the table others mentioned said advanced-pricing,
> then added special price, tier_price, etc to the group. After I saved I was
> able to save the product.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#5645?email_source=notifications&email_token=ACORK4UNMQPX6E5HLVM5MC3QQDGDJA5CNFSM4CJSYQQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECDCRQQ#issuecomment-545663170>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ACORK4VJV5BD6P2OPW6D5FDQQDGDJANCNFSM4CJSYQQQ>
> .
>
|
[TSG][PHP7.4] MFTF Fixes for 2.4 (pr38) (2.4-develop-php74)
Steps to reproduce
Expected result
Actual result
Exception #0 (Magento\Framework\Exception\LocalizedException): The configuration parameter "componentType" is a required for "advanced_pricing_button" component.
WorkAround this problem
I think the problem is due to the missing Advanced Pricing group on the new Attribute set, I tried to only create the new Advanced Pricing group. but didn't work.
I have to add the default attributes on that group again (special_price, special_from_date, special_to_date, cost, tier_price, msrp, msrp_display_actual_price_type, price_view)
The text was updated successfully, but these errors were encountered: