SPUtility.HideTaiwan - What does it do?

Thanks to intellisense I have discovered this method. The MSDN documentation about it is empty and I have "googled" it and I have found another related post but without any response.

Anybody knows what would happen if I execute it? SharePoint is scaring me…

CQWP debug item style

Reading this post a few months ago I found this great tip. If you want to know what are the fields that your CQWP receives you can use this item style to "debug" it.

<xsl:template name="Debug" match="Row[@Style='Debug']" mode="itemstyle">
<xsl:for-each select="@*">
            <br>
                <xsl:value-of select="name()" />
            </br>
        </xsl:for-each>
</xsl:template>

It will show all the fields passed to the web part (internal names). I recommend you to read the entire article; it shows the basis about the customization of the CQWP.

Related links:
http://blogs.msdn.com/ecm/archive/2006/10/25/configuring-and-customizing-the-content-query-web-part.aspx

SPQuery returns all items

If you execute an SPQuery through the SPList.GetItems(SPQuery) method and get all the items in the list, check the syntax in the Query property. The U2U CAML Query adds the tag <Query> to the query and it is not necessary in the Query property of SPQuery. For example:

SPList list = new
SPSite("http://MySharePointSite").OpenWeb().Lists[listName];

SPQuery query = new
SPQuery();

query.Query = "<Query><Where><Eq><FieldRef Name="Title" /><Value Type="Text">Test</Value></Eq></Where></Query>";
SPListItemCollection items = list.GetItems(query);

This code returns all items in the list, but if you remove the <Query> tag all works fine:

SPList list = new
SPSite("http://MySharePointSite").OpenWeb().Lists[listName];

SPQuery query = new
SPQuery();

query.Query = "<Query><Where><Eq><FieldRef Name="Title" /><Value Type="Text">Test</Value></Eq></Where></Query>";
SPListItemCollection items = list.GetItems(query);

Related Links:
http://joeshepherd.spaces.live.com/Blog/cns!9AE2097A4A610B63!123.entry

"Windows cannot find specified device, path or file.You may not have the appropriate permissions to access the item"

I have encountered this error today when I tried to execute a downloaded file on a Windows 2003 server. The cause of the error was the Internet Explorer Enhanced Security Configuration that is installed by default on a Windows 2003 R2. When you have installed it and try to execute a downloaded file it prompts this error.

To disable it:
1. Add or Remove Programs
2. Add/Remove Windows Components
3. Uncheck Internet Explorer Enhanced Security Configuration
4. Next

More info:
http://technet2.microsoft.com/WindowsServer/en/library/910d7a79-fd6f-447e-9bb1-bc9e57d54ec41033.mspx?mfr=true

Common problems with the MOSS variations

One of the most fantastic features in MOSS is the multilanguage support. It is accomplished through variations and I am going to explain two of the problems that I have encountered with it.

The invisible language selector: When you enable features on a site and create the variations, is probably that you are unable to select the language. The reason is a commented line in the language selector user control. You only have to uncomment it. The user control is located at “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\CONTROLTEMPLATES\VariationsLabelMenu.ascx”.

The variation systems crash, how to trace it?: A negative aspect of the variation system is that it do not alert when it fails. Then, the first place to look for any issue is in the variation logs at the top level site settings. The variation log shows all the activity of the variation system and shows errors like duplicate pages or content type errors. If this log is not useful you can explore the SharePoint logs (in the “hive 12”), but if the logs do not show the problem the next step is to check the state of the scheduled jobs in the farm. There is a job responsible of the propagation and it can be found in the Operation’s section in the Central Administration. If there is a problem with the jobs you can restart them restarting the Windows SharePoint Timer Service (services.msc) in all front-ends. It will restart all the jobs and the variation propagation will begin to work again.

I hope it help you!

Related Links:
http://blog.hametbenoit.info/Lists/Posts/Post.aspx?ID=168