Description of the need
This is an extension of issue: #1926 which handles the removal of links from a global level by utilizing a class="nolink".
Currently if a text format enables links to be automatically converted to html links, there is no way to keep a link from being removed by a content editor.
Proposed solution
What I propose is to create a pseudo token type of API where a colon can be added with some text to negate some sort of effect that has been automatically added by a text format.
I think this should be left open-ended to allow other pseudo tokens, however the only one I can think of off hand is :nolink which in practically would be done as: www.somelink.com:nolink and would result in plain text instead of the link being automatically rendered as an HTML link.
I like the idea of Core handling :nolink OOTB but I think the structure should allow other pseudo tokens through contrib
If there are no other use-cases where this could be applied, then the :nolink would be the focus.
Alternatives that have been considered
The issue in #1926 fixes this on a macro level where a site builder / admin / developer have access to the code or permissions to add this through the GUI however editors have no power to be able to do the same thing on a micro level.
Is there a Drupal or Backdrop contributed module that accomplishes this?
Unknown
Additional information
The other thing to consider is the name. I personally am not sold on the use of "token" but I do like the use of "pseudo" to fall in line with how CSS pseudo elements work.
Draft of feature description for Press Release (1 paragraph at most)
(Assuming :nolink is the only pseudo token implemented)
Backdrop now includes pseudo tokens that will give content editors the ability to convert an automatic link into plain text by using the format www.sitedomain.com:nonlink.
Recent comments
Hello @NumerousHats, I agree with your assessment. I am looking into this situation right now. The root of this problem is that Backdrop CMS is implemented on top of a "stack" of...
Update Core and Theme via Web interface
I just installed a Backdrop CMS site with version 1.27.0. I then used the user interface to download and update Backdrop CMS to 1.30.0. After starting the update process, and on the...
1.30.0 update.php generates incorrect link
I believe my permissions are set up correctly, as I can install modules from the UI. But for whatever reason, I can't update them. I will, however, double check against that documentation.
Update Core and Theme via Web interface