Flamelink changelog
Flamelink changelog

Stay up to date with new changes!





What's new widget

We've added an in-app changelog so that you're always up to date with all the updates, improvements and fixes that we make.

Even though we work on Flamelink all the time, sometimes it may seem that not much is happening. This changelog is here to improve the communication between you and us.

You'll receive an update when we change something in the widget, or if needed all things we've changed is available on our public changelog page.

Nested field groups

Previously, you were limited to 4 levels of nested field groups. We've extended this to 8 levels for both Cloud Firestore and the Firebase Realtime Database. Firestore has a limitation of 20 levels of any nested objects or arrays, and this roughly translates to 8 levels of schema fields within Flamelink.

Disclaimer: having extremely nested fields is not recommended because it will be hard for content editors to manage content in these structures. In the future, we'll improve the UI situation for nested components.

Downgrade reason

We want to know you, our users, better. As part of this effort, we’ve introduced a quick multiple-choice selector to the project downgrade page. Instead of a lengthy questionnaire, we only ask that you select one of the predefined options for why you are downgrading.

Profile Menu

The profile menu in the top right of the app has had a facelift. No longer will the menu fly open when you hover over it by mistake. To open your profile menu, click to toggle it open and closed. As a bonus, we improved the keyboard accessibility for all the header icons, including this menu.

Minor fixes and improvements

  • Column headers for mobile tables weren’t translated; now they are.
  • The source view editor for the WYSIWYG field did not persist the changes after “save”, but it is behaving now.
  • Location field error was cut short
  • The animation for content cards have been improved

Geeky things

We’re already code-splitting our bundles to improved loading performance in the app, but there’s always more that can be done. In this release, we’ve further split out heavier packages that you might not be using. If you’re not using it, why should you download it, right?