Create node relation in a multilingual site
Kameleonten - October 10, 2009 - 18:26
Hi,
I'm about to setup a bilingual site and found that drupal present all nodes in one non-related list/pile under /admin/content/node. My site will contain a lot of nodes and will be translated, so I would like to some how create related nodes or put nodes in "folders" where I easily can administer them.
Ex of hieararchy:
Eng
--->Main_eng
--->Node1_eng
--->Node2_eng
--->Node3_eng
Swe
--->Main_Swe
--->Node1_Swe
--->Node2_Swe
--->Node3_Swe
I've tried to find solutions for this in the forum but found nothing, probably because I don't really know what to look for.
Do anyone have a solution for this? Or how do you manage your site with thousands of nodes?
On the admin/content/node
On the admin/content/node page, you can set a filter for Language, as well as Type (read carefully at the top of the page). This will make managing your list of nodes much easier. If you like, you can always use the Views module to create custom lists if you have more specific needs. With Views you can create an Exposed Filter that will put a drop-down of filtering options on the listing page.
______________________________________________________________________________________________________
mybesinformatik.com - Drupal website development
I think this might help
I think this might help you organise your translations:
http://drupal.org/project/translation_overview
Assuming you are going to use the core 'locale' and 'content translation' modules, are you aware that a 'link' or 'reference' is created automatically between translated nodes? In other words, you won't to have to manage the translations as though they are completely separate from each other; Drupal knows that some nodes are translations of the same text.
Note that, whilst the core node translation works quite well, there are many problems with multilingual sites with regard to translating menu blocks, menu block titles, menu-items, block titles, taxonomy vocab and terms, content-types, Views, cck fields, paths, etc. Plus most language packs have many hundreds of untranslated core strings, and many contributed modules are not translated at all. It is these aspects that make it almost impossible to have a fully multilingual site, and it is a horrible, frustrating experience trying to get as far as you can. Certainly, I will never try to make a multilingual site again with D6 unless someone puts a gun to my head!