Closed (outdated)
Project:
Search configuration
Version:
6.x-1.6
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Oct 2009 at 16:51 UTC
Updated:
7 Mar 2016 at 10:47 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jbomb commentedInteresting, the hook_form_alter implementation is not noticeably different from the implementation in node_form_alter, which it replaces. Please try the attached patch.
Comment #2
jbomb commentedcommitted to dev. Reopen if this issue persists after 6.x-1.7
Comment #4
Dret commentedThe Patch works good!
But is not included in 6.16 version!
Comment #5
alan d. commentedThis has been committed into the dev branch, so is fixed but is simply not released.
Comment #6
yang_yi_cn commentedI disagree with the approach for #1, which basically generate another string for translation.
The i18n module (the i18n content type sub module) have handled this issue in a better way, which is to create the node type name string in a separate text group, so it can be reused in many places. It also alters the Drupal default search form with the correct translation.
My patch will alter the search form in such a way that it just use what ever string values it passed within the form, so if it's translated already, it will not get overwritten here.
Comment #7
alan d. commentedClosed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.