I have 2 different languages in the website, and would like to make the Chinese language as a default home page
how do i do that ?i am using Joomla 2.5
I supose you already install chinese and setup it in the admin language manager. I think you need to create a new menu Home in Chinese and setup like default.
Anyways joomla all the time will show the page in the main language setup in the browser.
Another way: go to Language Admin and choose the chinese language like default.
Related
Our Sitecore DB items had many of their display names changed to Japanese for no apparent reason. We thought that we might have accidentally changed the Sitecore language in the content editor, but I can confirm that it is in fact English. This seems to only be happening in the core DB. Has anyone had something similar happen?
Here is an example of the display name changing:
Here is a confirmation that we are set to English:
We're on Sitecore 7.5
There a 2 languages in the Sitecore CMS, the Content Language en the Client Language.
It looks like you change the Client Language to ja-JP. You can set the Client Language for each user in the User Manager, and a default in the web.config
<!-- CLIENT LANGUAGE
Specifies the default language of the Sitecore client if no language
could be determined in any other way.
-->
<setting name="ClientLanguage" value="en"/>
Another point there is a \App_Config\Include\ja-JP.config.example file. maybe you have rename it to .config?
And there is a installed Japanese (ja-JP): Client Translations
I have been looking for documentation and information as to how to translate web site content?
We've been using Django CMS for a long time and it gives us two tabs in the admin, i.e : English, Francais and we can toggle between the two to write content in the specific language.
In Mezzanine, I have my LANGUAGES tuple set up with en,fr as well as USE_I18N = True but I don't see how my content editors will be able to create bilingual pages. Any advice?
Mezzanine doesn't support multiple languages by default as Django-CMS does. You need to use 3th party app that can translate models which code you can't touch like django-modeltranslation.
There is an open issue for Mezzanine about Multilanguage support https://github.com/stephenmcd/mezzanine/issues/106
I was created two multilingual sites with my custom app https://github.com/vstoykov/django-magic-translation
In the Sitecore sites I'm working on (6.5 and 6.6), I've noticed that all the sites have a page at /si that is the same as the home page, but with the content missing/hidden.
Does anyone else have a website with this page? Does anyone know what it is for?
This is Chinese version of the home page. The content is missing as there are no Chinese language specific fields filled with data, but the page itself may come from Standard values.
Most probably your LinkManager in Sitecore.config has the value of languageEmbedding property set to asNeeded or always.
Switching to never would solve this issue (as long as you're not using multilanguage versions of you pages and you need language in the url).
Here are some posts which gives some more input about LinkManager:
Patching the Linkmanager
Sitecore Language Embedding multiple sites
This is expected Sitecore behavior.
You can find the same "pages" with "it", "dk", "de", "se" and so on.
In the httpRequestBegin pipeline found in web.config you can see that Sitecore language resolver is kicking in before the item resolver does. Hence Sitecore interprets the request as a request for the home page in another language layer and any two-letter ISO code for language will return the home page in that specified language context.
You could implement your own processor before the language resolver if you want to handle requests for specific language codes in certain ways.
I have a bit of a weird bug on a website I'm working on. I have multiple themes configured in the Forms Folders in Web Forms For Marketers. No matter what theme or color I select, all of my forms use the theme and color selected for the Website folder. I tested this with a clean install and it worked fine, this is a bug on my specific website.
Here's what I'm working with:
CMS 6.5.0 rev. 120427
DMS 2.0.1 rev.120427
Web Forms for Marketers-2.3.0 rev. 120216
Any ideas?
This is by design. From Sitecore Support, when I raised the same issue a while back:
Edited by Alexander Yaremenko on Thursday, November 18, 2010 at 2:10
PM
Hi Mark,
This is expected behavior. The Theme and Color defined for all forms
for the current site. If you run site (For example Site1) all web
forms will have themes from forms folder that defined in formsRoot
attribute for current site instead of theme from forms folder that
stored this form.
I have registered a wish that we can change this behavior in future.
I can't find the easier way to change this behavior now. I see only
one workaround: Create you custom control which will be insert link to
needed .css on the page. Note: the link to your .css should be defined
below then standard .css.
The Sitecore Support case reference is 336904.
In essence, WFFM assumes themes to be "per site", not multiple themes in the same site.
New to django...
I have a site with structure /[flavor]/[page] where there are many different flavors and each flavor has roughly the same set of pages. At least at a simple level, this seems to work fine as a django app - flavor can easily become an input to the template for a page.
Now I'm trying to integrate some cms mojo so someone non-technical can easily add/modify content or pages per flavor, and it's not clear how/if django-cms supports this. As far as I can tell, what I want seems similar or equivalent to how django-cms handles languages - in the admin there's a separate tab for each language where you can specify content per language.
For now, my site is English only, so I suppose one option (that doesn't seem too attractive or permanent) is to handle the flavors by pretending they're languages.
I know I can host an arbitrary django app on a cms page that could handle the flavor portion, but the hosted apps don't seem to support adding cms page within them in the same way that languages do.
Being new to django, I'm not wedded to a particular cms, and am open to any suggestions about approach, site structure, etc. as well - the main requirement is to support someone non-technical easily adding/modifying different content/pages for the different flavors.
Thanks!
One option would be to bypass the CMS for the flavor pages and create a Flavor model instead. You could use django-tinymce's HTMLField (https://github.com/aljosa/django-tinymce/blob/master/docs/usage.rst) to allow rich text editing on Flavor fields.