Skip to content

[Issue] Product layout based on attribute_set #38790

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

Closed
m2-assistant bot opened this issue Jun 4, 2024 · 4 comments · Fixed by #36244
Closed

[Issue] Product layout based on attribute_set #38790

m2-assistant bot opened this issue Jun 4, 2024 · 4 comments · Fixed by #36244
Assignees
Labels
Area: Catalog Component: Catalog feature request Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Progress: PR in progress Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it

Comments

@m2-assistant
Copy link

m2-assistant bot commented Jun 4, 2024

This issue is automatically created based on existing pull request: #36244: Product layout based on attribute_set


Currently there is only the possibility to adjust the layout by SKU or by types of the product. In most productive cases, however, this is only partly practical. because it then only refers to many articles or one article. With the integration the layout can be used based on the attribute set similar to an article group, which is more needed in most cases. The display of the articles are controlled in the backend by attribute_set, so there should be a way to pass this to the frontend store as well.

https://developer.adobe.com/commerce/frontend-core/guide/layouts/product-layouts/

LAYOUT FILE DESCRIPTION
catalog_product_view.xml Common layout. Affects all product types
catalog_product_view_type_bundle.xml Layout from this file is applied to bundle product only
catalog_product_view_type_configurable.xml Layout from this file is applied to configurable product only
catalog_product_view_type_downloadable.xml Layout from this file is applied to downloadable product only
catalog_product_view_type_grouped.xml Layout from this file is applied to grouped product only
catalog_product_view_type_simple.xml Layout from this file is applied to simple product only
catalog_product_view_type_virtual.xml Layout from this file is applied to virtual product only
catalog_product_view_id_{id}.xml Layout from this file is applied to the specific product by Entity ID value. E.g. catalog_product_view_id_45.xml
catalog_product_view_attribute_set_{id}.xml Layout from this file is applied to the specific product attribute set by Entity ID value. E.g. catalog_product_view_attribute_set_45.xml
catalog_product_view_sku_{sku}.xml Layout from this file is applied to the specific product by SKU value. E.g. catalog_product_view_sku_24-WG080.xml

Example: catalog_product_view_attribute_set_15.xml
Controls the front-end display of all items that are within the Bags group.

@m2-assistant m2-assistant bot added the Priority: P2 A defect with this priority could have functionality issues which are not to expectations. label Jun 4, 2024
@engcom-November engcom-November self-assigned this Jun 7, 2024
Copy link
Author

m2-assistant bot commented Jun 7, 2024

Hi @engcom-November. 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-November engcom-November added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Jun 7, 2024
@engcom-November
Copy link
Contributor

engcom-November commented Jun 7, 2024

Hello @in-session,

Thank you for the report and collaboration!

Changing the layout of the products based on attribute set is a good feature to implement.
Hence marking this as a feature request.

@engcom-Hotel engcom-Hotel moved this to Pull Request in Progress in Feature Requests Backlog Aug 19, 2024
@engcom-Dash engcom-Dash added Component: Catalog Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Area: Catalog labels Jan 6, 2025
@github-jira-sync-bot
Copy link

✅ Jira issue https://jira.corp.adobe.com/browse/AC-13622 is successfully created for this GitHub issue.

Copy link
Author

m2-assistant bot commented Jan 6, 2025

✅ Confirmed by @engcom-Dash. Thank you for verifying the issue.
Issue Available: @engcom-Dash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Catalog Component: Catalog feature request Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: done Progress: PR in progress Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
Status: Pull Request in Progress
Development

Successfully merging a pull request may close this issue.

4 participants