How to set alerts for yourself and others?

You can setup alerts for other users as well, below are the instruction to setup the alerts:

• Go to Library and click on Alert meà click on set alert on this library

• Here you can add the name or email address of the user for whom you want to setup alert or for yourself. You can add more than one user separated by a semi-colon or create a group of user who want to receive alerts and add the group name instead of adding\ setting alerts for multiple user one by one.

• Click on finish and you are done.

     Note: If any user wants to cross check that alerts has been setup for him\her, they can check by going to

          VIEW MY ALERTS ON A SITE

•       At the top of the site, click your name, and then click My Settings.
•      On the User Information page, click My Alerts.

         CANCEL AN ALERT FOR MYSELF

•      At the top of the site, click your name, and then click My Settings.
•      On the User Information page, click My Alerts.
•     Select the check box next to the alert that you want to cancel.
•     Click Delete Selected Alerts.
•     When you are prompted to confirm the deletion, click OK.

   

        VIEW ALERTS FOR OTHER PEOPLE ON A SITE

•       To view alerts for other people, you must be a site owner.
•        Click the Site Actions menu and then click Site Settings.
•       On the Site Settings page, under Site Administration, click User alerts.
•       In the list next to Display alerts for, select the person whose alerts you want to view.
•       Click the Update button.

        CANCEL AN ALERT FOR ANOTHER PERSON

•        To cancel alerts for other people, you must be a site owner.
•       Click Site Actions menu and then click Site Settings.
•       On the Site Settings page, under Site Administration, click User alerts.
•       In the list next to Display alerts for, select the person whose alerts you want to view.
•       Click the Update button.
•       Select the check box next to the alert that you want to cancel.
•       Click Delete Selected Alerts.
•      When you are prompted to confirm the deletion, click OK.
• 
  

Navigation Option was displaying only 50 items

We recently faced an issue while setting up top link bar on our sites, as we were using publishing  sites, we can see Navigation option instead of top link bar on site settings page.

After checking Navigation option we got to know that some of the links were not showing on top link bar and we were unable to change the position of few of the links.

After searching we got to know by default you can see only 50 items on Navigation items and if you want to increase it, there is a procedure to do that..

Below is the procedure to fix this issue :

Locate the web.config file on your server and do the below changes

<add name="CombinedNavSiteMapProvider" description="CMS provider for Combined navigation" type="Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider, Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" NavigationType="Combined" EncodeOutput="true" />

<add name="CurrentNavSiteMapProvider" description="CMS provider for Current navigation" type="Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider, Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" NavigationType="Current" EncodeOutput="true" />

<add name="CurrentNavSiteMapProviderNoEncode" description="CMS provider for Current navigation, no encoding of output" type="Microsoft.SharePoint.Publishing.Navigation.PortalSiteMapProvider, Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" NavigationType="Current" EncodeOutput="false" />

Add a DynamicChildLimit="0" before the end tag "/>" on each line to disable the default 50elements limit:

PS: Reference http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.publishing.navigation.portalsitemapprovider.dynamicchildlimit.aspx

Thanks !

Shared Document library page got corrupt

Recently I was reported for an issue in which user tried to upload a document and the shared document library AllItems.aspx page got corrupt and not working at all.

I dig-in the issue and found that somehow knowingly or unknowingly someone tried to alter AllItems view which caused the page to get corrupted.

Now the issue was how to create a default view for shared document library to make the library working again..

So here is the solution steps:





1) Open site that contains the library

2) Click on “Site Actions” >> “Site Settings” to view the site settings page “_layouts/settings.aspx”

3) Click on the Site list and library option under Site Administration heading and then click on the library name that displays the error to view the library’s settings page.

4) And create a new view for document library and make it as default view for document library and save it.  And here you go!

You can browse the document library and it should work.!

Enjoy!
Keep Learning :)

Move Wiki Pages to another library

Recently my lead asked me to move old wiki pages from one library to another, I was searching for traditional option of move to other location but to my surprise, I didn't find that option , I did some research and found that option is only available for normal document library and not for Wiki document library.

I did some search and found below method to move wiki pages from one library to another within same site or different site.

To move Wiki pages,

1. Go to Site Settings page of main site (site collection).


2. Go to the ‘Site Content and Structure’ page. You can access this site with either Site Actions > Site Settings or http://portal/_Layouts/sitemanager.aspx
3. Navigate to your source List or Document Library and mark all the items that you would like to have moved. Then click on Actions > Move
4. You’ll then be prompted with a pop-up that will let you navigate to your destination List or Document Library. After you find that, just press the OK button and you’ll be good to go!

Enjoy!!

Edit Page option is disabled\grayed out

Recently I got one issue, one user raised it saying like his edit page option was disabled(the ‘Edit page’ option in the Site Actions menu is disabled (greyed-out)!)

This is not an error. Edit page command will be disabled when another user has checked-out that particular page. To see which user has done so you will need to navigate to Pages library on your site.

If you have the right permissions and you need to edit the page, you can show the page editing toolbar and then click on Page -> Override Check Out. This will undo any changes the other users has made and the page will be checked out to you, but is useful if you really need to make a modification to the page.

Thanks !

Use Confirmation Page

