We are currently using the jQuery library as part of providing a SharePoint solution. We are using the library to provide the client with a rich interface in the browser. 

We had included the references to the jQuery library in our Master Page for the site. We had had developed several Sharepoint web parts which in some cases needed the jQuery library.

Since we started using it we have seen our SharePoint pages get 'stuck' very often - mostly we have had to kill our browser sessions. The behavior is inconsistent and there is not specific way to trigger it off - just loading a page does it. The first pointer to us that it it had to do with something related to loading the jQuery libraries was when our browser in some instances started throwing the error below - we were using Internet Explorer 7.

Error: 'jQuery' us undefined

Code:0

Current Solution: We copied all the jQuery to the local web server and everything seems to be working properly now. I will find a long term solution, but for now this will do.

When creating\editing a SharePoint BDC metadata xml file using, Visual Studio you should set the schemaLocation value to C:\Program Files\Microsoft Office Servers\12.0\Bin\bdcmetadata.xsd. It can be represented in the LobSystem tag as shown below. If you open the XML file generated by certain tools like simego in Visual Studio, you will get warnings such as schema contains errors or file not found, modify the XML file as shown below to get intelliSense.

<LobSystem xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance

 xsi:schemaLocation ="BusinessDataCatalog file:///C:/Program%20Files/Microsoft%20Office%20Servers/12.0/Bin/bdcmetadata.xsd"

Warnings shown in Visual Studio if value is not specified properly: The schema referenced from this location in your document contains errors.

I was trying to add some basic and custom web parts to a SharePoint web part page and realized that although I could scroll through all the web parts in the gallery, I could not find the “Add” button at the bottom of the page. In I could not see any of the usual buttons or links at the bottom of the page either.

What happened was that we had created a custom theme that would apply to all web pages in the site; in the process we had modified some CSS files with some additional styles. The styles also apply to the dialog page that comes up when you click “Add a Web Part”.  The specific style that caused the dialog not to show the buttons due to its width element is shown below. Please note the buttons are actually created but are not fully visible due to the style below.

#aspnetForm {margin:20px auto;width:960px;background-color:white;border:2px solid #435380;}

In my case, if you remove the WIDTH element the buttons show up properly. I talked to my SharePoint designer Phil Foss (http://philfoss.com ) who then modified the styles which then made the button visible again.

NOTE:The “Add Web Parts” page (webpartgallerypickerpage.aspx) is a page that exists in the layouts folder to which styles are applied as well.  You can find a link to the web part gallery page if you look at the source of the page that you are editing in your browser (Search for "Add a Web Part").

If you are trying to swap out the home page of a SharePoint site (Default.aspx) file with another file by renaming it in SharePoint, the default\ welcome page will not change.

Steps to reproduce

1. Let’s say you have 2 files in the Pages folder Default.aspx (which is the default) and NewPage.aspx which you want to introduce as the default.
2. Using SharePoint you rename the Default.aspx page to DefaultOrig.aspx.
3. Using SharePoint you rename the NewPage.aspx file to Default.aspx
4. When you navigate to the site, you will see the default page as DefaultOrig.aspx. This is because internally SharePoint will changed the Welcome Page URL to DefaultOrig.aspx. You can verify this using the ‘Welcome Page’ option in Site Settings.

The best way to swap out the Welcome Page is to use the Site Settings à Welcome Page option instead.

If you create a web part using Visual Studio 2008 extensions for Windows SharePoint Services 3.0, v1.3 you may not be able to Deploy your Web Part to your SharePoint web site (WSS\MOSS).  Your first step off course should be to read the release notes posted by Microsoft as suggested by the error message. In my case the issue turned out to the security account that was linked to the VSeWSS WCF Service did not have administrator permissions.

Steps that caused the error

1.       Create new web part project and solution, choose deployment to bin directory.

2.       Choose the Deploy option by right clicking on the solution in the Solution Explorer.

Solution that worked for me à Added the ‘Network Service’ account to the Administrators group.

Finding Root Cause and Solving it (if it was similar to mine)

1.       Open IIS and navigate to the Web Sites folder. Select VSeWSS.

2.       Open the properties window for VSeWSS. Note the Application Pool value under the Home Directory tab.

3.       Under IIS go to the Application Pools folder, locate the Application Pool for VSeWSS.

4.       Open the properties window for the Application Pool. Note the Security Account value under the Identity tab.

5.       Open Computer Management. Locate the Administrators Group under Local Users and Groups.

6.       Make sure the Security Account is added to the Administrators group.

·          If the security account is not under the Administrators group your root cause should be similar to mine.

·          Helpful Note: If you are working on a Virtual\Local Server you may not be able to find your security account e.g. you may not be able to find your Network Service account, make sure you are searching for the account in the right spot by choosing the right Location (Network or local machine) when the Add Users… dialog comes up.

7.       Restart IIS if you had to add the security account and try deploying your web part again.

My Error Description (When trying to Deploy the web part)

“Error       1              VSeWSS Service Error: Assembly C:\Documents and Settings\username\My Documents\Visual Studio 2008\Projects\MyWebPartsOne\bin\Debug\MyWebParts.dll not found. This may occur because the VSeWSS WCF Service does not have local administrator permissions. Please review the release notes.

VSeWSS Service Logging Error: Access to the path 'C:\Documents and Settings\Default User\Application Data\Microsoft\VSeWSS 1.3' is denied.

Logging failed attempting to write to C:\Documents and Settings\Default User\Application Data\Microsoft\VSeWSS 1.3\VSeWSS1.3 service.log. This may occur because the VSeWSS WCF Service does not have local administrator permissions. Please review the release notes. “

URL for Visual Studio 2008 extensions for Windows SharePoint Services 3.0, v1.3

http://www.microsoft.com/downloads/details.aspx?FamilyID=B2C0B628-5CAB-48C1-8CAE-C34C1CCBDC0A&displaylang=en

I came across a good article for guidance regarding turning on SharePoint's publishing infrastructure, here is the link http://mindsharpblogs.com/penny/archive/2007/09/28/2973.aspx.

Notes for turning on the Publishing feature

• If you want to turn on the publishing feature you must do so at the Site Collection level first. Follow these steps...
  • Navigate to the Site Collection's top level Site then go to Site Settings.
  • Choose ‘Site Collection Features’ link.
  • Activate the ‘Office SharePoint Server Publishing Infrastructure’ feature.
• To turn on the publishing feature at the Site level. Follow these steps…
• Go the Site Settings page of the particular site.
• Choose to the ‘Site Features’ link
• Activate the ‘Office SharePoint Server Publishing’ feature
• You will notice you will now have access to Site Setting links such as ‘Navigation’  (under Look and Feel) that give you greater control over fine tuning your Site navigation.

This article may answer questions like….

•  How to start using web content management features of MOSS (Microsoft Office SharePoint Server
•  I cannot see the ‘Navigation’ link under Look and Feel for my Site.
• Where is my Navigation link under Look and Feel

For more on developing solutions using the MOSS technology go to this excellent article http://msdn.microsoft.com/msdnmag/issues/06/08/GatheringMoss/