In 80% of use cases, truncating a field to a specified number of characters makes sense for teaser display modes. For those few use-cases where you actually want different content, what you really should be using is a different field.
Having these two concepts contained in a single field is confusing for users, and will become even more confusing when we introduce a Rich-text editor.
We may need to include some kind of an upgrade path for sites that were using the splitter before, but I think that could be done reasonably easily.
GitHub Issue #:
490
Recent comments
@yorkshirepudding, In the end I fixed it by deleting the config/active folder contents, copying the config/staging/ files into config/active, importing the database again and clearing the caches...
Importing the staged config throws an error: another field with the same name already exists
Thanks, I have to go out now, I will try later on and report back
Importing the staged config throws an error: another field with the same name already exists
Hi Francis. Yes, what config do you have in staging for it? You might have configs like: field.field.field_video_embed field.instance.node.page....
Importing the staged config throws an error: another field with the same name already exists