Selecting multiple languages through "Node source" admin panel [#1532478]

Comment	File	Size	Author
#9	no-default-language-1532478-9.patch	1.48 KB	berdir

Comment #1

ethanethan commented 17 April 2012 at 16:19

Exploring a bit today, i saw that jobs requested through the "Node Source" tab also don't obey quick checkout settings (when there is only one translator available).

Is there a reason why "node source" doesn't behave similarly to the "Translate" tab of a node?

Log in or register to post comments

Comment #2

ethanethan commented 23 April 2012 at 01:11

I'd be interested to hear what the devs think about this. What ya think?

Log in or register to post comments

We will add this. This is not limited by our API (it allows this, theoratically), but we don't have a UI for that yet (this is rather complicated). It is even more complicated in this case because we want to re-use as much of the existing and flexible functionality that is already out there (views, views bulk operations, etc.). We will probably have custom field form handlers (views) for this at some point. Also our UI will become really nice once all the core functionality is fully (and nicely) working (AJAX, etc.).

Log in or register to post comments

Comment #4

ethanethan commented 24 April 2012 at 15:05

Ok, sounds good. Sounds fairly long term, though, for something fully featured. I am working on a project that requires an efficient workflow for multiple content nodes, so we'd like to request translations from that node source page. Should i create a ticket for implementing the multistep checkout process? Or could i make some modifications in my custom translator so that multiple languages are processed (quick checkout) and automatically accepted?

Log in or register to post comments

Comment #5

berdir

German

Switzerland

commented 24 April 2012 at 15:17

The reason for this is that the rule to start a translation currently only supports the creation of a single job, which means that all selected nodes must have the same source language.

We probably need to replace that rule with a custom action (hook_action_info()), which is better integrated with VBO, then we can use tmgmt_ui_checkout_job($jobs) there which supports multiple jobs and can also do the autosubmit if possible.

Would be great if you want to work on that.

Once that is resolved, we can simply change the default view to allow multiple values for that exposed filter.