QuestionQ13

Content, CMS, and Storefront

A merchant requests a new category attribute that allows an additional mobile image to be uploaded for categories. The merchant uses Adobe Commerce Content Staging and Preview and wants to schedule and review modifications to this new mobile-image field.

A developer creates the attribute through a data patch and adds it to view/adminhtml/ui_component/category_form.xml. The attribute is shown for the category in the main form, but it is absent from the additional form when scheduled updates are created.

To modify this attribute while scheduling new category updates, what additional action should the Architect ask the developer to perform?

  • A The attribute must have its apply_to field set to “staging” in the data patch file.
  • B The attribute must also be added to view/adminhtml/ui_component/catalogstaging_category_update_form.xml.
  • C The attribute must have <item name="allow_staging" xsi:type="boolean">true</item> set in the category_form.xml file under the attributes ‘config’ section.
Explanation

Adobe Commerce Content Staging renders scheduled category changes through the CatalogStaging category-update UI component, separate from the standard category form. A custom category field must be declared in view/adminhtml/ui_component/catalogstaging_category_update_form.xml as well as the main category_form.xml to be available when creating scheduled category updates.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!