Content tokens are not usable in prefix and suffix

Created on 6 July 2016, over 8 years ago
Updated 1 July 2024, 6 months ago

When using tokens like [node:nid] in the prefix or suffix fields of a view mode controlled by Display Suite, it does not replace the tokens. There is a "Browse available tokens" selector link in the 'Expert' field template interface, suggesting that you should be able to use tokens. Tokens can be used in the custom DS fields, so there's workarounds available, but just wanted to know if this was by design or a bug.

πŸ› Bug report
Status

Needs work

Version

3.0

Component

User interface

Created by

πŸ‡ΊπŸ‡ΈUnited States chrisshattuck

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡§πŸ‡ͺBelgium swentel

    Weirdly enough, while checking the queue and testing tokens in suffix and prefix, they already seem to work. There's a problem with multilingual content though, so will double check that.

    Note: the dev branch now has an option to make prefix and suffix textareas, so that at least has been solved.

  • πŸ‡§πŸ‡ͺBelgium swentel

    Moving to bug to make the fixes that are needed. Needs tests a volonte.

  • πŸ‡§πŸ‡ͺBelgium swentel

    Added related issue that added prefix/suffix support initially

  • First commit to issue fork.
  • Pipeline finished with Failed
    9 months ago
    Total: 330s
    #126615
  • Pipeline finished with Success
    9 months ago
    Total: 329s
    #126623
  • Pipeline finished with Success
    9 months ago
    Total: 363s
    #126641
  • πŸ‡ΊπŸ‡ΈUnited States en-cc-org

    This patch has been essential for us, thank you. Are there remaining obstacles (test failures?) to getting this into a ds release? Thanks again.

  • πŸ‡§πŸ‡ͺBelgium swentel

    I'll have a look this week! I'm going to add an option at /admin/structure/ds/settings that allows you to enable this option so that sites who upgrade don't have undesired consequences, even though the impact is probably minimal anyway, but you never know :)

Production build 0.71.5 2024