Localizer module and the category module [#102874]

Working in a site with a links directory, I have one problem... I am making mi directory using the category module. So the structure is something like this:

Paises (Container)
--España (category)
----Link 1 (weblink)
----Link 2 (weblink)
--Italia (category)
----Link 1 (weblink)
--Francia (category)

and so on. The problem is that when I made the translation, it end up like this:

Paises (container)
--country (container)
--España (category)
----Link 1 (weblink)
----Link 2 (weblink)
--Spain (category)
--Italia (category)
----Link 1 (weblink)
--Italy (category)
--Francia (category)
--France (category)

In another words, it duplicates the content, and both categories (spanish and english) are show no matter what is the language select.

Comments

Comment #1

acappellamaniac commented 13 December 2006 at 12:44

I have a similar issue with the parent level dropdown when creating a book page - it allways shows all entries for all entered languages.
Any ideas ?

Comment #2

Roberto Gerola commented 13 December 2006 at 14:38

I'm working on a new version of localizer. I have almost finished the support for taxonomy module.
The new version provides also APIs for external modules and its own strings translations utility and table.
It will not depend anymore on t() function and locale module, but the translation interface is integrated
in menu, taxonomy and so on.
The plan is also to provide a general console translation where to manage all content strings.
Don't worry, if you have already used the locale module to translate the strings, I'll help you to write
the SQL code to import your strings in the new table.
I hope to be able to make a release in the next days.
I'm working very hard on it.

Comment #3

Roberto Gerola commented 19 December 2006 at 15:00

Can you try the new 2.1 release and let me know if it works now ?
Thank you.

Comment #4

Roberto Gerola commented 29 December 2006 at 09:32

Status:

Active

» Closed (fixed)

Comment #5

summit commented 23 February 2007 at 10:39

Status:

Closed (fixed)

» Active

Hi,

I am activating the issue with the category module if it is ok. If not sorry for the trouble.
I am also using the category module on drupal 4.7.6
I was wondering if it is possible still use one category language (I have the whole world in vocabulairy, and don't want to translate it all.
But now when I use the localizer module I don't see my categories with the translation to another language.
Can you please help?

Thanks in advance,
greetings,
Martijn
www.best-information.eu

Comment #6

summit commented 23 February 2007 at 10:57

The Localizer module and Category module have a strange behaviour.
If you type the TRANSLATIONS TAB and hit save the translated version is saved with the right category. But when you change category all other settings are gone.
I use panels with taxonomy blocks, so the panel is not working if category is changed!
How can I get rid of the message that you need to select category?

greetings,
Martijn

Comment #7

summit commented 2 March 2007 at 22:58

Hi,

I corrected above issue myself, but have still problems with Localizer and Taxonomy (Catalogy module)

My situation is: I want 1 container with categories in it and 1 container with regional info (countries/provinces/cities).
I want to put content categorized in these 2 containers.
This works fine without translation (localizer module).
I use the taxonomy block module to show the content.
This all works fine.

But now I want to use the Localizer module to have translations of the categories
I figured out how to add content on node level within one container and keeping the same category.

I have a problem using the great module.
When I click in the [TRANSLATIONS] button (above the content) when I want to translate a Category, a menu item is immediately made right under the allready existing menu-item. So now there are 2 menu items with the same name )or translated namw). Next to this if you set a container to be without language (the "-" option there is after the translation the translated category also stated. But now when you select this new category the content is not related to the original "-" category anymore!
I think the right behaviour for categories/taxonomy should be exactly the same as with items within nodes.
You don't see the translated items until the correct language is selected, but in the background the information is available.
With category behaviour as it is right now it is difficult to use this module. So right now I keep the non-language "-" for the category, but it is not how I would like it to be!

Is this achievable. Do I do something wrong?

Comment #8

edinjapan commented 3 March 2007 at 11:39

I have tried to replicate your issue, but am not quite seeing what you are seeing. (Or maybe have not understood your issue.) When you first create a category (Add vocabulary), you type in the information into what I will call a "top non-locale specific container", but AFTER you have successfully applied your translations for this, I don't see where "-" comes into play.
I wonder if what you are experiencing may be from one or more translations not being complete, or if it has to do with your Hierarchy settings. (I have mine set to single.)