Using the link field from the contrib module, you can add a static "anchor text" and "link title", so that the user that fills in the field must enter only the URL. In my websites, I use very very much this feature. Unfortunately, it went lost moving link to core.

And, of course, it would be nice if these static texts could have support for tokens...

Example use-cases:

  • A website that needs to store the link of an IOS or Mac OSX application in the App Store would need this feature to assign the "See [appname] in the App Store" (where [appname] is a token) to the anchor text of a link field without having the risk of publishers changing the exposed default value;
  • You might want to set the anchor text of a link to the value of another field of your content type, but for some reason you need the value either as a field value and the anchor text;

In these two use-cases, you would need a static "link title" too if you want to enhance these links' accessibility.

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented

Can you clarify the use-case(s) for a static link title? (ideally in the issue summary)

falcon03’s picture

falcon03 commented

@sun: done! :-) I hope this is clearer now!

swentel’s picture

swentel commented
Component: field system » link.module
swentel’s picture

swentel commented
Issue summary: View changes

Adding use cases

mac_weber’s picture

mac_weber commented
Issue summary: View changes
Status: Active » Postponed

Postponing feature requests as of the allowed beta changes https://www.drupal.org/contribute/core/beta-changes

mgifford’s picture

mgifford
he/him
Primary language English
commented
Status: Postponed » Active

Drupal 8-beta 1 has been released.

mac_weber’s picture

mac_weber commented
Version: 8.0.x-dev » 8.1.x-dev
Status: Active » Postponed

Drupal 8-beta 1 has been released.

Actually we are on Beta 15 now. Please read the policy at https://www.drupal.org/contribute/core/beta-changes

mgifford’s picture

mgifford
he/him
Primary language English
commented

Just cleaning up the 8.0 postponed items. Thanks for bumping it to 8.1.

mac_weber’s picture

mac_weber commented

Postponed items are like this because they should wait for the end of Beta. It is not about the version change.

New features cannot be added at this time.

mac_weber’s picture

mac_weber commented
Status: Postponed » Active

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

nicholas.alipaz’s picture

nicholas.alipaz commented

This seems like a much needed feature. Keep running into this on projects and having to write pseudo field every time.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

droprocker’s picture

droprocker commented

Any News upon this issue? I just ran into the same problem. I just wonder that this issue is 5 years old and still no solution? Or am I missing something?

dubs’s picture

dubs commented

+1 from me. This would be a very useful feature to add.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

limehouse’s picture

limehouse commented

+1 here 2! Thanks.

xenophyle’s picture

xenophyle commented

I have been using https://www.drupal.org/project/fixed_text_link_formatter. Works real good.

limehouse’s picture

limehouse commented

Perfect! Thanks very much for taking the time.

dubs’s picture

dubs commented

Thanks for that comment - I'll check that formatter out :-)

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

alphex’s picture

alphex commented

Bump this.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

dcam’s picture

dcam commented
Status: Active » Closed (won't fix)

Thank you for your suggestion to improve Drupal Core! I'm going to close this issue on the basis that there wasn't a lot of support for the idea over the last 12 years and that there's a contrib module that does what is asked. If anyone needs this functionality, then I suggest you download and install the fixed_text_link_formatter contrib module. I'm not certain that it supports tokens, but it could probably be updated to do that.