Closed (won't fix)
Project:
i18n auto translate
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
17 May 2010 at 00:13 UTC
Updated:
2 Oct 2013 at 10:14 UTC
Jump to comment: Most recent file
Comments
Comment #1
spacereactor commentedi think this function is not ready. http://drupal.org/node/684376 i not a programmer but you can try with rule setting.
Comment #2
bensquare commented@spacereactor
thx for your reply mate..
I tried the RULES modules, but I only managed to unpublish all new create (note) included the original also..where I only want original published and those 2 autotranslated nodes to be unpublished .
I think you are right that the function is not ready yet and it was just me tempting to hack the modules :P nearly there...
I love this module, it's just my opinion that default option should set to "unpublished" as those NEW autotranslated node is always a bit far from properly translated.
Comment #3
Narretz commentedsubscribing
this is defintely an important feature
Comment #4
greg.harveyHack away, just provide a patch of your hacks so they can be included! That's the idea... ;-)
Comment #5
klonos... a better title so people can locate this.
Comment #6
DanielAntonsson commentedI added the following lines under "prepare the new node":
It copies the settings for comments, front page promotion and filter from the source node and sets the new node as unpublished.
Comment #7
lolandese commentedI had to practice to roll a patch. Used #6 to do so.
Comment #8
greg.harveyComment #9
greg.harveyOk, this is straightforward enough. Quick question though - should this be optional, or should it be enforced? Current patch *enforces* the setting of new nodes to unpublished. Is there not a possible case where people want to show the node? E.g. in a crowd sourcing effort where this module does the initial legwork?
I think so, so marking as needs work. I think we need an admin UI to pick this option.
Comment #10
klonos...yep. I think it should be optional, either global or per content type or both. By "both" I mean to simply provide a global setting for what the default per content type setting should be for new content types. The global setting should "live" under the module's admin page, while the per content type can either be a on/off setting in the content types' config pages or a list (table) where one can adjust the setting for all current content types. Like so:
Comment #11
greg.harveyMarked #684358: Add admin option to optionally unpublish auto draft nodes as a duplicate.
Comment #12
greg.harveySorry, this project is no longer supported - strongly advise you move to using https://drupal.org/project/tmgmt