How to assign priorities?

yeah, it's done on each node's translation tab.

I guess I'm dense too, but I don't see where to set this at all. Perhaps a quick README file would help? I'd contribute one, but I don't know how this works.

[I'm assuming you're already translating nodes and understand that work flow.]

First off I'd say grab the 6.x-2.2 version it's got some big bug fixes. Then make sure you've assigned the management permissions to the roles that should be able to assign priorites, then on each node's translate tab you'll see radio buttons to set priorities for each language. See the attached picture.

Humm, that "search for existing nodes to match up as translations" bit at the bottom isn't from Translation Overview. It looks like that another module and TO are fighting over the form and TO is loosing. What other internationalization modules do you installed?

try disabling the synchronize translation module and see if that helps.

I have the same problem - here's my module list.

EDIT: Have turned of synch trans.

I also don't have access to this funcionality.

Using the i18n v1.1

Tried to disable all submodules, but still no priorities. Only when i18n was completly disabled, the options appeared.
Changed the weight of module on the system table to 11 (i18n is 10 in my system) but no go.

Hope this helps solving the issue.

Thank you for this module!

Forgot to add that the option to search for another node on the translate page is being added by the i18n core module since release 1.1.
See #295682: SOLVED: Choose an existing node as a translation.

The culprit is the i18n module itself.

See i18n_menu_alter() in i18n.module:

/**
 * Implementation of hook_menu_alter().
 *
 * Take over the node translation page.
 */
function i18n_menu_alter(&$items) {
  $items['node/%node/translate']['page callback'] = 'i18n_translation_node_overview';
  $items['node/%node/translate']['file'] = 'i18n.pages.inc';
  $items['node/%node/translate']['module'] = 'i18n';
}

Compare to hook_menu_alter() implementation in TO:

/**
 * Implementation of hook_menu_alter().
 */
function translation_overview_menu_alter(&$callbacks) {
  // Replace the translation module's node tab with our own.
  $callbacks['node/%node/translate']['module'] = 'translation_overview';
  $callbacks['node/%node/translate']['page callback'] = 'translation_overview_node_page';
  $callbacks['node/%node/translate']['file'] = 'translation_overview.pages.inc';
}

I believe it's hard to find a solution as both modules provide different features adn overriding forms rendered in tables is not easy. Maybe it could be possible to integrate TO features in i18n? ...or maybe TO could provide its own method to assign priorities from the node edit form?

I don't think the node edit form needs another option/field in there.
Perhaps as a tab in the translation overview page? It would filter, only showing the relevant nodes and it would be a central place to control priorities.

This ofcourse would be a major change in the module... :P

Spam!! Kindly delete the above post.

Why did you changed the issue information?

I'm changing it back.
If there is any problems, commentary or solutions, for the issue please specify, and change anything back accordingly.

Thanks!

Quick fix: Increasing the module weight to 100 in the system table puts the TO forms onto the Translate page in place of the i18n ones.