Best to set the language at the rootnode of your site. Right click on the node select Manage Hostnames, the domain name doesn;t have to be a real domain so you can simply say UK and select the Uk Language. That should work
That sounds really helpful. Unfortunately I think me deleting US from the language options has caused a somewhat catastrohic in the content nodes - every one I click (including the manage hostnames box) now comes up with the following error:
Value cannot be null.<br>Parameter name: value body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Lucida Console";font-size: .9em} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
Value cannot be null. Parameter name: value
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentNullException: Value cannot be null. Parameter name: value
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I went into the table 'umbracolanguage', and added en-US back manually setting the primary key to 1 (which I guessed was the original value) and the site/content tree sprang back into life.
I also implemented Richard's suggestion above and it worked a charm.
I had the same problem, that I got this error, when trying to enter
the Content section. Then I went to the documents as suggested in this
post. I saw, that each document could not enter the masterpages folder.
I added the aspnet user to the security settings. After having done
these settings, there were some errors in my masterpages, solved them
and then I could see my document settings and the Content pages.
Everything works fine.
Hope this will help someone who is facing the same problem.
Changing culture
Hi,
I am formatting strings as currency and the currency symbol is US$, rather than UKĀ£. I did the following to change the culture:
1. Removed US a language under settings --> Languages
2. Changed web.config to include <globalization requestEncoding="UTF-8" responseEncoding="UTF-8" uiCulture="en" culture="en-GB"/>
However it's still formatting as US($). Looking at the debug screen I can see this is being set: 'default.aspx Culture changed to en-US'.
So, my question is how do I set my culture to be en-GB and what have I missed!
Thanks for any help.
JC
Hi,
Best to set the language at the rootnode of your site. Right click on the node select Manage Hostnames, the domain name doesn;t have to be a real domain so you can simply say UK and select the Uk Language. That should work
Hope it helps you,
Richard
Thanks Richard,
That sounds really helpful. Unfortunately I think me deleting US from the language options has caused a somewhat catastrohic in the content nodes - every one I click (including the manage hostnames box) now comes up with the following error:
Value cannot be null.<br>Parameter name: value body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Lucida Console";font-size: .9em} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }
Value cannot be null.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Parameter name: value
Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: value
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
I tried to re-add it but I suspect this is a key contraint that's now broken. Possibly looking like a db rollback.
Thanks
JC
Update!
I went into the table 'umbracolanguage', and added en-US back manually setting the primary key to 1 (which I guessed was the original value) and the site/content tree sprang back into life.
I also implemented Richard's suggestion above and it worked a charm.
Thanks Richard.
JC
Hi there,
I had the same problem, that I got this error, when trying to enter the Content section. Then I went to the documents as suggested in this post. I saw, that each document could not enter the masterpages folder. I added the aspnet user to the security settings. After having done these settings, there were some errors in my masterpages, solved them and then I could see my document settings and the Content pages. Everything works fine.
Hope this will help someone who is facing the same problem.
Best, Martin
is working on a reply...