We're fixing issues as you feed them back to us. See the section, Known issues.
You can find a list of Fixed issues at the end of this page.
Common questions
How do I get Next Generation Authoring features?
You can benefit from the new 'look and feel' of the enhanced content authoring straight away just by switching it on. Learn about the out of the box features.
To get additional features, your developers will need to make changes to your content type schemas. Discover what's new.
Why is Next Generation Authoring already switched on?
Your organization has the option to turn on the new content authoring experience by default for all users. See Switching on for an organization.
How can the authoring experience be optimized?
Next Generation Authoring offers developers features, such as tab and grid layout, customizable components and content palettes, that they can use to optimize the authoring experience.
Can I switch between the new and previous authoring modes?
Yes, during the beta release you can switch Next Generation Authoring on and off. We encourage you to switch to our next generation of content authoring and take advantage of the benefits it offers. See Switching between authoring modes.
Why doesn’t drag and drop work all the time?
Sometimes if the items in your list span the full height of your screen then you will need to use the combination of click and mouse/trackpad to activate the drag behavior.
Will the new features work with the previous authoring experience?
Mostly, yes, Next Generation Authoring features can be used in the previous authoring experience. See the Limitations section.
Why am I being asked to save when I haven’t made a change?
One reason could be that your developers have changed the underlying content type schema. Simply save your content and continue.
Known issues
Why do tabs not indicate when there is an error?
Currently, individual tabs don’t notify you when there is an error unless you open the tabs. We are working on a solution that will bring errors in individual tabs to your attention.
Why isn't the card displaying for my content item?
In some instances, custom cards that act as thumbnails for content are not being displayed by Next Generation Authoring. This can relate to settings in your Content-Security-Policy
response header. Please check and update the frame-ancestors
to include https://content-form.extensions.content.amplience.net/
. For more information, see Content-Security-Policy: frame-ancestors.
Why can’t I create complex conditional scenarios?
We don't currently support all of the features specified in the JSON schema conditionals reference. We've provided examples of conditionals supported by Next Generation Authoring.
We may extend our support for conditionals in the future. To help us identify which features would be most beneficial, please send us your feedback. See How to send feedback.
Limitations
Next Generation Authoring is designed to be compatible with our previous authoring experience and with your existing schemas and content. However, in some instances it may not be possible for the previous authoring experience to fully adapt to next generation features:
The previous authoring experience is not shown correctly
This is probably because you're trying to open a content item that contains these Next Generation Authoring features:
Tab and grid layouts
Content types with next generation tab and grid layouts will re-adjust to a single list of fields when you switch them to the previous authoring mode.
Fixed issues
View the list of resolved issues
Issue | Description | Fixed date |
---|
Pasted text in multi-line fields is being cropped. | We've fixed this issue so pasting into multi line fields now works the same way as it does for single line fields. | 21st May 2025 |
Content links sometimes removed from a list when Replace is used. | This issue has now been fixed. | 21st May 2025 |
List does not indicate the minimum number of items it should have. | This issue has now been fixed. | 21st May 2025 |
Image name not changing when updated in Content Hub or Asset Tab. | This issue has now been fixed. | 14th May 2025 |
Authoring experience loses focus when entering a field value. | We've resolved the issue where when you start to enter values the authoring experience appears to redraw. | 14th May 2025 |
Additional notification of ‘should match else/then in schema’. | We've corrected the issue where sometimes, if a value doesn’t meet field validation, an extra notification is displayed, as well as the usual field validation message. | 14th May 2025 |
Required field names in error message not matching field titles. | This issue has now been fixed. | 16th April 2025 |
In some instances "Save" was unresponsive due to missing state validation, causing error messages not being displaying to users. | This issue has now been fixed. | 16th April 2025 |
Incorrectly saving content without values in required fields. | This issue has now been fixed. | 16th April 2025 |
Sliders incorrectly displaying the field-level error message "should be multiple of .1" when used in with multipleOf validation for .1 increments. | This issue has now been fixed. | 11th Feb 2025 |
Date field changing when I first save. | Corrected an issue with time zones, where the date fields displayed on the screen don’t match what’s actually being saved. | 5th Feb 2025 |
Authoring experience going blank when a conditional field is used. | We've resolved the issue where unselecting a populated value in a conditional statement caused the screen to stop rendering fields. | 28th Jan 2025 |
Certain default values prevent users from adding more than one item to list arrays. | We've fixed an issue caused when a default empty object is added to a content type schema. | 22nd Jan 2025 |
White screen displayed instead of the new authoring experience | Corrected issue with drop down lists with labels causing the new experience to not render if a value in the list is set to 0. | 22nd Jan 2025 |
Authoring experience slow with long forms. | We've fixed issues with layers of nested content that caused this issue. | 14th Jan 2025 |
Screen goes white when moving an item in the content palette | This issue has now been fixed. | 4th Nov 2024 |
Form displaying a blank white screen. | Updated Next Generation Authoring to correctly handle items that caused this issue. | 29th Oct 2024 |
Notification of missing “_meta” on required fields | We have resolved the issue where in some cases there was a notification that the "_meta" property is required on fields. | 8th Oct 2024 |
Newly created nested content items are not recognized, so parent content items cannot be saved. | Updated so that Next Generation Authoring allows the parent item of newly created nested content items to be saved. | 7th Oct 2024 |
Schemas containing conditionals being displayed as a blank screen in the content form. | This issue has now been fixed and we've updated our conditionals schema example. | 2nd Oct 2024 |
Images not showing in the default text editor | Now when you paste an image link into the default markdown editor, the image will display in the Edit tab. | 2nd Oct 2024 |
System slow when moving items around in a list | Issues that caused the system to be slower than expected when items were moved within complex lists are now resolved. | 23rd Sept 2024 |
Multi select images, video and content | Next Generation Authoring now supports adding multiple assets or linked content items to a list. | 9th Sept 2024 |
Earlier versions of the Safari browser | Next Generation Authoring compatibility issues that prevented you from saving content with Safari browser versions of 16.4 or older, are now fixed. | 4th Sept 2024 |
Tables in default markdown editor not retaining table formatting | Updated to enable the correct parsing of markdown tables to prevent them being corrupted when saved back using new form. | 4th Sept 2024 |
Hierarchy node inheriting data | Corrected so that creating a new hierarchy node creates an empty content item with no data inherited from the parent. | 4th Sept 2024 |
Related pages
Out of the box features
Optimize your authoring experience