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.There's already a built-in mechanism to add support for the Node Clone module (see #1205304: Clone the panels display if using node_clone to clone a panelized node).
This patch adds the same support to translated nodes.
Thanks!
| Comment | File | Size | Author |
|---|---|---|---|
| translation-support.patch | 818 bytes | joelstein | |
Comments
Comment #1
merlinofchaos CreditAttribution: merlinofchaos commentedI suspect htis is relevant for Drupal 6 only, and not Drupal 7?
Comment #2
joelstein CreditAttribution: joelstein commentedI can't speak for the D7 version; I only needed it for a D6 site, and the patch above works for D6.
Comment #3
webcultist CreditAttribution: webcultist commentedThis would be really nice for D7!
Comment #4
webcultist CreditAttribution: webcultist commentedchanged to d7
Comment #5
merlinofchaos CreditAttribution: merlinofchaos commented...have you verified this doesn't work on D7? Because the D7 2.x version of Panelizer should clone naturally. Your comment doesn't state that you've done any due diligence prior to actually changing the issue.
Plus, there's a D6 patch here that changing this to D7 disregards. :/
Putting back to D6.
Comment #6
webcultist CreditAttribution: webcultist commentedSorry Merlin,
yes this is working for D7.
I think, what I was looking for was a way for normal translation and without node clone.
I had not enough sleep on that day, I think -.-
I'm really sorry for that!
Comment #7
Letharion CreditAttribution: Letharion commentedComment #8
enekoalonso CreditAttribution: enekoalonso commentedWhat is the status for D7? Is there any way to translate panelized nodes and automatically copy all the panels?
Comment #9
DamienMcKenna@enekoalonso: According to merlinofchaos it should already Just Work™ in D7.
Comment #10
seanrIn my experience, this actually did not work out of the box in D7. When I translate a node with customized panelizer settings (using core's content translation), the translated node ended up with empty panelizer content (or at least default for that content type which happens to be blank in our case).
Comment #11
DamienMcKennaGiven the patch is for D7, it needs to be backported for D6.
Comment #12
DamienMcKennaUnless someone steps up to provide a patch, it's unlikely this will be worked on. If someone is willing to put time into it and build a patch then I'll happily review it.
Comment #13
Kendall Totten CreditAttribution: Kendall Totten commentedI can verify I'm experiencing a similar issue mentioned by seanr in #10, which sounds like he was talking about Drupal 7, as am I.
Custom panes added to the original (English) node via Panelizer show up on the rendered English node. However other languages just inherit the default panelizer settings, regardless of the fact that I have added custom panes to the other language panel as well. http://note.io/19AqzFvhttp://note.io/19ArYM4
It's possible that this issue is related to the workbench module? I do see the revisions listed though, and the latest revision is published so that seems less likely of a culprit.
Comment #14
DamienMcKennaPanelizer doesn't support multiple languages, so there may be problems with caching on D7 sites.
Lets continue this in #2070891: Support core Content Translation by cloning the Panelizer display for the new entity.
Comment #15
DamienMcKennaThe 6.x-1.x branch is no longer supported, so this will not be resolved.