This PR changes the language file for the Smart Searchr (com_finder) so that the "Smart Search content plugin is not enabled. Changes to content will not update the Smart Search index if you do not enable this plugin." contains an hyperlink to the Plugin Manager.
Test instructions
In back-end > Components > Smart Search
If the Smart Search - Content Plugin is not enabled, it will display a message "Smart Search content plugin is not enabled. Changes to content will not update the Smart Search index if you do not enable this plugin."
This PR changes the language string
so that the warning message has a hyperlink to the Plugin Manager,
including a filter option for the name "Content - Smart Search".
Result of that hyperlink
If you click on the hyperlink you will be redirected to the Plugin Manager,
which filters the "Content - Smart Search" so you can easily enable it.
What makes you think assuming the labels are the same is better than assuming the id's are?
Sounds to me that using the id's is better, provided they are determined on execution time.
That requires the isEnabled to retrieve both enabled and id, introduce the getPluginid and replace that in the message with sprintf.
Then this works no matter the language used by the administrator in the backend!
It is also prepared for the time Joomla doesn't hard code these id's anymore!
I understand your concert @sovainfo. IMHO in this case labels are better than IDs provided that the reference to the Plugin Name is translated correctly.
I've added a comment for translators (thanks @infograf768 for this suggestion in a similar PR #6947 )
joomla-cms-bot
- 
RTC
wilsonge
-
even tiny steps like these will increase usability. Thank you @pe7er
This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/6948.