{"action":"created","issue":{"url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/161","repository_url":"https://api.github.com/repos/OrchardCMS/Orchard2","labels_url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/161/labels{/name}","comments_url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/161/comments","events_url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/161/events","html_url":"https://github.com/OrchardCMS/Orchard2/issues/161","id":153280256,"number":161,"title":"Taxonomies & Localization","user":{"login":"urbanit","id":1871551,"avatar_url":"https://avatars.githubusercontent.com/u/1871551?v=3","gravatar_id":"","url":"https://api.github.com/users/urbanit","html_url":"https://github.com/urbanit","followers_url":"https://api.github.com/users/urbanit/followers","following_url":"https://api.github.com/users/urbanit/following{/other_user}","gists_url":"https://api.github.com/users/urbanit/gists{/gist_id}","starred_url":"https://api.github.com/users/urbanit/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/urbanit/subscriptions","organizations_url":"https://api.github.com/users/urbanit/orgs","repos_url":"https://api.github.com/users/urbanit/repos","events_url":"https://api.github.com/users/urbanit/events{/privacy}","received_events_url":"https://api.github.com/users/urbanit/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2016-05-05T17:25:25Z","updated_at":"2016-07-30T09:26:05Z","closed_at":null,"body":"The problems with localization we face with Orchard (and tried to solve with this module [https://github.com/urbanit/OrchardCMS.Localization-Extensions](https://github.com/urbanit/OrchardCMS.Localization-Extensions) ) are:\r\n\r\n**Taxonomies with Localization Part**\r\n1. Create a taxonomy --> Category_En\r\n2. Add translation --> Category_Gr\r\n3. Add a term in Category_En --> Term_En\r\n4. Add a translation --> Term_Gr\r\nOops... without the module, Term_Gr is created, but not under Category_Gr and misses its parent... Lost\r\n\r\n**Content Items  with Localization Part and Taxonomies**\r\n1. Add Localization Part and Category Taxonomy (both Category_En and Category_Gr? - this is how it works now with module)\r\n2. Create a new Content Item - no language is selected yet.... As for now, no taxonomy is shown... \r\n3. Select Language and save... The appropriate taxonomy appears.... And now you can choose your terms...\r\n\r\nI will update this post with how Drupal is working -- not ideally though..."},"comment":{"url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/comments/236355464","html_url":"https://github.com/OrchardCMS/Orchard2/issues/161#issuecomment-236355464","issue_url":"https://api.github.com/repos/OrchardCMS/Orchard2/issues/161","id":236355464,"user":{"login":"jersiovic","id":4950766,"avatar_url":"https://avatars.githubusercontent.com/u/4950766?v=3","gravatar_id":"","url":"https://api.github.com/users/jersiovic","html_url":"https://github.com/jersiovic","followers_url":"https://api.github.com/users/jersiovic/followers","following_url":"https://api.github.com/users/jersiovic/following{/other_user}","gists_url":"https://api.github.com/users/jersiovic/gists{/gist_id}","starred_url":"https://api.github.com/users/jersiovic/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jersiovic/subscriptions","organizations_url":"https://api.github.com/users/jersiovic/orgs","repos_url":"https://api.github.com/users/jersiovic/repos","events_url":"https://api.github.com/users/jersiovic/events{/privacy}","received_events_url":"https://api.github.com/users/jersiovic/received_events","type":"User","site_admin":false},"created_at":"2016-07-30T09:26:05Z","updated_at":"2016-07-30T09:26:05Z","body":"I see. \r\nA question: do we will have a weight for each localized term or it will be only in the master term?\r\nIf there is a weight per term when you change it through UI, through recipes or programmatically using taxonomy service, will it be synchronized in localized versions too or will it has to be changed explicitly for each localized version? \r\nFor flexibility reasons I see better they are not synchornized but for making easy the most common scenario I would prefer they are synchronized. So, a midpoint could be make it configurable at taxonomy level.\r\nIf it will be synchronized, the desirable will be that no matter if you change the master term or a synchronized versions all of them they will be updated. \r\n\r\nRelated with query projections: the taxonomy field filter for query projections would be interesting that also look up for localized versions of the term set by the user in the filter or offer a check 'Filter also by localized versions of these terms'  to leave this decision to the user. \r\n\r\nIn taxonomy services it would be useful for maintaining localization logic just in one place an extra argument for the same purpose in methods like GetContentItems, GetContentItemsCount or GetContentItemsQuery. \r\nFurthermore, for other methods like GetTermsForContentItem, GetParents or GetChildrenan an extra parameter setting the culture in which you want the resulting terms will be useful to help consumer the culture of those methods to be ignorant of the culture used bye the which a user selected a term in a taxonomy as input to a page."}}
{"actor":{"display_login":"jersiovic"}}