Skip to content

Product and Category Attributes

Why limit the visual editor to pages and blocks? Hyvä CMS can manage compatible product and category attributes, such as descriptions, with the very same Liveview Editor. Merchants get component-based catalog content, and developers keep the rendered output structured and theme-controlled.

This feature is provided by the Hyva_CmsMagentoAttributes module.

Available since Hyvä CMS 1.2.0

Managing product and category attributes with Hyvä CMS was introduced in 1.2.0.

What Product and Category Attributes Do

Magento product and category attributes normally store HTML in native EAV fields. With Hyvä CMS attributes, the native attribute remains in place, but Hyvä CMS can render published CMS content for that attribute on the storefront.

Common examples:

  • Product description
  • Product short description
  • Category description
  • Custom rich text catalog attributes

Enabling Product and Category Attribute Support

Before Hyvä CMS can manage a product or category attribute, two things need to be true:

  1. Attribute support must be enabled in configuration.
  2. The attribute must be compatible with Hyvä CMS.

Product and category attribute support is enabled by default.

Admin path:

Stores > Configuration > Hyvä Commerce > Hyvä CMS > Attributes

Configuration options:

  • Enable Product Attributes
  • Enable Category Attributes

Compatible attributes are typically textarea or rich text attributes intended for page content. The default rules are:

  • Product attributes: textarea attributes with Page Builder enabled.
  • Category attributes: textarea attributes with Page Builder or WYSIWYG support.

If an attribute does not appear in the Hyvä CMS panel, it is not considered compatible by the installed rules.

Managing Attribute Content (Merchant Workflow)

To manage product or category attribute content with Hyvä CMS, follow this workflow:

  1. Open a product or category in the Magento admin.
  2. Find the Hyvä CMS panel on the edit page.
  3. Select the compatible attributes you want Hyvä CMS to manage.
  4. Save the product or category.
  5. Open the Liveview Editor for the selected attribute.
  6. Build the attribute content with components.
  7. Save drafts while working.
  8. Publish when the content should go live.

Publishing is what makes the content visible on the storefront. A saved draft does not replace the live attribute output.

Disabling Hyvä CMS for an attribute gives output control back to the native Magento attribute field. The Hyvä CMS draft data is kept, so it is available again if you re-enable the attribute later.

Store View Scope for Attribute Content

The All Store Views scope is the default content for a product or category attribute. Store-specific scopes can either use that default or override it with their own Hyvä CMS content.

On a specific store view:

  • Leave Use default value enabled to inherit the default Hyvä CMS content.
  • Disable Use default value to edit that store view independently.

Use store-view overrides when the content structure or content itself needs to differ by store. Use Translations when the structure should stay the same and only translatable field values need localized content.

Attribute Content Version History

Product and category attribute content uses the normal Hyvä CMS version workflow. Published versions can be reviewed, restored, named, and pinned from the editor's version history panel.

Migrating Existing Page Builder Attribute Content

If a product or category attribute already contains Page Builder or WYSIWYG content, use the migration tools as a starting point before replacing the native output.

Migration can convert existing content into Hyvä CMS components, but migrated content should still be reviewed before publishing.

See Page Builder Migration.

Scheduling Attribute Content

Product and category attribute content can be scheduled when the attribute feature and scheduling module are enabled. Scheduled attribute publications update the Hyvä CMS content for the target product or category attribute.

Unlike CMS pages and blocks, product and category attributes do not currently expose extra scheduled entity settings such as URL key or title.

See Content Scheduling.

Exporting and Importing Attribute Content

Product and category attribute content can be exported and imported through the Import/Export functionality. The target product or category must already exist in the destination environment, since the transfer moves the Hyvä CMS content but does not create products, categories, or EAV attributes. For how content is matched between environments, see Product and Category Attribute Transfers.

Troubleshooting Product and Category Attributes

An Attribute is Missing from the Hyvä CMS Panel

Problem: A product or category attribute does not appear in the Hyvä CMS panel's attribute list.

Cause: Only compatible attributes appear. By default, these are rich text or textarea-style attributes that are suitable for CMS content.

Solution: A developer can extend the compatibility rules if a custom attribute should be available.

The Storefront Still Shows the Old Attribute Content

Problem: Edited attribute content does not show up on the storefront.

Solution: Make sure the Hyvä CMS content is published and that you are checking the correct store view. A saved draft does not replace the live output.

A Store View Shows the Wrong Attribute Content

Problem: A specific store view shows different content than expected.

Solution: Check whether Use default value is enabled for that store view. If enabled, the store view inherits the default (All Store Views) content.

Disabling the Attribute Made the CMS Content Disappear

Problem: After disabling Hyvä CMS for an attribute, the storefront no longer shows the CMS content.

Cause: That is expected. Disabling hands output back to the native Magento attribute field.

Solution: The Hyvä CMS content is retained, so re-enabling the attribute brings it back.

For Developers

This feature is provided by the Hyva_CmsMagentoAttributes module. For module architecture, the recommended AttributeContent ViewModel rendering pattern, compatibility rules, storage, REST endpoints, and adding attribute editing to a custom entity, see Product And Category Attribute Content Development.