In order to do site specific search (a.k.a. “This Site” scope) you can append a query string parameter as follows-
http://server/results.aspx?k=sharepoint&u=http%3A%2F%2Fserver%2Flists
Problem
The above will return zero results if you have a server name mapping configured in your search settings-
Solution
Removing the server name mapping will resolve this issue and site specific search works as expected
Tip: Adding a query string url restriction is equivalent to the following-
Problem
After installing Kwizcom Calendar 3.2.90, text selection is disabled on your sharepoint site on pages that have the calendar webpart. This was a huge issue for us since we had the minicalendar in the page header.
Workaround
Modify one of the Kwizcom javascript files (“12\TEMPLATE\LAYOUTS\KWizCom_KSCP\KSCP.js”) to comment out the drag drop functionality (See lines 13, 21 & 22) -
1: function kwiz_cal_DragDropOnLoad(q)
2: {
3: g_WPQ = q;
4:
5: // attach onscroll event (needed for recalculating table cells positions)
6: window.onscroll = kwiz_cal_Scroll;
7:
8: if(browseris.ie || browseris.safari)
9: {
10: kwiz_cal_Calculate_Cells();
11:
12: // disable text selection for ie, safari
13: //document.onselectstart = function(event) {return false};
14: }
15: else
16: {
17: // firefox does not execute this function when assigning to onscroll event, but IE & Chrome do
18: kwiz_cal_Scroll();
19:
20: // disable text selection for firefox
21: //if (typeof document.body.style.MozUserSelect != "undefined")
22: // document.body.style.MozUserSelect = "none";
23: }
24: }
More Info
The official word from Kwizcom Support on this issue is as follows:
“The issue is caused by dragdrop functionality. The new release version 3.3.00 will allow the users to disable drag drop through settings. Currently there is no exact timeline for release.”
1) Boot up & Login
You can login using either your regular Gmail account or your Google apps account. You can even sign in when there is no network connection. Presumably you would have had to sign in once with the network on but from there on outwards the OS seems to cache your credentials.
Boot up was under 15 seconds on all attempts with a VMware configured with 256MB RAM and 1 Processor at 2.4 GHz. From login screen to home screen took under 5 seconds on all attempts.
2) Inside the OS
Upon the first login, Chrome OS opens up 2 tabs that would be most commonly used: Mail & Calendar. However after resetting the machine chromium only displayed the Google home screen. The homepages are configurable (See configuration options below)
There is a button on the top left that seems to be the equivalent of a “Start” button in windows. However you need a “@google.com” account to access any “Google Short Links” here. Neither my Gmail account nor my Google Apps account worked here.
3) Configuration Options
Configuration options can be accessed from the top right drop down menu. Looks like Google is planning on supporting other browsers besides just chrome based upon the second configuration screen.
Are your alert emails defaulting to the generic template (SPAlertTemplateType.GenericList) even after you’ve specifically updated the list to use a custom alert email template (using myList.AlertTemplate)?
Turns out that if you already have an existing alert setup on the list then even if you switch the list to use a different alert template, sharepoint sends you alert emails using the template that was assigned to the list when you ORIGINALLY setup the alert.
So the SOLUTION is to delete your existing alert and re-subscribe to the list.
If you would like to know more on how to customize the alert email templates in sharepoint then this is a great resource: Customizing Alert Notifications and Alert Templates in Windows SharePoint Services 3.0
Did you recently change the IP address of your physical VMWARE host server? Are you having trouble getting into the web-based vmware console to manage your virtual machines? This post will help you solve a “503 Service Unavailable” error message.
I recently ran into this problem and soon realized that the “VMWARE Server Web Access” service had stopped due to the IP Change.
The solution is to simply start this service! You may notice a console window pops up and starts a tomcat process. Let this window run in the background. If you close it, then your service will stop again.
Did you upgrade your virtual machine to Windows Server 2003 SP 2 and found that the network adapter no longer works? This is a common problem on VMWARE server (2.0 in my case).
To fix this, install Vmware tools on the virtual machine. You can kick-off the installation using the Vmware Server homepage on the physical host.
I saw this bus in DC today-
