that enables me to see from the backend the relatations between pages.
i'm using your razor script in order to create the nodes on publish.
there is one problem - your script creates the nodes in all the languages trees, but it relate the node only to the english tree.
for example: i create about page in english tree and publish. i get the about page created in all the trees: spanish, german etc.
but if i go to the spanish tree for example, i can see that the about page is related only to the english tree and not also to german, france etc.
the expected behaviour will be that on publish the node will be created and will be related to all the languages, so when i go to the same node in all the languages, i will see that it related to all the other languages.
do you know how to achive that? do you think its a bug or its a new feature that will be relevant to other people?
You can infer the relation to the other languages by going through the "master language", that's exactly what this package does. So you can navigate from spanish to german without having to have a specific relation between both.
The extra relations would be overkill in my opinion and complicate stuff. This is also recommended design by the umbraco HQ...
Is there a specific case you're trying to achieve?
damn, i wrote long comment and it deleted... anyway my scenraio that i want to relate specific page to all the other languages, so when i switch from "About" in english it will take me to to the "ABout" in spanish, and when i switch from there it will take me to "About" in german etc..
today, its working from English to other language, but it stops there. i thought it because there is only a relation between english to german for example, but not from german to spanish. am i make myself clear?..
as i understand from you, it suppose to work properly this way? because the English is the "master" anb act like a "bridge" between all the languages?
if yes, there is 2 options: there is a bug, or maybe i customize your package and created a bug..
please tell me, and please explain to me the "master" language concept if you can.
yes it should already work as you describe, using English as "the bridge". You can see this working for instance on this page: http://www.cease-therapy.com/about-autism
Suppose you found a bug or something is being messed up in the relationsships... The code is included so can you debug it?
i think i found the problem - its not with your code, its because of me: instead of using your razor macro (that relate and copy on publish), i choose to use the Vivioz package and add the relations manually. it was huge mistake - it seems that this package dont make the relations as i expected. i had a reason to do that, but its not important now. what important now, it how i'm getting out from this mess, becaus my client is very stressed.
when i enabled your macro, it worked as expected - when i publish a node it the top language tree (English), it created a copy in all the other language trees and relate it correctly to the original node.
the biggest problem now, is that i'm stuck with 50+ pages * 8 languages.. :-( and the worst part that i dont know how to relate them now - if it was new site it wasnt a problem, but now each tree contains nodes with different content.
do you have an idea how to make similar relations to what your macro does, but on existing published nodes?
Copy Document ToRelated On Publish
Hi,
i'm using your nice package with a multi language site (8 languages).
also, 'm using this great package http://our.umbraco.org/projects/backoffice-extensions/viziozrelationships
that enables me to see from the backend the relatations between pages.
i'm using your razor script in order to create the nodes on publish.
there is one problem - your script creates the nodes in all the languages trees, but it relate the node only to the english tree.
for example: i create about page in english tree and publish. i get the about page created in all the trees: spanish, german etc.
but if i go to the spanish tree for example, i can see that the about page is related only to the english tree and not also to german, france etc.
the expected behaviour will be that on publish the node will be created and will be related to all the languages, so when i go to the same node in all the languages, i will see that it related to all the other languages.
do you know how to achive that? do you think its a bug or its a new feature that will be relevant to other people?
Thanks.
Hi Eran,
You can infer the relation to the other languages by going through the "master language", that's exactly what this package does. So you can navigate from spanish to german without having to have a specific relation between both.
The extra relations would be overkill in my opinion and complicate stuff. This is also recommended design by the umbraco HQ...
Is there a specific case you're trying to achieve?
damn, i wrote long comment and it deleted... anyway my scenraio that i want to relate specific page to all the other languages, so when i switch from "About" in english it will take me to to the "ABout" in spanish, and when i switch from there it will take me to "About" in german etc..
today, its working from English to other language, but it stops there. i thought it because there is only a relation between english to german for example, but not from german to spanish. am i make myself clear?..
as i understand from you, it suppose to work properly this way? because the English is the "master" anb act like a "bridge" between all the languages?
if yes, there is 2 options: there is a bug, or maybe i customize your package and created a bug..
please tell me, and please explain to me the "master" language concept if you can.
Thanks a lot.
yes it should already work as you describe, using English as "the bridge". You can see this working for instance on this page: http://www.cease-therapy.com/about-autism
Suppose you found a bug or something is being messed up in the relationsships... The code is included so can you debug it?
Hi Yannick,
i think i found the problem - its not with your code, its because of me: instead of using your razor macro (that relate and copy on publish), i choose to use the Vivioz package and add the relations manually. it was huge mistake - it seems that this package dont make the relations as i expected. i had a reason to do that, but its not important now. what important now, it how i'm getting out from this mess, becaus my client is very stressed.
when i enabled your macro, it worked as expected - when i publish a node it the top language tree (English), it created a copy in all the other language trees and relate it correctly to the original node.
the biggest problem now, is that i'm stuck with 50+ pages * 8 languages.. :-( and the worst part that i dont know how to relate them now - if it was new site it wasnt a problem, but now each tree contains nodes with different content.
do you have an idea how to make similar relations to what your macro does, but on existing published nodes?
any help or idea will be valuable!...
and again, Thanks.
Eran.
Hmm I've no experience with creating relations afterwards. Maybe this package may help you:
http://ucomponents.codeplex.com/wikipage?title=MultiPickerRelations
Hi,
i will check for it. but can you please explain me the concept behind the "master" language?
if i publish node in english, your code is copy it and do the relations to the other languages, for example spanish and german.
i dont really understand how the spanish and german connected using the english as a bridge.
thanks.
i still have few problems and i cant find a good way to edit existing relationships.
i will update this post if i will find one.
Thanks!
is working on a reply...