Here is an issue we are having with our website developed in XPages which is accessible in several regions and languages. Based on the browser language we are able to determine which header to display at the top of web page. Our content is then displayed for that language in that region. Content displayed is from individual documents in a Domino database and there is one for each language so the user can see language friendly data. Some documents are only for a particular Region/Language and not translated for other regions due to availability of the product.
The issue is when someone clicks on a link (ie via social media let's say) like https://www.cascorp.com/americas/en/reach-forks they go to the americas English version but the header and menu items are displayed in the browser language and content is displayed in the English language. Server Redirect rules won't work in this case. It would be nice to be able to redirect them to https://www.cascorp.com/eme/en/reach-forks and have a page that comes up stating that the product is not available for that region. Is there a way I can dynamically change the address bar to redirect them to a different document by replacing the region part of the address? This way we can have a document for that region/language stating that the product is not available in their region.
You can use context.redirectToPage(nameOfXpage) to redirect based on your language logic.
For a partner of mine, www.the-academy.nl, we decided to abandon Server Redirect rules completely, so we installed Apache as a reverse proxy server. It gives you full control over all links in and out if you want, and we managed to remove all visible references to the web database. Apache can be installed on the same system as Domino (easiest on Linux). It might be a bumpy ride, but it's worth it.
Related
Based on the document:
When you open the Pages application on a multilingual website, you can see the language selector below the content tree. Use the selector to switch between language versions of the currently selected page.
But my language selector is missing!!!!
I am using Kentico v10.0.11 with Based license edition.
I have set UK and US in my website.
What else did I miss?
Can you double check you have assigned cultures for your current site?
As far as I know localization should be accessible in the base license so this should not be an issue.
If everything is set properly and it`s still not working you could check event log and browser console.
I have set up a new role in my Sitecore 8 (update 3) instance and have assigned the following roles to it (as well as giving read/write access to my content tree):
sitecore\Sitecore Client Translating
sitecore\Sitecore Client Users
sitecore\Sitecore Client Authoring
sitecore\Sitecore Client Designing
When logged in and using the Content Editor, I can change language ok. When I change language in the Page Editor Experience Editor however, (using Experience > Language menu item) I get a 404 error. If I clear the URL in the browser to the root (hostname) the language appears to have been changed.
Edit: Additional Information
It's worth noting that:
The solution does not use translated items. We have a separate content tree (within a single instance) for each site/language.
The linkManager is configured to use DisplayName for the URL.
Please share the snapshot of your new content tree structure and link manager config settings if possible. Meanwhile, can you please revert link manager settings and check if it works fine? Also use firebug net tab with persist to see the URLs requested while click on second language.
Also, please check following cookies values if updated your-site-name#lang:-
website#lang
here webiste is name of default sitecore site
Moreover, when your Experience Editor is loaded, just to make sure, click on default language from language menu to see if it works even for default language.
As said keep your firebug open with persist and keep eye on net tab with all to see if any resource request having 404.
The default behaviour of t3solr is to hide results with access restrictions if the currently logged in user does not have the rights to see this page (or is not logged in at all).
Our customer wants a different behaviour: the results shall be displayed, but be visually highlighted (by adding a css class, for instance). The (not yet logged in) user can "preview" an abstract of the desired content in the search result excerpt (to tease him) and click the link. He will then be presented the login page and redirected to his target page after login (last part is already default typo3 behaviour).
Does anyone know whether this is possible with the current t3solr? I think it was possible with indexed_search when I last used it some years ago, so I thought t3solr may support this as well.
And no, I have not "just" tried it out yet as setting up the whole stuff takes longer than asking here before. Also, I'm not sure whether I have to pay for the early access version of the t3solr to get this (possible) feature.
Both versions of the TYPO3 extension Apache Solr are identical regarding the access rights to pages and content elements.
The requirements you are stating are not going to work out of the box as we designed the extension to be very strict on displaying only results that you are allowed to see.
There is certainly a way to circumvent the behaviour that would require a change in the solr access filter that we have in the extension. Or by assigning access rights on content level and and having a plugin displaying a teasing part only.
We generally monitor questions about solr for TYPO3 here:
news://lists.typo3.org:119/typo3.projects.solr
There is an existing app in MOSS, which allows to create polls for a call center, operators fill them out as they call targeted customers. Then this Web app outputs the results of this poll.
Is it possible to change the interface language of this existing web app? Operators don't understand English. If it's not about language packs, it would still be easier for me to embed new names and labels, rather than rewrite in a system I am not familiar with.
Also, is it possible to change the authentication type from Windows authentication to regular username/password check (username and password will be stored in DB or somewhere only for this site)
If it is possible, can you direct me to some kind of tutorial, help or manual which would show how to do it?
On MSDN it's written that language can't be changed, but I'm not sure whether it's about the Web app language.
Thank you.
Have a look at chapter 4 in our free SharePoint Development Guidelines.
I have no mutch idea about web app language
But I shall share you the links for sql authentication
http://weblog.vb-tech.com/nick/archive/2006/06/14/1617.aspx
http://www.codeproject.com/KB/sharepoint/moss_enableforms.aspx
For SharePoint it is possible to create different web's in different languages. Not that i know you could use one web in different languages.
But, it may be funny or not, a crazy idea or not, but could work: before dumping rendered contents to user, maybe you could extract text values excluding form values, post them to Google or Bing translator and put back translated values? You can override global.asax file and use PreSendRequestContent to modify contents just before they are sent to client.
If your company is not huge and it's an intranet page, then, althought slower, but it could work. Better than nothing.
PreSendRequestContent. This event
signals that content is about to be
sent to the client. This provides an
opportunity to modify the content
before it is sent.
Lets try keep this simple.
Given a SharePoint site (english) and a feature (localized with resource files) to English (default) and Czech (but could be any language).
Why do I need to install a Czech Site Collection to get the Czech localization strings to work. I thought localization worked from user context, IE: based on the currently logged on users regional settings which trickle through to the browser?
A feature is not really meant for "end users", but for site admins to roll out only. So localization files pertaining to the feature itself (i.e. description, title etc.) are shown in the language of the site collection. Any controls and aspx pages etc. you create though could be localized for the display language of the current user's browser, just use the normal ASP.NET way of doing this. To be able to have your site actually listen to the user's language preference you need to change the web.config of the web app also though by setting the globalization to auto like so:
<globalization fileencoding="utf-8" uiCulture="auto" culture="auto" />
Any aspx page needs to have Culture="auto" UICulture="auto" in the <%# Page directive.
Al off the above is an "excerpt" from Hristo Yankov's excellent article.
I believe a feature LCID will be related to the RootWeb.Locale.LCID of the Site Collection.
That said, you probably need to code your own logic to grab culture info and display your respective resource file.