Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Create a node with source language = 'french'
save it, translate it and publish.
This node will not be visible in the /admin/dashboard/deployment/deploy
nor will it be visible in the /admin/content
the workaround is to delete the content and re-create it as english as the source language.
We need to prevent this from happening, or else allow these nodes to be used.
Comments
Comment #2
sylus CreditAttribution: sylus commentedThis is likely just a view setting that needs to be adjusted? Is all you are saying that you created a node in french first without an english?
Comment #3
joseph.olstadya the node was created in french , THEN translated to english
the /admin/content view doesn't show the node
nor does the /admin/dashboard/deployment/deploy view
also, we had problems deploying in french so we made a rewrite rule for the admin/dashboard/deployment/deploy path to always go to english but I think that's a seperate bug
/fr/admin/content does not show the node with french source language
nor does /en/admin/content
only the nodes that were created with English as a source language show up.
I looked at the views and didn't see where this would be changed. it might be a bug in a contrib module causing this, or maybe a bug in views.
Comment #4
sylus CreditAttribution: sylus commentedThis works for me, perhaps when you made your french node you didn't hit the translate button and hit add? This adds the entity translation linkage.
Reproduction Steps:
1) go to: node/add/wetkit-page
2) Title: Title FR
Body: Body FR
Language: French
3) Save
4) Hit Translate Tab
5) Select add link next to english section
6) French Values will initially be added to English Side of Screen
7) Change Title: Title EN
Body: Body EN
Language: english
8) Save
Everything works and appears in both screens. My guess is you didn't select the translate tab and just saved the nodes in english and french without that step.
Comment #5
joseph.olstadok, let me retest
Comment #6
joseph.olstadOk, to repeat this do steps as documented above AND:
create a whole bunch of new revisions (say 5 or 6) and publish
revert to one of the new revisions you created, create a few more revisions and publish
then delete ALL previous revisions until only the current revision is shown.
NOW visit /admin/content and /admin/dashboard/deployment/deploy
the node is not seen in those views. Not sure if this is a workbench moderation issue, but it occurs on the OLD workbench moderation distro dev version november 26 AND the new distro dec13 with the new workbench moderation.
Comment #7
sylus CreditAttribution: sylus commentedHow are you deleting those old revisions? This is starting to look like an edge case that might make more sense in workbench moderation queue. Depends on how u r deleting the revisions.
Comment #8
joseph.olstadWe're deleting the revisions using the moderate tab in node/edit
Agreed, if we can confirm that this is a workbench moderation issue then we should move this to the workbench moderation queue.
Comment #9
joseph.olstadnode/36/moderation , using the delete link from this page
Comment #10
joseph.olstadat this point I'M not 100% sure if the source language or translation of the node has anything to do with it. More testing would be needed to isolate the issue.
Comment #11
sylus CreditAttribution: sylus commentedComment #12
joseph.olstadthis bug is also affecting the following use-case:
create a node
translate it
publish it
edit draft
publish it
create another draft
save
now in the moderate tab, delete this draft
The content now disappears from /admin/content and /admin/dashboard/deployment
Comment #13
sylus CreditAttribution: sylus commentedIs there an associated workbench moderation issue for this so can be tracked?
Comment #14
sylus CreditAttribution: sylus commentedI have track this issue and there is a fix / hack over at this issue:
#2734295: entity_translation_field_attach_delete_revision() ends up deleting current entity's record from {entity_translation}table
Am going to let that issue sit for a few days but will commit to distro after get validation won't introduce any regressions.
Not fond of the fix but definitely fixes the problem.