published source node appears as not published in the translate tab

Me too. I don't have access to our organization's SQL tables, but my guess is that the "published" flag gets frozen if the source material isn't published before the translation module is invoked. I'm going to try and ninja the tables to see if I can clear it up... wish me luck.

Please, try with the latest dev and see if the problem is still there.

Happened to me too.

This is what I did:

1. Create a content (Spanish) with "No published" status
2. Then create a translation (English) and mark it as "published"
3. Then edit the original content (Spanish) and mark it "published"

Led me to: The original language translation still marked as "Not published", despite of the node status of published, because each translation has its own status, but could not get it updated on the regular node edit page; so I was always seeing the published translation (English) despite the language.

Because of post #2, I downloaded the latest dev version on my dev site, and this problem got solved by unifying the edit form, so each translation can update its own translation settings, but this dev version didn't handle translations body and summary well, so rolled back...

So what I did was a little patch to the entity_translation_overview page, to always get the "edit translation" link to be able to acces the translation settings form, and skipped the edit button because it is already on the tabs for the node.

Before submitting a patch, please check the latest dev.

I seem to have the same issue with 1.0-alpha2. I also have another issue, which may be related to this one — plach, please tell me whether I should open a separate issue. I have a content type with translation (Enabled, with field translation" (i.e. translatable through ET). I created a language-neutral node of that type, and later realized that I need it in several language versions. I changed its language from "Language neutral" to "English". As soon as I do that, I get the translation form, but the original English version is always marked as "Not published" in the translations table (even though it is "Published" in the editing form, as well as in the list of content. When I try to open in as a non-admin user, I get "English translation unavailable for ... (name of the node in question here)".
If I change it back to "Language neutral", I see it again in the English version of the site. Funnily enough, even though there is no Translate tab nor the translations list anymore, I still see the (previously published) translations in the respective language versions of the site. I.e., I see my "language-neutral" original text in the English version of the site, but, say, the Russian translation (which cannot be unpublished, deleted etc. anymore) in the Russian version.
I cannot try the -dev version at the moment. (As far as I understand, it needs the -dev version of the core, and I am lacking the development environment now to install Drupal 7-dev core.)

this seems to be fixed with the latest dev release 7.x-1.0-alpha2+97-dev

Ok, thanks. Feel free to reopen if needed.

@stevieb: thank you, I have updated the module to the latest -dev, and I will check later how this latest version handles that situation.

I have the same issue using v1.0-alpha2 : source node keeps hidden (for non-admins) while everything else is published

Workaround: use your SQL ninja skills
A) phpMyAdmin inline edit select your DB then the 'entity_translation' table then update the status flag for the original node or ...
B) UPDATE `entity_translation` SET `status` = '1' WHERE `entity_translation`.`entity_type` = 'node' AND `entity_translation`.`entity_id` = $FAIL_NODE$

It solves the problem

I cannot recall where I found it, but for older versions of ET the "published source node appears as not published in the translate tab" bug could be fixed by adding to entity_translation.node.inc

/**
 * Update translation status of the source translation when changing the status
 * of the node.
 */
function entity_translation_node_update($node) {
  db_update('entity_translation')
    ->fields(array('status' => $node->status))
    ->condition('entity_id', $node->nid)
    ->condition('source', '')
    ->execute();
}  

