|
|
|
In the help for the glossary block config, the text is displayed in a popup window as follows..
<b>Last modified entry</b> will always display the entry that was last modified, and <b>Random entry</b> will choose a new one at random every time. The option <b>Next entry</b> will cycle through the entries in order. This last option is especially useful when a number of days is also chosen, allowing you to make a <i>Quote of the week</i> or a <i>Tip of the day</i> that everyone sees.
Obviously the intention is that some terms will be bolded or italicised but because the text is being passed through the url rather than as a file, its not working.
|
|
Description
|
In the help for the glossary block config, the text is displayed in a popup window as follows..
<b>Last modified entry</b> will always display the entry that was last modified, and <b>Random entry</b> will choose a new one at random every time. The option <b>Next entry</b> will cycle through the entries in order. This last option is especially useful when a number of days is also chosen, allowing you to make a <i>Quote of the week</i> or a <i>Tip of the day</i> that everyone sees.
Obviously the intention is that some terms will be bolded or italicised but because the text is being passed through the url rather than as a file, its not working. |
Show » |
|
I think we should:
1) Transform that call to helpbutton() to use one standard help file (lang/en_utf8/help/block_glossary_random/type.html)
2) Review if there are more uses of helpbutton() using $text contents instead og external help files. Fix all them to use standard help files.
3) add debugging message to helpbutton() in case it receive something in $text, informing it's not the recommended way.
Note that the $text option won't work properly because the text needs to be always cleaned and, when cleaned... html tags always break, so it's unusable. That's the cause I suggest to move all current uses of $text in that function to real help files usage.
Confirm with MD, plz. TIA and ciao