Hi Justin,

Great module you created, really ! Do you plan to make an i18n integration ? On a multilingual website, it would be great...

Thx,

Gilles

Comments

gillesbailleux’s picture

Title: i18 integration » i18n integration
jweberg’s picture

That is in the plans. I don't know much about it though. If someone is willing to tackle this, that would be great.

jweberg’s picture

Status: Active » Postponed

We'll work on this for the 2.x release.

gillesbailleux’s picture

Thank you very much for taking care of my request.

milos1234’s picture

have you tried making it a multilingual variable? you can set it in settings.php i imagine that would fix it.
:)

milos1234’s picture

i can confirm that setting multilingual variables for any of the 3 custom search box fields works! yay

jweberg’s picture

How would I add this functionality into the module? The point of the module is to make things as easy as easy as possible. Let me know. Thanks.

milos1234’s picture

if you wanted to make it changable in the module, you could possibly apply a patch similar to the one for nodewords http://drupal.org/node/130389#comment-1309964

or, how i have done it, is to turn the variables into multilanguage variables, so i can set one for each language i am viewing the site in.

explained here:
http://drupal.org/node/23064

the variable i added for custom search text is 'custom_search_box_default',

mokko’s picture

This is a nice little module! Very useful! It makes the impression that is not yet quite finished.

I removed block title and used the multilingual variables. Now I can basically translate the search box.

Let me just make things (written already above) a little more explicit:

if you have multilingual site you are likely to know about

$conf['i18_variables']=array {};

already.

Now add:

custom_search_box_label,
custom_search_box_default,
custom_search_box_text

switch language on admin/settings/search

dddave’s picture

Glad I found this. Translatability is a major concern for my site and I am very glad that this can be done via multilingual variables.

There should be some docs/link to this issue on the project page imho.

jweberg’s picture

Thanks for the info. We are working on getting a new version out that fits the drupal coding standards better and allows for easier expansion in the future. I originally started this module as a simple little fix for a issue that too many people were having and there really wasn't a good way to do it. Once we get the frame for the new version we will be able to start adding these additional features that we are getting requests for. It seems you are well aware of i18n integration and could really use some help with it. Please let me know if you are able to help out.

Thanks
Justin

jdanthinne’s picture

An other module I've written, Custom Search is inspired in part by this one, but greatly enhances it, as well with other options (content type & taxonomy pre-selection), and is i18n-friendly (originaly developed for a multilingual site). Have a try!

jweberg’s picture

Status: Postponed » Closed (fixed)