The content types in the advanced search are not translated

The advanced search form is generated by the core search module, not Custom Search… Where have you find the related node_type_get_names() in the i18n submodule?

@cmseasy: which selector are you talking about? In the advanced search form (as this issue title says), or in the search block?

I have same issue.
When change the language in my website, in a block with custom search the content types name not change language.
Not change also the language select for search or in italian or in english.
Sorry for my english!!!!

This small patch apply to latest dev version and make the names of content types translatable.

Thanks.
Pushed to Dev and Custom Search 7.x-1.19.

I've upgraded to the new version (7.20) but the content types are still not using the translated entities nor do I see the option to translate the content types in when I translate the interface.

How should the content types be translated?

Hello,

I'm facing the same problem. I have the newest update of the module. Is there any other solution yet?

Best regards,
Mariska.

FYI, wrapping the names in t is not a good solution... you need to use i18n here. Otherwise the end use will have multiple places where they need to translate the content-type name.

+    if (module_exists('i18n')) {
+      $name = i18n_node_type_name($machine_name, $name);
+    }

.

Same here:
- custom-search-7.x-1.x-dev
- custom_search_i18n-7.x-1.x-dev
- i18n_node-7.x-1.26
- translation-7.59

Already checked translation on admin/config/regional/translate/translate and make sure content types were translated.

Still, no translation on content types when user searches on en/search/node/example_term_search

Any tips?

It looks the (bad) patch got committed, with the content type name wrapped in a 't'. Here is the code in the dev version of this module:

       if (count($types)) {
          $names = node_type_get_names();
          if (count($types) > 1 || variable_get('custom_search_' . $delta . 'any_force', FALSE)) {
            $toptions['c-all'] = variable_get('custom_search_' . $delta . 'type_selector_all', CUSTOM_SEARCH_ALL_TEXT_DEFAULT);
          }
          foreach ($types as $type) {
            $toptions['c-' . $type] = t($names[$type]);
          }
        }

So this means that translating your content-type in the "Node types" text group will not be enough. You will need to translate it a second time in the "Built-in interface" text group.

The "node type" string won't be available on "Built-in interface" if that string is not cumulative used somewhere else.

So, that's not a working solution, like you said on #12.

Hi,

The content types are not being translated. I have tried to look into the code and the module appears to rely on node_type_get_names() which doesn't print the translation of the content types.

I have managed to solve my problem by overriding in template.php with this content:

theme/custom_search.pages.inc

by using i18n_node_type_name() in the two functions, I was able to show them translated in results page, which is fine.