User tests: Successful: Unsuccessful:
Pull Request resolves # .
This change allows you to use custom text for links in the URL field.
The original link names are not applicable by the site administrators. Since the default link names are extremely useless for the site. Simply linking to a website doesn’t mean anything; anyone already knows that a link leads to a website. Therefore, the written text of the link stating that it opens the website is useless, hinders navigation, and interferes with the intuitive understanding of the link.
Let’s assume that 2 different links to different websites need to be attached to the material: one link to Telegram and the other to YouTube. In both cases, the links will have the name “Visit Website”. No one will ever click on such a link, because it evokes fear — what if there’s a virus? And the link doesn’t explain why I should click on it in the first place.
Here, it is not applicable to use the override of INI localization constants. Since the text displayed for the link uses the global INI constant from the joomla.ini file.
The text “Visit Website” and “Visit Link” was displayed, with no option to specify custom text for the link.
In addition, you can now specify your own custom link name for this field.
Please select:
No documentation changes for guide.joomla.org needed
Documentation link for guide.joomla.org:
No documentation changes for manual.joomla.org needed
Pull Request link for manual.joomla.org:
| Status | New | ⇒ | Pending |
| Category | ⇒ | Administration Language & Strings Front End Plugins |
| Labels |
Added:
Language Change
PR-7.0-dev
|
||
| Title |
|
||||||
| Title |
|
||||||
I can see what you are doing here but it doesnt really solve the problem. You are simply changing the fixed string from the language file with a fixed string in the field config. It doesn't let me set a string specifically for the url
| Title |
|
||||||
Maybe I’m wrong, but it seems like everything worked for me as I described in the description.
First, specify the external link in the article field. On the client page, we see the article with the A tag:
<a href='$url'>Visit Website</a>But now the link will (should) look like this.
<a href='$url'>User text with a description of the website being opened.</a>The text is inserted from the plugin field settings.
It worked for me.
Did you enter the link name in the plugin field settings?
The text is inserted from the plugin field settings.
Which means its the same text for every time you use the field
Which is exactly what you could already achieve with a language overide of JVISIT_WEBSITE="Visit Website"
I was expecting to be able to add unique text for every time I used the field
What does “unique text” mean each time?
After all, in this change, we can set a unique text for the created field.
Are you suggesting creating it for each article separately?
If we override the constant JVISIT_WEBSITE="Visit Website", we will override it not only for all URL plugin fields, but for the entire website.
But my PR allows you to set your own text for the created field. Not for all fields of this plugin at once, but for a single field. For example, you can create a YouTube field; for all articles, you can specify the YouTube link in this field.
Perhaps you got confused in the analysis; the field has 2 XML configuration files. One of them is the plugin configuration, and the second file is the field configuration. I’ll note that I added a new field not for the plugin, but for each field.
No I am not comfused
No I am not confused
Are you suggesting creating it for each article separately?
yes
This will be a fundamentally different field. The new desired change requires that the field value in the database contains not only a reference but also the field name.
Such a field will require the value to be serialized for storage in the database.
In this case, you can create a new field with a new name, Link; this name is more suitable for the new functionality.
This will be a fundamentally different field. The new desired change requires that the field value in the database contains not only a reference but also the field name.
Such a field will require the value to be serialized for storage in the database.
In this case, we can create a new field with a new name, Link; this name is more suitable for the new functionality.
🤔It feels like no administrator has used this plugin at all. Since only a layout designer or a programmer can configure this plugin.