According to README.TXT, "There's a new [flag-note] token when using this module with flag_action (or/and rules) and if the token module is active". However, those token support is only available where tokens should not be visible (in the user-editable text area), and they are not available, where they are needed (in "Flag note form title", "Flag note fieldset legend", "Flag note textarea label", and "Flag note help text (behind textarea)").

This is really bad since a flag note form looks by default like this:

Flag note

Flag note

Flag note: _____________________________________________

Flag note

Really dumb, isn't it? How is a user supposed to understand what he/she can enter in this blank form? The form does not say to which kind of content it relates, and it does not even adapt to the name of the flag where it is used. These texts are redundant, and - without tokens - they can't be made meaningful. An example for a meaningful "Flag note form title" would be: "Note for [title]". This would also give a meaningful title in the browser. An example for a meaningful "Flag note help text (behind textarea)" would be: "Optional note why you put [title] on your [flag] list".

The only place where tokens are evaluated is the text area field - but that's the place where a user expects to be able to type something (and not to read what or why he/he is supposed to write something). If this text area is partially prefilled with some token-powered auto-generated text, how is he/she supposed to figure out that/what he/she can edit or write theirself? Especially, why should the user even bother to think what he/she could write since it is prefilled anyway? (Remember those meaningless auto-generated edit comments for revisions where the changelog says, over and over again: "This node has been changed. You could have entered here why you did this"?)

On the other hand, this threefold redundancy of unintelligent "Flag note form title", "Flag note fieldset legend", "Flag note textarea label" texts is a total waste of screenspace if everything relevant needs to go into the text area anyway. Finally you would end up with a "Note default text" like this:

This is an automatically generated note for [title] by [author-name-raw]. If you want to enter a notice for [titlel] yoursellf, just delete this text and write your own note.

This is bad usability, as bad as it can get. So please allow us to use tokens in "Flag note form title", "Flag note fieldset legend", "Flag note textarea label", and "Flag note help text (behind textarea)".

Thanks you!

Comments

gunzip’s picture

Title: Tokens are not available where they should be » Provi
Status: Active » Closed (duplicate)

According to README.TXT, "There's a new [flag-note] token when using this module with flag_action (or/and rules) and if the token module is active". However, those token support is only available where tokens should not be visible (in the user-editable text area), and they are not available, where they are needed (in "Flag note form title", "Flag note fieldset legend", "Flag note textarea label", and "Flag note help text (behind textarea)").

The [flag-note] token quoted has nothing to do with the tokens inside the flag note text area, see #549202: Provide token for flag note for use cases.

I mark this issue as duplicate, see #728710: Add Token support for flag note input settings. Atm i don't have enough time to implement this,
anyway you can contribute with a patch.

gunzip’s picture

Title: Provi » Provide token support for flag note form fields