After installing the search config modul in a multilingual site, the content types are not translated anymore in the advanced search. After removing the modul, the translations work fine again.

Comments

jbomb’s picture

Status: Active » Needs review
StatusFileSize
new637 bytes

Interesting, the hook_form_alter implementation is not noticeably different from the implementation in node_form_alter, which it replaces. Please try the attached patch.

jbomb’s picture

Status: Needs review » Fixed

committed to dev. Reopen if this issue persists after 6.x-1.7

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Dret’s picture

Status: Closed (fixed) » Active

The Patch works good!

But is not included in 6.16 version!

alan d.’s picture

Status: Active » Closed (fixed)

This has been committed into the dev branch, so is fixed but is simply not released.

yang_yi_cn’s picture

Version: 6.x-1.5 » 6.x-1.6
Status: Closed (fixed) » Patch (to be ported)
StatusFileSize
new708 bytes

I 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.

alan d.’s picture

Issue summary: View changes
Status: Patch (to be ported) » Closed (outdated)

Closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.