Skip to main content

7 releases tagged with "cms"

View All Tags

Β· 2 min read

The isSingleton property is now available for merchants to create a single page of a content type in the Headless CMS. This property prevents the creation of multiple pages of the same content type, ensuring that any updates made to the content type layout are consistent across all requests.


What has changed?​

Previously, when creating or editing a content type without the isSingleton property, the content type page could be duplicated in multiple versions. This could cause issues when trying to update the correct version or result in multiple content types with the same name but different content, leading to confusion during content management.

With the isSingleton property, you can keep consistency across the content types in your store by preventing the creation of multiple pages with the same content type. This ensures that any updates to the page layout are reflected in all requests, streamlining your content management process.

Why are we making this change?​

The change enables consistency in the content of a page. The isSingleton property prevents the creation of multiple pages of the same content type and ensures updates to the page layout are reflected in all requests.

What needs to be done?​

For more information, please refer to the Using isSingleton property in a content type documentation.

Β· 2 min read

The onlySettings property is now available for merchants to create content types intended for settings only. ​​This option is particularly useful for content types that do not require storefront content, like an SEO page.

Image 1Image 2
Image 1 - Content type with onlySettings and with one tab for settings: SEO.Image 2 - Content type without onlySettings and with two tabs: Sections and SEO.

This property ensures that the content type page displays only the available settings without the Sections tab. Follow the steps below to use the onlySettings property for your desired content type.

What has changed?​

Previously, when creating or editing a settings-only content type, two tabs were displayed: one for sections and another for page settings. However, for some content types like SEO pages, which do not have storefront content, the Sections tab was not relevant.

Now, the onlySettings property allows the creation of content types meant for settings only. This change improves content management and simplifies interface navigation for merchants by displaying only one settings tab on the page.

Why are we making this change?​

The change enables the creation of setting-only content types that do not require storefront content, and simplifies interface navigation by displaying only one tab for the page configuration.

What needs to be done?​

To add the property to your store, please follow the instructions in Using onlySettings property in a content type.

Β· 2 min read

The Releases module allows you to manage and publish groups of connected changes called releases. The Calendar, a view of Releases, has been improved with the Monthly, Weekly, and Daily Views of your planned releases, allowing you to manage them more easily and effectively.

What has changed?​

Before, you had to manage releases in a searchable list. You could sort and filter releases, but it was difficult to visualize them, making it hard to keep track of your releases, their publication date, and how they related to each other.

Now, the Calendar page offers new ways to keep track of your releases. You can choose the Monthly, Weekly and the Daily View to better visualize and manage your releases.


Why did we make these changes?​

Better visualization of your releases enables you to have more control over them. These changes aim to enhance your experience and make management more simple and efficient.

Also, visualizing how releases relate to each other in a timeline can help you develop more precise communication plans because you have a clear vision of it and how your releases overlap, for example.

What needs to be done?​

No action is needed. The change will be automatically implemented in all stores developed using FastStore. Currently, Releases is available only for stores using FastStore.

For more information, see the documentation in Help Center:

Β· 2 min read

We are pleased to announce the release of Media Admin, a media gallery manager designed to help you efficiently manage your digital assets. With Media Admin, you can upload and organize your media files, whether they are PNG, JPG, GIF, SVG, or WEBP.

You can also integrate Media Admin into Site Editor and Headless CMS so users can access and manage their media files from within these platforms. For more information, refer to Using the Media Gallery as a CMS widget.


Uploading files​

Use the Media Admin to upload various media types, including PNG, JPG, GIF, SVG, and WEBP files. Check in the following how to upload and cancel an upload in progress.

  • Uploading a file

Uploading a file

  • Canceling an upload

Canceling an upload

Visualizing files​

Media Admin has two visualization modes - grid and list view. You can switch between these views to better locate and preview media files by clicking the list or grid icon in the top right.

The grid view displays a thumbnail preview of each file, while the list view shows the files in a detailed list.

Grid viewList view
Grid viewList view

Searching and filtering files​

Media Admin allows you to filter files by the newest, oldest, and name (in ascending or descending order). You can also search for specific file names using the search bar.

Using filters

Managing files​

You can use Media Admin to preview your digital assets, download them to your local device, delete them if they're no longer needed, or copy their URLs to use them elsewhere.

Managing files

Media gallery can be used as a widget in Site Editor and Headless CMS. All management actions are accessible within the widget, which is displayed in a modal. Check the video below to see the Media widget being used in each CMS solution.

  • Headless CMSHeadless CMS
  • Site EditorSite Editor

Note that the Media Admin app is associated with the VTEX account, meaning that both the Site Editor and Headless CMS will have access to the same gallery of media files.

Another important point to keep in mind is that if you delete a file from the media gallery that is being used in a section of the document, it will still be displayed in the section.

Β· One min read

The Base Store (Next.js) starter now supports instant VTEX Headless CMS previews.

Use the Preview option while writing a draft on VTEX Headless CMS to preview content changes immediately and whenever you want.

CMS Preview

What needs to be done?​

These changes are available in Base Store (Next.js) version 22.38.3 or greater. If you have already started a FastStore project with the Base Store (Next.js) starter, remember to keep it up to date with its latest version.

Also, notice that __next_preview_data cookies are set on the browser whenever you generate a CMS preview. Hence, after using the VTEX Headless CMS, make sure to clear the cookies from your browser so you can see your production website once again.

Clear cookies

Β· One min read

We’ve recently launched VTEX Headless CMS 1.x. For this new version to properly work, the Releases app must be installed and configured on the VTEX account.

What has changed?​

Besides notable new features, such as the non-blocking Publishing Flow, this update makes the VTEX Headless CMS strictly dependent on the Releases app.

Why did we make these changes?​

Gradually, Releases should become the single place in the VTEX platform to look into any changes that might affect published stores. VTEX Headless CMS moves in sync with this roadmap by requiring Releases integration in its latest version. This both reduces the complexity of our Publishing Flow implementation, facilitating debugging and improving stability, and also makes sure we’re future-ready with how the VTEX platform is moving.

What needs to be done?​

Developers must upgrade to VTEX Headless CMS 1.x and configure the Releases app as described in this guide.

Β· 2 min read

Following the next successful push to your store's repository default branch, the VTEX Headless CMS preview available at https://gatsby-preview-vtex-sites--<your-account-here> will require users to authenticate to VTEX.

In order to access the preview, users will need to have access to the domain of that specific account. This can be done either through the build environment variable GATSBY_STORE_ID in the vtex.env file, or the api.storeId entry exported by the store.config.js configuration file.

What has changed?​

Previously, CMS previews were published to public URLs by default. Now, they are private by default, requiring authentication to VTEX.

Why did we make these changes?​

CMS previews may contain sales promotions and product launches that are not yet available to the general public. This change aims to prevent unauthorized access to such content while also making the platform more secure.

What needs to be done?​

Every CMS preview is now private by default. However, to be able to log in and view the private previews, you must install the vtex.faststore-auth app in your account. To do this, run the following command:

vtex install vtex.faststore-auth

If, for any reason, you need your CMS previews to be accessed by the public or third-party solutions, you may disable authentication by adding USE_CMS_PREVIEW_AUTH=false to your repository's vtex.env file.