Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Comment | File | Size | Author |
---|---|---|---|
#6 | custom_search-translate_content_types-2165063-6.patch | 630 bytes | andypanix |
Comment | File | Size | Author |
---|---|---|---|
#6 | custom_search-translate_content_types-2165063-6.patch | 630 bytes | andypanix |
Comments
Comment #1
jdanthinne CreditAttribution: jdanthinne commentedThe 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?
Comment #2
cmseasy CreditAttribution: cmseasy commentedSame issue here.
Using contenttypes (with translated names) as selector, the default language is shown in the select options in all languages. Is this related to the i18n submodule?
Comment #3
jdanthinne CreditAttribution: jdanthinne commented@cmseasy: which selector are you talking about? In the advanced search form (as this issue title says), or in the search block?
Comment #4
cmseasy CreditAttribution: cmseasy commentedIn the search block: see http://herder.com.mx/ in the menu.
The "refine your search" "- all -" and "close" are translatable, the contenttypes are not.
Libros / Books is a contenttype, I cannot change it to "Books" and the translation "Libros"
Maybe a different issue, but related...?
Comment #5
msweb69 CreditAttribution: msweb69 commentedI 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!!!!
Comment #6
andypanix CreditAttribution: andypanix commentedThis small patch apply to latest dev version and make the names of content types translatable.
Comment #8
jdanthinne CreditAttribution: jdanthinne at AppTree commentedThanks.
Pushed to Dev and Custom Search 7.x-1.19.
Comment #10
rroose CreditAttribution: rroose commentedI'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?
Comment #11
MariskaTh CreditAttribution: MariskaTh commentedHello,
I'm facing the same problem. I have the newest update of the module. Is there any other solution yet?
Best regards,
Mariska.
Comment #12
joel_osc CreditAttribution: joel_osc at OpenPlus commentedFYI, 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.
Comment #13
alexeye CreditAttribution: alexeye commented.
Comment #14
jrochate CreditAttribution: jrochate commentedSame 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?
Comment #15
joel_osc CreditAttribution: joel_osc at OpenPlus commentedIt 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:
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.
Comment #16
jrochate CreditAttribution: jrochate commentedThe "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.
Comment #17
jrochate CreditAttribution: jrochate commentedHi,
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.