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
You can edit images and load them back to the same folder with the same name and extension, this will not create a problem. Replace directly in the file system, without the use of CMS, for CMS...
Image manipulation on server?
I was under the impression you could not do that - don't know where I got that idea from... thought it had to do with the way Backdrop manages image files.
Image manipulation on server?
I think given the warning on the source site: At this time, if your new project can afford to require PHP 5.5+, which it should, please use PHP's native password_hash() /...
July 31, 2025