5

There is no GEO Location service built-in with Tridion, but you can integrate with an external, 3rd party service within the web application code. The following question by Alvin (and the answers) may help you: Geolocation options for content delivery. Pankaj gives a couple of examples of 3rd party GEO Location services that you could use in his answer.


5

The most obvious measure is to ensure that only the right people have the Localize permission. As far as I know, you need this also to unlocalize. And of course, only people with write permission would be able to unlocalize. You can't use workflow to manage localization, but you certainly could write an events system that enforced your rules. You would want ...


5

Would you like to check if on the local environment where the things are working have this hot-fix applies - CP_3.1.0.75095 - Cumulative Hotfix. You can get more details about this hotfix HERE Apparently it seems to be a known issue with CP 2009 SP1 and in my case this issue got resolved once I applied the above said hot fix.


4

Why don't you localize it at source and send separate package for translation then import it in the destination after translation? i think that would avoid any risk.


3

Every time you send component for translation: TM get latest version of source component (English) Send all fields of source component including non translatable fields to TMS (except for aggregated components it send only translatable fields) On retrieve TM apply all fields to target components So if you change anything in target item it will be ...


3

It seems to me that you may have a blueprint priority conflict somewhere, or an additional localization of your component. In Tridion 2009 I don't know how to check this easily, in Tridion 2011 and higher you can see the whole blueprint hierarchy for a given component... Can you: Open the page that contains the component in the publication that you're ...


3

I have to assume that the message is not a mistake, as this logic is quite solid. You probably have an old transaction that is still pending. Make sure you set filters in the publishing queue allowing you to see: Transactions by any user instead of current one Transactions of any date instead of the current date By default the publishing queue will only ...


2

As you mentioned, you are facing this issue on the environments where you have limited access. It could be related to security permissions against the user account with which you are running the content porter. Also I can see in logs “Error while reading item”. So it adds to it as well. To Port the localized page, the user(or user group) must have Page, ...


2

"Resolve shared items with BluePrint mapping" is the setting that will let us have the desired results. By default, this option is not checked.


2

With regards to your question of "Could this BluePrintInfo be cached or not realtime info?", the answer is 'No'. If there was a level of caching then this would need to be configured when multiple Content Manager servers are load balanced, and this is not the case. I've just run the following test to verify this also (using the Core Service): Create a new ...


2

I agree with Mark and Rick on this one. I’ve seen many similar projects that start with “Let’s put them in the same Publication - It’s only a few pages”, and end up becoming a major unpicking job later down the line after the scope expands. As well as working against how translations (and Translation Manager) should work within the CMS, you’ll also be ...


2

There is nothing built-in to be able to report on this. Once you unlocalise the item, all details on the localsed version are lost. Depending on your logging level, this information could be written out to the Content Manager logs. However, it would not be a nice job sifting through them, and you'd have to retain all of the log files to get an accurate ...


1

I agree that using metadata on each (presumably, localised) keyword and then filtering these out with your C# TBB would be a reasonably elegant and maintainable solution. Alternatively (and depending on your requirements!), you could also use a naming convention on the keyword value (e.g. Prefix the keyword's Value field with something like "HIDE - "), but ...


1

Not using BluePrinting for languages is definitely not going the right way. For example, you won’t be able to use Translation Manager to do translation.


1

Question: Will field be updated after translation in Spanish component (after "re-translation" of already translated component) My Answer: Spanish (translated and localized) component and you can send to translation for second time from Spanish publication. Question: Will field be updated after translation in Spanish component (will it get values from ...


1

I'd come at this question from a slightly different angle, particularly regarding situations like this... A major catch is code that relies on Content Manager-side paths (e.g. referencing a template by name) ... and suggest that you shouldn't need naming conventions for these things. In fact, I'd go as far as to expressly avoid it as to me, this screams ...


1

In case of Structure Groups and Folder Structures, there are different ways to do that, and no one is better than other, just depends on what fits into the Users preferences Case 1: Localize and Translate directly the Folder or SG Name 001 Home --> 001 Casa Case 2: Localize and add translation but still keep the original name in English 001 Home --...


1

Did you ever see any localised content within your 'X' website? Could it be that you are using SDL Tridion Content Delivery (or a Content Delivery framework like DD4T) and you are still referencing content from your 'master' publication? It's easy to make this mistake if you're copying the application from your master to a number of child websites. This ...


Only top voted, non community-wiki answers of a minimum length are eligible