dear all,
I want to unpublished note so that user won't see the "draft translated content"

I added this,

$new_node->status = 0;

and I found only 1 of the 2 translated node unpublished..

am I doing anything wrong ?

many thanks

CommentFileSizeAuthor
#7 i18n_auto_inherit_and_unpublish.patch663 byteslolandese

Comments

spacereactor’s picture

i think this function is not ready. http://drupal.org/node/684376 i not a programmer but you can try with rule setting.

bensquare’s picture

@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.

Narretz’s picture

subscribing

this is defintely an important feature

greg.harvey’s picture

Hack away, just provide a patch of your hacks so they can be included! That's the idea... ;-)

klonos’s picture

Title: unpublish translated note -? » Unpublish draft-translated nodes

... a better title so people can locate this.

DanielAntonsson’s picture

I added the following lines under "prepare the new node":

$new_node->comment = $node->comment;
$new_node->promote = $node->promote;
$new_node->format = $node->format;
$new_node->status = 0;

It copies the settings for comments, front page promotion and filter from the source node and sets the new node as unpublished.

lolandese’s picture

StatusFileSize
new663 bytes

I had to practice to roll a patch. Used #6 to do so.

greg.harvey’s picture

Status: Active » Needs review
greg.harvey’s picture

Status: Needs review » Needs work

Ok, 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.

klonos’s picture

...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:

Default publish behaviour for new content types:

	(*) Set to "Do not publish draft-translated nodes".
	( ) Set to "Publish draft-translated nodes after translation".

Current publish behaviour for existing content types:

	Content type | Publish draft nodes
	-------------|--------------------
	page         |       [V]
	-------------|--------------------
	article      |       [V]
	-------------|--------------------
	poll         |       [ ]
	----------------------------------

[ Save settings ]
greg.harvey’s picture

greg.harvey’s picture

Status: Needs work » Closed (won't fix)

Sorry, this project is no longer supported - strongly advise you move to using https://drupal.org/project/tmgmt