<?xml version="1.0"?><?xml-stylesheet type="text/xsl" href="/rss.xsl"?><rss version="2.0"><channel><title>SPLanguageStore Releases Rss Feed</title><link>http://www.codeplex.com/SPLanguageStore/Release/ProjectReleases.aspx</link><description>SPLanguageStore Releases Rss Description</description><item><title>Created Release: 1.1.0.0 (May 04, 2009)</title><link>http://splanguagestore.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=26992</link><description>&lt;div&gt;This release fixes an issue where under certain circumstances, entries in the list cannot be edited because only 1 field is visible on the edit form. In actual fact the fields are still there, but they can only be updated using the API which isn't very convenient! This issue was also found (and resolved) in the sister project to this one, the &lt;a href="http://spconfigstore.codeplex.com"&gt;SharePoint Config Store&lt;span&gt;&lt;/span&gt;&lt;/a&gt;.&lt;br&gt;&lt;br&gt;&lt;b&gt;Sidenote&lt;/b&gt;&lt;br&gt;&lt;br&gt;I had seen this behaviour when SharePoint Content Deployment was used to deploy the list, but not under other circumstances. However, I &lt;i&gt;think&lt;/i&gt; a change in either the October 2008 or December 2008 Cumulative Update has caused it to be more of a problem, and I had a handful of reports of this problem.&lt;br&gt;&lt;br&gt;I've tested this in as many ways as I can think of (including Content Deployment), and it seems solid - I'm confident this is now fully resolved. Apologies for the inconvenience.&lt;br&gt;&lt;br&gt;&lt;/div&gt;</description><author>chrisobrien</author><pubDate>Mon, 04 May 2009 21:28:09 GMT</pubDate><guid isPermaLink="false">Created Release: 1.1.0.0 (May 04, 2009) 20090504092809P</guid></item><item><title>Released: 1.1.0.0 (May 04, 2009)</title><link>http://splanguagestore.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=26992</link><description>&lt;div&gt;This release fixes an issue where under certain circumstances, entries in the list cannot be edited because only 1 field is visible on the edit form. In actual fact the fields are still there, but they can only be updated using the API which isn't very convenient! This issue was also found (and resolved) in the sister project to this one, the &lt;a href="http://spconfigstore.codeplex.com"&gt;SharePoint Config Store&lt;span&gt;&lt;/span&gt;&lt;/a&gt;.&lt;br&gt;&lt;br&gt;&lt;b&gt;Sidenote&lt;/b&gt;&lt;br&gt;&lt;br&gt;I had seen this behaviour when SharePoint Content Deployment was used to deploy the list, but not under other circumstances. However, I &lt;i&gt;think&lt;/i&gt; a change in either the October 2008 or December 2008 Cumulative Update has caused it to be more of a problem, and I had a handful of reports of this problem.&lt;br&gt;&lt;br&gt;I've tested this in as many ways as I can think of (including Content Deployment), and it seems solid - I'm confident this is now fully resolved. Apologies for the inconvenience.&lt;br&gt;&lt;br&gt;&lt;/div&gt;</description><author></author><pubDate>Mon, 04 May 2009 21:28:09 GMT</pubDate><guid isPermaLink="false">Released: 1.1.0.0 (May 04, 2009) 20090504092809P</guid></item><item><title>Created Release: 1.0.1.0 (Mar 23, 2009)</title><link>http://splanguagestore.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=25130</link><description>&lt;div&gt;
Added an overload of GetValue() method to allow passing of an SPWeb (this is used to check SPWeb.Locale to determine which language to return). This allows the Language Store to be called from code which has no SPContext, e.g. Feature receiver, STSADM command, timer job etc.&lt;br&gt;
&lt;/div&gt;</description><author>chrisobrien</author><pubDate>Mon, 23 Mar 2009 23:19:06 GMT</pubDate><guid isPermaLink="false">Created Release: 1.0.1.0 (Mar 23, 2009) 20090323111906P</guid></item><item><title>Released: 1.0.1.0 (Mar 23, 2009)</title><link>http://splanguagestore.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=25130</link><description>&lt;div&gt;
Added an overload of GetValue() method to allow passing of an SPWeb (this is used to check SPWeb.Locale to determine which language to return). This allows the Language Store to be called from code which has no SPContext, e.g. Feature receiver, STSADM command, timer job etc.&lt;br&gt;
&lt;/div&gt;</description><author></author><pubDate>Mon, 23 Mar 2009 23:19:06 GMT</pubDate><guid isPermaLink="false">Released: 1.0.1.0 (Mar 23, 2009) 20090323111906P</guid></item><item><title>Released: 1.0.1.0 (Mar 23, 2009)</title><link>http://splanguagestore.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=25130</link><description>&lt;div&gt;
Added an overload of GetValue() method to allow passing of an SPWeb (this is used to check SPWeb.Locale to determine which language to return). This allows the Language Store to be called from code which has no SPContext, e.g. Feature receiver, STSADM command, timer job etc.&lt;br&gt;
&lt;/div&gt;</description><author></author><pubDate>Mon, 23 Mar 2009 23:19:06 GMT</pubDate><guid isPermaLink="false">Released: 1.0.1.0 (Mar 23, 2009) 20090323111906P</guid></item><item><title>Created Release: 1.0.0.0 (Dec 06, 2008)</title><link>http://www.codeplex.com/SPLanguageStore/Release/ProjectReleases.aspx?ReleaseId=20221</link><description>&lt;div&gt;
Initial release&lt;br&gt;
&lt;/div&gt;</description><author>chrisobrien</author><pubDate>Sat, 06 Dec 2008 12:10:19 GMT</pubDate><guid isPermaLink="false">Created Release: 1.0.0.0 (Dec 06, 2008) 20081206121019P</guid></item><item><title>Released: 1.0.0.0 (Dec 06, 2008)</title><link>http://www.codeplex.com/SPLanguageStore/Release/ProjectReleases.aspx?ReleaseId=20221</link><description>&lt;div&gt;
Initial release&lt;br&gt;
&lt;/div&gt;</description><author></author><pubDate>Sat, 06 Dec 2008 12:10:19 GMT</pubDate><guid isPermaLink="false">Released: 1.0.0.0 (Dec 06, 2008) 20081206121019P</guid></item></channel></rss>