Extend / override Char Limit for plaintext fields

[sturmundbraem]

We use a lot of plaintext fields. It's great that we can keep the field types list short by just using a predefined field Type and then override the label and the handle:

Alas, there is one thing we would really appreciate to be able to extend as well "per Instance": the max chars ("Field limit")

[sturmundbraem]

We need the max chars to discipline our editors. else, you'll get those looong teasers, pitches and leads inevitably.

We've tried adding specialised fields with different max chars:

While this is +- feasible, the problem is that if you build a site in collaboration with the editors, you can't always say beforehand which text lengths they will need in the end. So I might say "The lead has max 500 chars". But when the editor asks for 100 more, I have to be able to adapt.

As far as I can see, I can't switch the field here, right?

So either you just forget about the max chars (and open the flood gates) or you end up in absolute specificity, creating a single field type for each field, which is a pity.

Hence the request for overriding/extending max chars for plaintext fields

[brandonkelly]

This was previously requested by #8688. However there are some technical challenges that have prevented us from implementing it.

[sturmundbraem]

Sorry for the double posting and thanks for the transparent feedback

[sturmundbraem]

@brandonkelly Am I right, it's not possible to change the basic fieldtype that has been used for a field without losing the content?

Example:

1. Use fieldtype plain500 for the lead field
2. Content arrives
3. More content arrives, editor requests more chars
4. Switch fieldtype for the lead field to plain500
   -> That won't work, right?

[brandonkelly]

Not currently, but you can add a new field to the layout, and then copy existing field values over to it using the resave/entries command.

php craft resave/entries --section=mySection \
  --set=myNewField --to=myNewField \
  --update-search-index

And once that’s done (on all environments), you can remove the old field from the field layout.

[sturmundbraem]

Got a workaround!!!

Using doublesecretagency/craft-cpjs and some custom nomenclature for the instructions field.

document.addEventListener('DOMContentLoaded', function() {
  // Select all instruction elements with IDs starting with "fields-" and ending with "-instructions"
  var instructionsEls = document.querySelectorAll('[id^="fields-"][id$="-instructions"]');

  instructionsEls.forEach(function(instrEl) {
    // Extract the fieldName from the id (e.g., "videoPlayText" from "fields-videoPlayText-instructions")
    var match = instrEl.id.match(/^fields-(.+)-instructions$/);
    if (!match) return;
    var fieldName = match[1];

    // Extract the numeric limit from the instructions text using the pattern [[max-chars-60]]
    var limitMatch = instrEl.textContent.match(/\[\[max-chars-(\d+)\]\]/);
    if (!limitMatch) return;
    var limit = parseInt(limitMatch[1], 10);

    // Replace the pattern with "Max {limit} Chars" in the instructions element
    instrEl.innerHTML = instrEl.innerHTML.replace(/\[\[max-chars-(\d+)\]\]/, 'Max: $1');

    // Find the associated input element by constructing the ID "fields-{fieldName}"
    var inputEl = document.getElementById('fields-' + fieldName);
    if (inputEl) {
      // Only apply if the element is an <input type="text"> or <textarea>
      var tagName = inputEl.tagName.toLowerCase();
      if ((tagName === 'input' && inputEl.getAttribute('type') === 'text') || tagName === 'textarea') {
        inputEl.setAttribute('maxlength', limit);
      }
    }
  });
});

Setting up the field:

Result:

[sturmundbraem]

(Don't ask who wrote the JS)

[brandonkelly]

Clever!