Docs

Release Notes for v0.26.0

Table of Contents

- [Bug Fixes](#bug-fixes)
- [Features](#features)
- [Upgrading from v0.25.0](#upgrading-from-v0250)
  - [The CMS object is no longer enabled by default](#the-cms-object-is-no-longer-enabled-by-default)

Bug Fixes

gatsby-tinacms-git: useGitForm#loadInitialValues does not run in production (a42d50c)
gatsby-tinacms-mdx: useMdxForm#loadInitialValues does not run in production (e0c2275)
next-tinacms-json: useJsonForm#loadInitialValues does not run when cms is disabled (9fbd8e8)
next-tinacms-markdown: useMarkdownForm#loadInitialValues does not run when cms is disabled (3292bf4)

Features

@tinacms/forms: useForm always runs loadInitialValues (a624087)
@tinacms/react-core: a new CMS is disabled by default (ef3ac08)
add focus ring to inline wysiwyg (2768afd)
tooltips for menubar options (bd06f11)

Upgrading from v0.25.0

The CMS object is no longer enabled by default

If you were creating the CMS like this:

const cms = new TinaCMS()

Then the CMS would have been enabled (i.e. the eidting UI would be available).

This is no longer the case so you will have to switch to:

const cms = new TinaCMS({ enabled: true })

View on GitHub

Last Edited: August 3, 2020