NO BUG: Rich Text Dynamic Data Link Protocol Issue

Bugs
1

Not sure if a bug or intended for ease of use.

Using Rich Text and inserting a link using dynamic data - as its linked to the main brand so I store this in a Meta Box settings page.

The link pulls through all ok but the Rich Text adds http:// to the beginning of the URL when you apply the link.

When I have a full link (https://www…) this renders my DD link incorrect on the Rich Text editor end on the frontend, making the link unusable.

Could we remove the auto addition of the http:// at the front of the url ??

Link in Settings page

image
image908×170 33.9 KB

Link in Rich text with DD only

image
image904×226 47 KB

After clicked apply and gone back to edit

image
image874×232 48.4 KB

Rendered on the front end

image
image860×200 42.4 KB

2 Likes
2

Hi Dan,
Thanks for your report!

The link field only checks whether the entered text already contains a protocol or not. If you type in any word (without a protocol), you will get the same result.

Even if the dynamic data tag contains a link, it is still just text like {your_tag}. Personally, I see no reason to make the dynamic data tags compatible with the link field at great expense, because the intended use is probably rather rare.

In that case, you can also insert the link manually, which will certainly take a few seconds longer, but it works without any problems.

However, I could be wrong. Feel free to submit this as a suggestion on the Idea Board, let’s see if it makes it to the list and if so, how many votes it gets.

Best regards,
timmse

1 Like
3

Just run into this again and looking at it, it is probably just easier to enter the link manually. Might have to rethink my custom fields and perhaps add the protocol as a pretext to avoid this. Trying to make things easier for clients and having to tell them to manually add a link on the text tab is not the best but hey.

One suggestion, is the protocol defined as http in Bricks or is it a WP thing? If Bricks, could this be changed to https perhaps? Nowadays everyone is using https

4

In that sense neither. It’s a tinyMCE thing, but we can customize it if we get the chance. Makes sense :slight_smile:

5

Hey Dan,
We would like to change the link protocol, but we have to wait until WordPress updates TinyMCE, because the change of the protocol is only supported from version 5.x on. Currently, WordPress still uses version 4.9.x.

1 Like