Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding a simple select in product attribute for dropdown type won't open options #38708

Closed
1 of 5 tasks
marmureanuweb opened this issue May 8, 2024 · 8 comments
Closed
1 of 5 tasks
Assignees
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@marmureanuweb
Copy link

marmureanuweb commented May 8, 2024

Summary

I'm trying to extend the product attribute option with a simple select element.
When trying to open it, it won't open due to an unknown reason.
I've tried removing the classes and adding "select","admin__control-select" but no luck. I've tried moving the select from the top of the row, but you will see the same exact issue.
SCR-20240508-ofbd

Examples

The file where I'm trying to add the select "vendor/magento/module-catalog/view/adminhtml/templates/catalog/product/attribute/options.phtml" > in the "<script id="row-template" type="text/x-magento-template">" in any of the <td> cells.
The element I'm trying to add <select name="test" class="select admin__control-select" > <option value="enable" selected="selected">enable</option> <option value="disable">disable</option> </select>

Proposed solution

No response

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@marmureanuweb marmureanuweb added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label May 8, 2024
Copy link

m2-assistant bot commented May 8, 2024

Hi @marmureanuweb. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@m2-community-project m2-community-project bot added this to Ready for Confirmation in Issue Confirmation and Triage Board May 8, 2024
@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label May 8, 2024
@marmureanuweb
Copy link
Author

@magento give me 2.4-develop instance

Copy link

Hi @marmureanuweb. Thank you for your request. I'm working on Magento instance for you.

Copy link

Hi @marmureanuweb, here is your Magento Instance: https://1cda3a7f8f8f9688624ed79a48e49f16.instances-prod.magento-community.engineering
Admin access: https://1cda3a7f8f8f9688624ed79a48e49f16.instances-prod.magento-community.engineering/admin_a400
Login: a6163ccc
Password: 7c410074e00e

@marmureanuweb
Copy link
Author

The element that I'm trying to add

                    <select name="test" class="select admin__control-select">
                        <option value="1">enable</option>
                        <option value="2">disable</option>
                    </select>

@engcom-Hotel engcom-Hotel self-assigned this May 9, 2024
Copy link

m2-assistant bot commented May 9, 2024

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
  • 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
  • 4. Verify that the issue is reproducible on 2.4-develop branch
    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
  • 5. Add label Issue: Confirmed once verification is complete.
  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Hotel
Copy link
Contributor

Hello @marmureanuweb,

Thanks for the report and collaboration!

Rather than modifying anything within the vendor folder, I recommend creating a custom dropdown field for an existing form in the Magento 2 Admin Panel by following these steps:

  1. Create a custom module.
  2. Use Magento UI Components to define the dropdown field and its behavior.

And also it doesn't seem a Magento core bug hence I suggest you refer to the Magento Stackexchange.

Thanks

@engcom-Hotel engcom-Hotel added Issue: needs update Additional information is require, waiting for response and removed Issue: ready for confirmation labels May 9, 2024
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board May 9, 2024
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board May 9, 2024
@engcom-Hotel
Copy link
Contributor

Dear @marmureanuweb,

We've observed that there haven't been any updates on this issue for quite some time. Therefore, we're assuming it's been resolved and will be closing it. Feel free to open a new ticket or reopen this one if you require further assistance.

Regards

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue: needs update Additional information is require, waiting for response Reported on 2.4.x Indicates original Magento version for the Issue report. Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
None yet
Development

No branches or pull requests

3 participants