Cherry Bytes

I recently realised that regardless of what language you have set your locale or settings to in your SharePoint instance that the spellchecker dictionary ALWAYS defaults to US English – however a client of mine wanted to use the Australian English as their site was hosted and used primarily by Australians!

I thought this was going to be an easy configuration change, however in the end this required a bit of javascript injected into the page.

Basically all you need to do is add the following to the masterpage and set the correct value for the locale that you want:

<script language=”javascript” type=”text/javascript”>
L_Language_Text = 3081;
</script>

Once this is added the default dictionary is changed. I have included a table below of the common dictionaries for the various English languages. For a complete list of locales check out the following site here: http://msdn.microsoft.com/en-us/goglobal/bb964664.

English – United States – 1033
English – United Kingdom – 2057
English – Australia – 3081
English – Belize – 10249
English – Canada – 4105
English – Caribbean – 9225
English – Hong Kong SAR – 15369
English – India – 16393
English – Indonesia – 14345
English – Ireland – 6153
English – Jamaica – 8201
English – Malaysia – 17417
English – New Zealand – 5129
English – Philippines – 13321
English – Singapore – 18441
English – South Africa – 7177
English – Trinidad – 11273
English – Zimbabwe – 12297

If you get the ‘SeSecurityPrivilege’ error when trying to install SharePoint 2010 – this is due to not having adequate permissions with the account you are using. This can often be caused by the permissions your account has in Active Directory. Luckily there is a way to get around this on the local machine you are using.

 In order to fix this you will need to do the following:

Go to > Local Security Policy- > Local Policies -> User Rights Assignment on the server you are trying to install on.

Assign your logged in account (eg [domain]/[username]) the following rights:

• Back up files and directories
• Debug Programs
• Manage auditing and Security log
• Restore files and directories
• Take ownership of files or other objects

Once you have done this, log out then log back in again.
After this the installer should now work!

Wow! Can’t believe I haven’t discovered this before, but you can NOT directly update a SharePoint list item in a SPListItemCollection. Basically you need to reference the item you are going to update as an SPListItem and update that for it to work.

ie this does NOT work:

SPListItemCollection productMatches = currentWeb.Lists[“SomeList”].GetItems(query);
productMatches[0][“UpdatedValue”] = true;
productMatches[0].Update();

Where as this DOES work:

SPListItemCollection productMatches = currentWeb.Lists[“SomeList”].GetItems(query);
SPListItem someItem = productMatches[0];
someItem[“UpdatedValue”] = true;
someItem.Update();

Funny how such simple things can elude you for so many years… 😉