We needed to be able to customize the default texts that are shown in the feedback div by using the browser (no editing of .po files, which requires access to the server), so I've created the patch included in the attachment. One can customize the help text, the title of the message and the title of the div box itself (in here one can use HTML text, let's say if he wants to have an 
tag instead of plain text).
The form used to customize the texts can be found under /admin/settings/feedback .
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | feedback-797726-8.patch | 3.56 KB | danepowell |
| #5 | feedback-797726-5.patch | 3.58 KB | danepowell |
| feedback_texts_customization.6.x-2.x-dev.patch | 3.53 KB | mihai_t |
Comments
Comment #1
awlo commentedLooks great, hope the maintainers will agree.
Comment #2
danepowell commentedLooks solid, except you mention that you should be able to use HTML in the help text, and your use of check_plain() prevents this.
Comment #3
jody lynnYou can use http://drupal.org/project/stringoverrides or core locale module to override any string.
Comment #4
dawansv commentedI am a little surprised to see a "won't fix" on this. As mush as stringoverrides or locale can be used, it seems overkill for what might be considered a standard feature. In my experience, most modules offer options to customize their own strings... IMHO stringoverrides should be reserved for last resort, rare case uses...
That said, this is a great module, and many thanks to the dev team...
Comment #5
danepowell commentedHere's a slightly updated patch, rolled with git...
Comment #6
jody lynnOk, but new features need to go into the 7 branch at this point first.
Comment #7
sunUnfortunately, this is still a tough problem space in Drupal. By making the strings configurable, t() can no longer be used for localizing/translating them into the current language. Additional support code for i18nstrings module of the i18n project would then be required in order to make the configured strings translatable.
That's a extremely big and effin' mess, and when considering all of the required work for that, suggesting people to simply use $string_overrides in settings.php (or whatever the variable is called), or a hook_form_alter() to perform wanted string adjustments... sounds more appealing in terms of module maintenance, dependencies, etc.
Comment #8
danepowell commentedI understand it's not ideal, but here's an updated patch against 6.x-2.2 (I am using this solution in production until a better alternative is figured out)
Comment #9
henrijs.seso commentedIt seems there are 3 problems with form customization - a) translation b) immobility of "Message" text area and c) fixed "If you experience a bug..." text. Am I correct?
a) Since this is entity form in D7 there should not be problem of translation with i18n module
b) "Message" text area should be similar to nodes body field, there by default, removable or re-arrangeable
c) possibility 1) If we place all fieds in default textarea with description "If you experience a bug...", then we could change it from site to site.
Comment #10
jody lynnI just don't understand why you don't use the stringoverrides module or override the individual strings in settings.php. That is the mechanism for overriding administrative strings in Drupal, and having settings to change every bit of interface text in every module seems unnecessary.
Comment #11
mparker17The Drupal 7 version is no longer available, and no longer maintained. So I'm going to close this issue as outdated.
(If you'd like to maintain the Drupal 7 version, please post an issue in the queue)