Sitecore doesn't expose the version manager [you've shown] on templates. However, you can use the DB Browser (~/sitecore/admin/dbbrowser.aspx) and manage items, templates, etc. that way. Simply point your browser to http://instance/sitecore/admin/dbbrowser.aspx:
Then navigate to the template you're looking to modify and select the version you're after and ...
Because you want to keep the content in the Master database, but you do not want to publish it to the web database, this may be a good opportunity to use Workflow.
If you're using Workflow on these pages
Here's how to fix your issue:
Establish which Workflow your fr-FR pages are using.
In that Workflow, create a new Workflow state called "Archived&...
You can configure the LinkManager to use Display Name instead of item title when generating URLs.
If the workflows are not drastically different, you can achieve 'site-specific' workflow via content security.
Step 1: Workflow security
Create a single workflow definition with some generic access roles for each state. Use these only to grant access to the workflow states.
Step 2: Content security
Create a security role for each site and assign it to ...
If you don't want FilePath based language resolving, simple do below setting in Sitecore.config:
<setting name="Languages.AlwaysStripLanguage" value="false" />
This will do nothing but ignoring the StripLanguage processor from preprocessRequest pipeline.
By default first item (after domain name), Sitecore checks whether it's a language or not. If it'...
Props to @rosscartwright, @cassidydotdk, and @jammykam for getting us to the answer at lightning speed and for the helpful links.
The issue was a feature of Sitecore called AlwaysStripLanguage that is controlled by a Sitecore Setting in the Language group that controls the activation of a processor in the <preprocessRequest /> pipeline called Sitecore....
Try the following solution:
We need to override Sitecore.Pipelines.PreprocessRequest.StripLanguage
public class StripLanguage : Sitecore.Pipelines.PreprocessRequest....
There's already answer to similar problem on Stack Overflow: https://stackoverflow.com/questions/21452260/sitecore-tree-list-datasource-versionexist
In a nutshell, what you need to do:
Create DataView which will be responsible for filtering non-existing items
LanguageFilteringMasterDataView : MasterDataView
Override method GetChildItems where you can filter ...
I think this is possible with SPE. Something like this should work:
Remove-ItemLanguage -Path master:\content\home -Language "fr-FR" -Recurse
Perform this on a CM server and publish the site to move the changes to the web database and the CD servers.
It's probably also a good idea to rebuild your indexes and link database after doing this.
It might also ...
To deliver content in different languages per domain you need to create two sites in config and use language attribute in site definition. That attribute tells sitecore what language should be used if language is not explicitly defined in request.
targetHostName = "www.x.com" />
I think this is well covered on John West's post which in summary describes what the priority is and how Sitecore handles them:
"The Sitecore layout engine retrieves content from the Sitecore repository in the context language (Sitecore.Context.Language). The default logic to determine the context language is to use the first of these variables that ...
Check that the users' Roles have access to the Languages they are attempting to edit. You can do this by opening the Access Viewer, selecting the role, and navigating to System/Languages. Don't just check the Read and Write settings, it's the Language Read and Language Write settings that control access to Items based on that language. If Language Write is ...
You could loop through items in your tree and restrict publishing using Sitecore PowerShell.
$item = Get-Item master:/sitecore/content/home
$item["__Never publish"] = "1"
Some useful links:
This is possible - when creating a language you don't need to specify the region.
You can pick a language, Sitecore will fill the region but you may clear it:
When doing so, you will end with a language list similar to this:
For future use:
I found a solution for this, we need to enable language fallback for master and web indexes like below, and rebuild them. By default, this setting is set to false
If Cachable attribute equals true, it means that Glass Mapper will apply cache for this object. I've decompiled the Glass.Mapper.Sc.dll, where CacheKeyGenerator is defined and we can see that it doesn't consider the language in the key for cache:
public class CacheKeyGenerator : ICacheKeyGenerator
public string ...
As much as I hate to put this as an answer, but this is not a Sitecore issue.
this doesn't fail: http://sitecoredemo/sitecore/service/notfound.aspx/%20/
neither does http://sitecoredemo/sitecore/service/notfound/%20/
neither does http://sitecoredemo/sitecore/%20/
I have tested this on IIS 7, IIS8, and IIS10. On Sitecore ...
The out of the box links don't specify language at all, so there is no way with an internal item reference to specify a specific language. The link is tied at the item level, not the version. Similarly, you can't directly link to a specific version of the content in the current language.
When invoked, the LinkManager uses the current context language for ...
Although Sitecore has great support for multi-site and multilingual implementation, there is no 'silver bullet' design that works for every situation.
Below I described four options we use for our sites. Hopefully you can use one of them or build your own.
1. Separate Site
I am not sure if there is an easier way to do this. But I've achieved this before by setting a custom language cookie and then set the context language in a HttpRequest pipeline processor based on the value of your custom language cookie.
When you switch language on the website then you can just set the value of your own custom language cookie and then you ...
You are correct that the Translate button is what you are looking for. Since you are not seeing it when logged in with your user with the new role, your new role likely does not have the necessary sitecore/Sitecore Client Translating role that is required in order to see the button.
Try logging in as an administrator and see if the button will ...
You need to follow next steps:
Download Language Registration tool from https://marketplace.sitecore.net/en/Modules/Custom_Language_Registration.aspx
Start the “Language Registration” tool
Change the name to “pt-MX”
Click the “Register” button
Declare a new language in the “\App_Config\LanguageDefinitions.config” file:
<language id="pt" ...
For your request you can use Display name functionality
Display names can include characters not allowed in item names.
Display names can vary by language, where item names cannot.
Because display names can vary by language, and item URLs can contain display names rather than item names, URLs for individual items can vary by language (beyond hostname, ...
Regarding the front-end website, this is unrelated to Sitecore. It can be handled with HTML and CSS.
In Content Editor, Sitecore handles this so you do not need to worry about it. I've worked on Arabic sites and the RTE popup automatically changes to RTL. The preview of RTL show LTR though but that's not a problem, it is still very much readable:
You can ...
You can use URL Rewrite module for your issue :
1) Open the Internet Information Services(IIS) Manager
2) Select “Your Web Site”
3) In the Feature View click “URL Rewrite“
4) In the “Manage Providers” pane on right hand side click on “View Rewrite Maps…” and then select "Add Rewrite Map.."
5)Set the map name, SpaceMap for example
6) In the “...
You can add your own processor to the httpRequestBegin pipeline after the ItemResolver processor. Your processor should generate Sitecore.Content.Item URL and compare it with HttpContext.Current.Request.RawUrl. If new url contains language and RawUrl does not contain, just redirect user to the newly generated url.
Something like this should do the trick (I ...
date.ToLongDateString() executes in the background DateTimeFormat.Format(this, "D", DateTimeFormatInfo.CurrentInfo).
It means that the culture info is taken from the thread or from the server (you may want to double check if it's from both or from one of them only - I'm not sure anymore).
What you could do is passing the chosen culture to the Format method ...
Another way to do this is using Sitecore Powershell Extenstions. There is a cmdlet called Remove-ItemLanguage, this removes the specified language version from the item.
Example that removes the German version of a template:
Get-Item master:\templates\User Defined\MyTemplate | Remove-ItemLanguage -Language de-de
You could create a script that would load ...
In a clean install of Sitecore 8.1 update-3, the templates and their related sections/fields are always created in English, no matter what language the user may be working in from the ribbon:
But if your user/developer has changed their language preference in their profile (Control Panel > Region and language options > Display language) then the ...
I think you will have to make this functionality yourself. You will most likely have to hook into the httpRequestBegin pipeline and also extend and replace the default LinkProvider.
Here's an (untested) example of how this can be approached.
Start by hooking into the httpRequestBegin pipeline and check if the language matches the language setting on the ...