Recently I came across a weird issue, one of the user raised an incident that he can't see the use-confirmation page and he is getting access denied error in-spite of having administrative rights on the site.

I checked myself and confirmd that he was one of a site collection admin, when I myself tried to access that page, I was getting SQL error, that page doesn't exist.

I searched a lot and found some solution, below are the steps:

Use Confirmation page URL : http://sitename/_layouts/useconfirmation.aspx

Description: This page is used to confirm that this site is in use,
Issue type: If anytime you get access denied error that means, this site has read only access or might get locked

Solution:

• Go to --> central admin--> application management---> 

• under site collection--> configure quotas & lock

• select the desirable site---> and check "lock status for this site" should be selected as "Not locked"

And that's it, it  should work.

Feature stapling

One aspect of features I wanted to cover quickly is the relationship SharePoint Features have with site definitions. Site definitions are created by a developer and subsequently used by site owners to create new sites. Much of this facility is also available by the 'Save site as template' functionality, though there are some minor differences. Additionally the 'Save site as template' functionality is removed on SharePoint publishing sites (or at least the link in Site Settings is via a HideCustomAction feature element), due I think, to some site information/functionality which SharePoint cannot properly save into a .stp file. So developers often create site definitions as part of their customization, and it's a process well-documented in the WSS SDK.

If you have created a site definition, there are several ways of using features with it. These are:-

1. Create a site from the definition and subsequently deploy your features to the site.
2. Include the features in the site definition (onet.xml) before using it to create sites.
3. Use feature stapling to associate your features to the site definition.

Since the first option doesn't really associate the Features to the site definition, we'll focus on options 2 and 3.

2. Include features in site definition

This option should be used if the site definition has not yet been deployed, and no sites have yet been created from it. The section of the onet.xml file where features are associated with the site definition contains may look something like:

<Configuration ID="0" Name="BLANKINTERNET">

    <SiteFeatures>

        <Feature ID="C85E5759-F323-4EFB-B548-443D2216EFB5" />

        <Feature ID="A392DA98-270B-4e85-9769-04C0FDE267AA" />

        <Feature ID="7C637B23-06C4-472d-9A9A-7C175762C5C4" />

    </SiteFeatures>

    <WebFeatures>

        <Feature ID="00BFEA71-DE22-43B2-A848-C05709900100" />

        <Feature ID="00BFEA71-E717-4E80-AA17-D0C71B360101" />

    </WebFeatures>

    <Modules>

        <Module Name="Home" />

    </Modules>

</Configuration>

The ID value is, of course, the feature GUID. The SiteFeatures element contains features which should be activated when the site definition is used to create a site collection, and the WebFeatures element contains features for when the definition is used to create a standard web within a site collection.

3. Use feature-stapling to associate your features to the site definition

This option should be used when the site definition is already in use (and sites have been created). This is because there are risks in modifying a site definition once it has been deployed, since the site definition files on the filesystem are used for pages which are ghosted (not modified).

To use feature-stapling, you first need the feature(s) you wish to link to the site definition - these should be created in the normal way. The, you should create a 2nd feature which does the actual stapling. Sample values for the various files are shown below:

The manifest.xml file if you are wrapping your feature in a solution:

<?xml version="1.0" encoding="utf-8"?>

<Solution xmlns="http://schemas.microsoft.com/sharepoint/" SolutionId="26E1A1D9-7BB2-4e76-888E-B20184B16E3B">

  <FeatureManifests>

    <FeatureManifest Location="COB.Demos.FeatureStapling\feature.xml" />

  </FeatureManifests>

</Solution>

The feature.xml file which defines the feature 'header' information:

<?xml version="1.0" encoding="utf-8" ?>

<Feature Id="4AF9999A-0517-4224-9ED3-D2F9F87D92E2"

        Title="COB.Demos.FeatureStapling"

        Description="Staples a set of features to custom site definitions. The features/site definitions are defined in stapling.xml."

        Version="1.0.0.0"

        Scope="Farm"

        Hidden="FALSE"

        xmlns="http://schemas.microsoft.com/sharepoint/">

  <ElementManifests>

    <ElementManifest Location="stapling.xml" />

</ElementManifests>

</Feature>

And finally, the core feature definition in the stapling.xml file:

<Elements xmlns="http://schemas.microsoft.com/sharepoint/">

  <FeatureSiteTemplateAssociation Id="F6924D36-2FA8-4f0b-B16D-06B7250180FA" TemplateName="MySiteDefName#0" />

  <FeatureSiteTemplateAssociation Id="94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB" TemplateName="MySiteDefName#0" />

  <FeatureSiteTemplateAssociation Id="02464C6A-9D07-4F30-BA04-E9035CF54392" TemplateName="MySiteDefName#0" />

</Elements>

The FeatureSiteTemplateAssociation element maps feature GUIDs to site defintions - note that the format of the TemplateName attribute value is <SiteDefName>#<ConfigurationID>. This obviously allows a degree of flexibility and allows you to do fairly complex things with different configurations of site definitions.

The final thing to note is that feature-stapling won't affect any sites which have already been created from a site definition, only subsequent sites. The only way to do this is to activate your features individually on the site, though obviously an STSADM script can help you activate multiple features against multiple sites.