search

backdrop / backdrop-issues

Issue tracker for Backdrop core.
145 stars 40 forks source link

[UX] Views: Fix the replacement patterns weirdness #3696

Open klonos opened 5 years ago

klonos commented 5 years ago

I am starting this as a question, with the intention to make it a task...

Here is the help text that we have for the "Replacement patterns fieldset":

The following tokens are available for this field. Note that due to rendering order, you cannot use fields that come after this field; if you need a field not listed here, rearrange your fields. If you would like to have the characters '[' and ']' please use the html entity codes '%5B' or '%5D' or they will get replaced with empty space.

  1. Can we make these work like the token browser, where clicking a token gets it added to the text field?

  2. I would like to find out more about the due to rendering order, you cannot use fields that come after this field bit. Is this a "hard" technical limitation, or are we imposing something that is develop-y to the end users? Can we "fix" it somehow? Is there a way to make all tokens available, independently of the order of the fields?

  3. Why do we "force" the user to use HTML codes? Could this be a pre-CKEditor-in-core limitation? Can we perhaps introduce some sort of "internal", stripped-down version of a text format, which has some custom toolbar buttons for these things?

olafgrabienski commented 5 years ago

If you would like to have the characters '[' and ']' please use the html entity codes (...)

Why do we "force" the user to use HTML codes? Could this be a pre-CKEditor-in-core limitation?

AFAIK, it's not a text format issue. Square brackets are a special thing here. You can't use them directly in your content because they're part of the replacements patterns syntax, as in [title] or [type].