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.
Recent comments
Trying to push it to upstream 🤞 https://github.com/drush-ops/drush/pull/6621
Using Drush 8 with php 8
Wow, thank you!
Using Drush 8 with php 8
Hi folks, I went ahead and ported all drush 8.x stuff to PHP 8.3 and completely ripped out the legacy Symfony 2 internals. You can check out the exact details of what was done in the PR...
Using Drush 8 with php 8