Skip to content

Make Custom Layout Update file selectable generally available in all categories, products and cms pages.  #26901

@gcampedelli

Description

@gcampedelli

Description (*)

Currently in version 2.3.4 Custom Layout Update has been removed to improve security which is great. But to add an update you have to create a xml file in relevant theme directory Magento_Cms, Magento_Catalog using this termination:

catalog_category_view_selectable_<Category ID>_<Layout Update Name>.xml
catalog_product_view_selectable_<Product SKU>_<Layout Update Name>.xml
cms_page_view_selectable_<CMS Page Identifier>_<Layout Update Name>.xml

a) I tried this feature in using this termination "cms_page_view_selectable_mylandingpage_custom.xml"

b) It would be nice if we declare a file with custom layout update and it is generally available to be selected in all pages, categories and products.

Expected behavior (*)

a) Update Dev Docs to make it clear in which folder files have to be saved. => Magento_Cms for pages and Magento_Catalog for categories and products.
b) Have custom layout updates generally available for all pages, categories and products, so user can select and update layout without creating many files with same code over and over. For example:

catalog_category_view_selectable_<All Categories>_<Layout Update Name 1>.xml
catalog_category_view_selectable_<All Categories>_<Layout Update Name 2>.xml
cms_page_view_selectable_<All CMS Pages>_<Layout Update Name 1>.xml
cms_page_view_selectable_<All CMS Pages>_<Layout Update Name 2>.xml

and keep the current feature which is also great

Benefits

=> I think it would improve usability. Users can have a generally available custom layout update and specific available custom layout updates

Additional information

It would save time if user wants only to repeat an already made custom layout update.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue: ready for confirmationPriority: P2A defect with this priority could have functionality issues which are not to expectations.Progress: ready for groomingReported on 2.3.4Indicates original Magento version for the Issue report.Severity: S2Major restrictions or short-term circumventions are required until a fix is available.feature request

    Type

    No type

    Projects

    Status

    Ready for Grooming

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions