Installation and deployment
Version 3.x > Installation and deployment > Default visitor culture View modes: 
User avatar
Member
Member
sahuspilwal1981-hotmail - 10/1/2008 10:37:47 AM
   
Default visitor culture
Since importing my site into a production environment all my pages within the site including the root document state the following message in the CMS Desk:

New Culture Version (sq -AL)
The document does not exist in current culture. You can create a new culture version of the document.

If I go into the Site Manager > Edit Site > General tab
The Default visitor culture is set to automatic but in the drop down menu it has the Albanian - Albania setting displayed, why is this appearing in here even though the global and site settings for culture are set to "en-US". I want to get rid of this in case the clients cookies attempt to display the site using this culture. Checking the web.config settings in ASP.NET I could see the application settings taking this setting. Having changed it back to en-US it still remains sq-AL in the CMS Desk. Any feedback would be much appreciated, as i'm worried it will cause problems down the line.

Kind regards,

Sahus Pilwal

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 10/2/2008 4:12:43 AM
   
RE:Default visitor culture
Hi Sahus,

could you please tell me which type of license do you use in a production environment and which one have you used to develop the site?

Could you please check which cultures are in CMSSiteManager -> Sites -> edit your site -> Cultures?

It is possible you have a license on your production server that does not support multiple languages, whereas the develop server allows this.

If you have allowed all cultures on your develop site and then import this site to production server (where the multiple languages are restricted) it takes the first culture of the list from the export and use this one in your site.

The result is to export once again with allowed only one culture (in CMSSiteManager -> Sites -> edit your site -> Cultures), or ask the support at support@kentico.com to send a few days Enterprise license on your production server and with the help of this deny all cultures except for the one you use, or upgrade to Enterprise license, which supports multiple languages.

Best regards,
Helena Grulichova

User avatar
Member
Member
sahuspilwal1981-hotmail - 10/2/2008 4:24:53 AM
   
RE:Default visitor culture
Hi Helena,

Thanks for the feedback it is much appreciated.

I'm running the free edition v3.1a on IIS 6 WIN 2003 Server SP1 using own website, this is my production server!

I've checked the CMSSiteManager -> Sites -> edit your site -> Cultures and I get the following message due to using the free edition:

The requested feature is not available in the CMS edition you are using: Free

Should I run the export tool again from development environment and choose only to export the en-GB culture object?

Kind regards,

Sahus Pilwal

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 10/2/2008 4:36:14 AM
   
RE:Default visitor culture
Hi Sahus,

You could choose only one culture in CMSSiteManager -> Sites -> edit your site -> Cultures on your develop server (only one checkbox will be checked). Then you could export the site by a standard way (no special settings).

The import should work correctly after this.

Best regards,
Helena Grulichova

User avatar
Member
Member
sahuspilwal1981-hotmail - 10/2/2008 8:44:42 AM
   
RE:Default visitor culture
Hi Helena,

I re-ran the export and created a new site on production server which ran me through the site setup again i.e. choosing database using existing site etc. I only imported one language object culture being en-gb and now the site seems to be behaving slightly better. I still get the issue with all the web page documents in the CMS desk being of different culture if I login from an external network. However accessing the CMS Desk within the production network the CMS desk works fine without any problems. I've tested the site from various sites and network locations and the issue with the default page sometimes displaying no site content seems resolved. For now it's working and I will manage the site from within the network ONLY. Though if you have any idea why this would behave differently from outside the network I would be interested to know your uptake.

It seems somehow the default site visitor culture is causing the problem even though now I only have en-gb has an option. Strange.....! I also attempted to choose a language on the login page to the CMSdesk but that did not help.

Again as always thanks for your help.

All the best,

Sahus Pilwal

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 10/2/2008 9:55:56 AM
   
RE:Default visitor culture
Hi Sahus,

I am sorry, I do not understand, why you created a new site.

If you follow these instructions, you should have no problems:

(There are two environments – source site with multiple languages (let is call SS) and target site with Free license (TS).

1. SS: There is only one checked checkbox near the culture in which you created the content in CMSSiteManager -> Sites -> edit your site -> Cultures.
2. SS: Export your site. Please follow these instructions: http://devnet.kentico.com/docs/devguide/exporting_a_site.htm
3. TS: Import the export package from previous step. Please follow these instructions: http://devnet.kentico.com/docs/devguide/importing_a_site.htm (you may use the default settings of import tool).

It seems you used a Kentico CMS Web Installer. You do not need to use this tool to import a site, you may manage all sites (including site import, export or creating a new one) within the Site Manager.

Best regards,
Helena Grulichova

User avatar
Member
Member
kevin-kevincraig - 2/4/2009 12:41:47 PM
   
RE:Default visitor culture
I'm having this problem as well. Every time the application restarts/recompiles in production, the default visitor culture is set to a new language. My license is the free one.

So, right now, I've got the site culture set to US English, but, today, the only visitor culture available is Arabic. Yesterday, the only culture available to me as Spanish. It's annoying, because I need to keep making changes to the web.config to force a recompile in prod until the thing picks English as the one and only culture it will allow visitors to use.

User avatar
Member
Member
sahuspilwal1981-hotmail - 2/5/2009 6:48:45 AM
   
RE:Default visitor culture
Hi Kevin,

I still have this issue but it only seems to effect the CMSDesk and site manager area. Once logged in and I move between sections of the backoffice area all seems to be OKAY. The production part of the site is fine.

Are your eventlogs showing that the web application is restarting every 20 minutes? Do you find that your landing page for the production site is slow by any chance. Please see another post of mine relating to this called "Landing page download speeds".

All the best,

Sahus


User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 2/6/2009 6:10:41 AM
   
RE:Default visitor culture
Hi Sahus,

Could you please tell us more details about "I still have this issue but it only seems to effect the CMSDesk and site manager area."? Where are the problems? If you are unsigned?

Best regards,
Helena Grulichova

User avatar
Kentico Developer
Kentico Developer
kentico_helenag - 2/6/2009 6:04:33 AM
   
RE:Default visitor culture
Hello,

could you please tell us more details? Did you import the site on the production server? Had the original site more than 1 cultures?

Best regards,
Helena Grulichova

User avatar
Member
Member
Obfuskater - 3/11/2009 4:41:31 PM
   
RE:Default visitor culture
I found a similar thread here:

http://devnet.kentico.com/Forums/f18/fp8/t6571/The-document-does-not-exist-in-current-culture----.aspx

It seems there is a bug in the export module which relates to the cultures.