The latest version (ET 7.x-1.0-alpha2+97-dev) seems to cope with the published source node status problem even without this (though the translation status (published/unpublished) does not actually control its visibility - see #1762064: Unpublished translations are visible to non-administrators).

Testing 7.x-1.0-alpha2+97-dev gives me weird results with several things. For a node that was neutral, English was selected and greyed out when I editing the node to switch language. Possibly not a big deal, but I couldn't select another language. Saving it without doing anything switches it to English. Now the Edit tab is gone. Translate tab is there, and the English version is still Published. So that's good. Now if I click "Add" next to a language, I get a node form, with English selected and not changeable. All the fields are also empty. Also not so useful. Lastly, if I go to the node edit page directly, I see my user profile page instead of the node form. The page I see could be specific to my setup, but not getting the edit form is not so good. So this dev version is pretty broken imo, and for now I'll just edit the db directly to fix the unpublished English translation.

*update*: After experiencing that weirdness, I reverted the module back to alpha2 and things worked properly as before. The English node was still published, so that was good, but if I repeat the steps with another node, it will be unpublished.

We have the same issue with alpha2.
But -dev seems broken. No page delivery anymore, watchdog contains tons of "PHP undefined index" from entity_translation module...
Don't know the exact source of the issues, but it's dead.

Hope -dev will be stable soon...

@miro_dietiker:

It's pretty weird what you are reporting, dev should be pretty stable right now. In fact there will be a beta out soon, based on it. Maybe one of the latest commits broke something? Can you track the origin of the errors?

Also, why has this been marked fixed?

Accidentally switched..

Rechecked with -dev. Same situation here.
Also i ran into an issue that system is fully broken. The menu alter clearly has a weight problem it seems.

Still published doesn't switch with publishing the main (entity translation enabled node) entity when a translation is already there.
The node (source english) switches to published while the translation record (of the source language) is still unpublished.

Tried it with a fresh install. Same problem.
New drupal, dl entity entity_translation-7.x-1.x-dev
New content type "test" with entity translation and body translateable.
Unpublished new content - add translation, published - edit main node, publish node
Result: translation of source language in translate tab still is in unpublished state.

EDIT: My previous reported unstability seems in addition to be this: #1818440: Fatal error with unclean edit path

Well, if I understand this issue correctly, you are saying that the excepted behavior is that the main translation publication status and the node status should be tied, so that if I switch the publication status of a node the status of the translation corresponding to the entity language switches accordingly, right?

Originally this was a feature: I might want to publish a translation in a language differing from the original one and leave the original unpublished. However I agree that this is a minor use case and we might want to drop support for it if it is causing so much trouble here.

What do you think?

Oh wow...
I (and 2 others) didn't realize that you can separately enable publishing of a translation for the source language... We didn't see the vertical tab "Translation" or didn't expect to have a separated "translation" publishing state there (corresponding to a/the translation record).

Might be a misunderstanding... At least a major usability issue (I just didn't expect any information from the translation tab to be merged into the source...). Let me think about this.

Hmm... no
In the latest version of entity_translation, the vertical tab "Translation" in the source node is available but always greyed out (disabled).
It even seems the checkbox is always checked and disabled, independently if the translation record is not published.

So publishing the translation of a source that was previously unpublished is impossible with UI now.

I'd have to check again but the logic originally implemented was that at least one translation has to be published if the node is published. Not necessarily the one related to the original language. If things are grayed out probably you have only one translation published.

The node itself represents the original "translation" (source language). so greying out is nonsense.
If i want to publish it as/with the first language, i need being able to do so.

Also it's always grey in my case... :-)

So if the edit represents the original / source language, it should also just have an unconditional translation published checkbox as a start.
When creating new things i only ask myself if the translation published checkbox should (by default value when creating a new node) represent the published default state of the node. Alternatively just set it to TRUE by default.

Having the original translation as being "published" is also fine if the node is not published yet.

I see no reason for that disabled state then. Even i would add a warning message if i publish a node and the source translation is not published yet.
Should i provide a patch for that?

Ok, I tried to test this more thoroughly and I think now I grasp what's the UX issue:

1. Create an English unpublished node > The "original" translation has unpublished status
2. Create an Italian translation > The new translation has published status and this cannot be changed since at least one translation must be published
3. Publish the node > You get the node published only in Italian, while you probably wanted both translations published

Following the suggestions in #25, the attached patch implements these changes:

• when there is no translation the "original" translation is always published instead of following node status;
• when creating a translation its status is published by default but can be switched (is not greyed out).

This means that in the scenario above both translations are published when you publish the whole node. You can still decide to unpublish the English translation but you can do that only if the Italian translation is published.

This seems a good fix anyway so I went ahead and committed it.
Please let us know if this can be called fixed.

Quoting @miro_dietiker from #1818440: Fatal error with unclean edit path (wrong issue):

Much much better!
(But not perfect yet ;-) )

In addition i think for consistency, we should set the translation status to TRUE for all new nodes. not query for the node status.

Inconsistency example:
Compare case A
Create a node, unpublished
=> status of first translation is UNPUBLISHED
publish the node
=> status of first translation is PUBLISHED
unpublish the node
=> status of first translation is PUBLISHED

If we make the first translation record implicit, we rely on the node "published" state and we rely on the default (source) language.
I thus suggest to make this published as the source language is the initial reference.

The rest seems fine, test coverage is insufficient. Tests pass still without any change. :-)

And reuploading the patch.

Makes sense.

Committed and pushed, thanks!

The rest seems fine, test coverage is insufficient. Tests pass still without any change. :-)

Our test coverage currently sucks, although thanks to @bforchhammer is improving. We have an issue for this which will probably become a meta issue at some point: #1770750: Improve test coverage.

Meanwhile I'm tagging all the issues I'd like to see test-covered:

http://drupal.org/project/issues/search/entity_translation?issue_tags=Ne...

Cool! Thank you.
No idea why i ended up in the wrong issue... *doh* :-)

Tested and -dev now works cleanly.