Category: Webparts

Widgets instead of Add-Ins/Apps?

The concept of Add-Ins (formally knows as Apps) in SharePoint puts logic as HTML and CSS to another page. This page is then rendered as iFrame to another SharePoint page. This approach has advantages and disadvantages. You have to decide yourself.

A very promising way to put stuff (or WebParts) onto a SharePoint page is the Widget Wrangler.

More information can be found on https://dev.office.com/blogs/introducing-widget-wrangler.

Conceptually Widget Wrangler implementation is based on similar thinking as PnP App Script Part implementation, which was released few years back as part of the PnP patterns (or at the time it was call App Model Samples). Advantages of this model is that you do not have deal with iFrame implementations and functionalities can be fully responsive, where needed. Also implementation of the capabilities is much simpler when your JavaScript is directly embedded to the page rendering logic without additional complexity.

In demo section Bob is showing following topics

  • How to use Widget Wrangler with plan JavaScript?
  • How to use Widget Wrangler with jQuery?
  • How to use Widget Wrangler with KnockoutJS?
  • How to use Widget Wrangler with Angular?
  • How does Widget Wrangler handle multiple instances of same widget in the SharePoint Pages?

I like that. As soon as I’ve some spare time, I will take a close look.

ChangePassword Webpart – new version available

The ChangePassword WebPart on CodePlex has been downloaded over 20.000 times. The new version has a couple of new features:

  • Easy Installation
  • SharePoint 2010 and 2013 (Foundation and Server)
  • Password strength indicator
  • Plugin support to extend functionality by custom code1
  • Warning if an unsecured connection is used
  • Copyright hint can be removed1
  • Auditing of password changes (and attempts)
  • Logging into the SharePoint logs

This is how it might look on your SharePoint:
ITaCS Password Changer
Documentation and downloads are available here.

Major Update to the Fileserveraccess Web Part

In 2008 I’ve released a Web Part, which enables your users to access files on your fileservers through SharePoint. Original post. This Web Part has been downloaded many times. With this new version, I’ve tried to deal with the most asked questions (like Kerberos), which will make the Web Part easier to use. Naturally new features have been implemented, to get you to upgrade to the new version.

With this release, the Web Part requires SharePoint Foundation / Server 2010. For the users who are still using WSS V3, please stick to the old version, or upgrade your farm 🙂

First some screenshots, so you know what I am talking about.

image

imageimage

Features

  • Download files from your fileservers via SharePoint
  • Download a folder with all containing files as zip-file
  • Upload files to a fileserver
  • Delete files from a fileserver
  • View the file properties
  • By default, the fileserver path has to be UNC. Local paths are not allowed, so a user cannot enter C:\ to access e.g. the web.config or other files on the local server
  • Multilanguage

Of coarse the access to the files is security trimmed. Meaning that if your users would not be able to access files with their logon from their client, they won’t be able from the Web Part!

Requirements

For authorization against the fileserver, the credentials of the currently logged on user is used. For SharePoint (and any other application as well), it is necessary to configure the WebApplication which is hosting the Web Part to use Kerberos instead of NTLM. Otherwise a server cannot pass the user credentials forward to a second server. This is called the “Double-Hop problem”. To get a glimpse about the topic, take a look at an article I wrote some time ago. Configuring Kerberos for SharePoint. That post has been written for SharePoint V3! But thereimage are plenty of Kerberos Guides out there for SP 2010. And a whitepaper from Microsoft: Configuring Kerberos Authentication for SharePoint 2010 Products http://technet.microsoft.com/en-us/library/ff829837.aspx

If you do not configure Kerberos for the WebApplication, the Web Part will detect that, and show a notification in the properties section.

A small sidenote: If you are going to use local paths (meaning a folder on your SharePoint server), you can continue using NTLM. 

Another good starting point for Kerberos-Troubleshooting can be found here: http://blogs.msdn.com/b/friis/archive/2009/12/31/things-to-check-when-kerberos-authentication-fails-using-iis-ie.aspx

Configuration

image

To use the WebPart, you’ll need to at least configure a path. Files – and subfolders – from that path will be shown.

Additionally, there are some properties, which modify features of the Web Part.

The Paging size defines, how many files are displayed on one page. With the next three checkboxes, you can allow files to be downloaded as zip, allow files to be uploaded and to be deleted.

I recommend to leave the caching activated. Deactivate only, if you have specific reasons, because there will be more todo for your SharePoint server and fileserver.

Using a local path as source

In case you want to use a local path as source for the Web Part, you have to allow the path to be used. To do so, follow the steps below.

  1. locate the feature.xml file ("C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\FEATURES\FileserverAccess\Feature.xml")
  2. Edit the file in your favorite editor
  3. Look for the property with the key “AllowLocalPaths” and modify the value to correspond to the driveletter you wish to use
    image
    Replace “Driveletter” with e.g. “C”. You can specify more than one drive letters. In that case use a “;” as divider
  4. Save the feature.xml
  5. Restart your IIS (iisreset)

Remember that you’ll need to modify the file on all of your FrontEnd SharePoint Servers! After an upgrade of the Web Part, the file has to be modified again. If you do not allow local drives, the Web Part will show an error.

image

This version is compatible to the old version. So you can simply upgrade the solution and benefit of the new features!

Download the new version for SharePoint 2010 (Foundation and Server): RH.FileserverAccess.wsp

Download the old version for WSS V3 / MOSS 2007: RH.FileserverAccess.wsp

Update March 2012

  • I did not get the Web Part working in my claims based authentication test-environment. Additionally, the Web Part properties will show the current user and authentication method. If you see Negotiate, your environment is set up correctly (for classic authentication).

imageimage

  • Another small update, which prevented the upload from working in Chrome

Active Directory User Editor

SharePoint is importing user information from the Active Directory through the Shared Services Provider (if you have MOSS).

Wouldn’t it be nice if users could “manage themselves”? That would save lots of time for the Admins 🙂

The answer is here: http://nominesptools.codeplex.com/

  • 5 different types of properties fields: Simple TextBox, DropDownList/ListBox (with predefined values), People Picker, Date Picker with calendar.
  • Multi-domain compatible.
  • Nearly Any Active Directory property can be easily added or removed of the edit form, directly trough the webpart configuration (nothing "hard-coded").
  • SharePoint "look & feel"
  • Available in English and French

Additional informations and installation manual are available here (French & English): http://alexis.nomine.fr/

image

This Webpart is again a prove that there are plenty SharePoint solutions for you to use.

btw: this was my post #200 😀

Multi Level Navigation

The out-of-the-box WSS navigation offers one level of navigation. The navigation elements can be configured in the site settings.

There is a way to make it have multi level navigation, as MOSS does, by changing the DataSource. But this “hack” is not flexible, as you can not reorder the item within the navigation menu.

While I was reading the post How to create your own Cascading Navigation using the ASPMenu control, the decision was made to build a custom navigation which supports multiple navigation levels.

default WSS toplevel navigation 

configure top link bar 

 

multi level navigation I wanted a more flexible way of realizing a navigation, which allows you to have more than one level with a plain Windows SharePoint Services site. So I build a navigation control, which uses the entries of a SharePoint list as source for the navigation elements.

Of coarse multiple navigation levels are supported. You can configure a parent element for each navigation element.To customize the order of appearance, you can set the ‘Link Order’.

The feature list:

  • Custom navigation control
  • Webpart shows the navigation
  • SharePoint list as DataSource
  • Multiple navigation levels
    • Assign a parent navigation element
    • Expand navigation nodes with child elements
  • Reorder navigation elements
  • Hide navigation elements
  • Access check on relative links for web, list and items
  • Cache
    • Items from the navigation list
    • Invalidate cache if there is a change within the listitems
    • Access to navigation Urls is stored in the session
  • Import SharePoint TopLevel navigation entries to the list
  • Get navigation list items with elevated privileges, so the list can be hidden from users
  • Grouped view “By Parent” for the navigation list
  • Url Parameter
    • Refresh=true
      will force a reload of the navigation list items
    • Debug=true
      will show how long (in ms) the navigation control needs to render

Each navigation element is stored in a SharePoint list. This list is created when the feature is activated on the SiteCollection.

SharePoint list

The list can be filled with the current SharePoint navigation by clicking on the link “Import Navigation to Multi Level Navigation List” in the site settings. It brings up another page, where you can import the navigation and check for updates for the solution.

site collection administration

Installation:

  1. Add the solution with “stsadm –o addsolution –filename RH.Navigation.wsp”
  2. Deploy the solution in the Central Administration
  3. Active the feature “RH.Navigation” for a site collection
    sitecollection feature
  4. Add the Webpart to a page, or alter the masterpage to use the custom navigation instead of the build-in SharePoint navigation

Customize the masterpage

To use the Multi Level Navigation instead of the out-of-the box SharePoint navigation, register a tagprefix, add the control and remove the SharePoint Navigation.

  • Add an entry to the top of your masterpage
    <%@ Register TagPrefix="Navigation" Namespace="RH.Navigation.Control" Assembly="RH.Navigation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=2d07bbf19c37a6cf" %>
  • Alter the SharePoint navigation
    <SharePoint:AspMenuNavigation:MultiLevelNavigation
          ID="TopNavigationMenu"
          Runat="server"
          DataSourceID="topSiteMap"
          EnableViewState="false"
          AccessKey="<%$Resources:wss,navigation_accesskey%>"
          Orientation="Horizontal"
          StaticDisplayLevels="21"
          MaximumDynamicDisplayLevels="1"
          DynamicHorizontalOffset="0"
          StaticPopoutImageUrl="/_layouts/images/menudark.gif"
          StaticPopoutImageTextFormatString=""
          DynamicHoverStyle-BackColor="#CBE3F0"
          SkipLinkText=""
          StaticSubMenuIndent="0"
          CssClass="ms-topNavContainer">
            <StaticMenuStyle/>
            <StaticMenuItemStyle CssClass="ms-topnav" ItemSpacing="0px"/>
            <StaticSelectedStyle CssClass="ms-topnavselected" />
            <StaticHoverStyle CssClass="ms-topNavHover" />
            <DynamicMenuStyle  BackColor="#F2F3F4" BorderColor="#A7B4CE" BorderWidth="1px"/>
            <DynamicMenuItemStyle CssClass="ms-topNavFlyOuts"/>
            <DynamicHoverStyle CssClass="ms-topNavFlyOutsHover"/>
            <DynamicSelectedStyle CssClass="ms-topNavFlyOutsSelected"/>
        </SharePoint:AspMenuNavigation:MultiLevelNavigation>
  • OR remove the SharePoint navigation (<SharePoint:AspMenu…) and insert the MultiLevelNavigation
    <Navigation:MultiLevelNavigation runat="server"></Navigation:MultiLevelNavigation>

Note:

If your AspMenu contains the StaticDisplayLevels property, remove it or set it to 1! (Quote from MSDN: The StaticDisplayLevels property indicates how many levels to display statically from the root of the menu. For example, if StaticDisplayLevels is set to 3, your menu will be expanded to statically display its first three levels. The minimum static display level is 1, and the control will throw an exception if the value is set to 0 or a negative number.)

Download RH.Navigation.wsp

Download Sourcecode 

Upload documents/pictures to a discussion lists

You might already know my Wiki Webpart, which allows you to upload pictures and documents to a Wiki while editing it.

What is it?

With this Solution you can upload images and documents from the new/edit form into existing picture/document libraries. After the file has been uploaded, a link will be inserted into the Body.

This is either a <img> or a <a> tag, depending on the uploaded file.

How does it work?

After uploading the image/file, it will be put into your Body via JavaScript. There is no reload of the page required.

Requirements

.NET 3.5 (SP1) on all of your frontend servers

Installation

The DiscussionListUpload comes as a SharePoint solution (wsp file), which will be installed on your SharePoint farm via "stsadm -o addsolution -filename RH.DiscussionListUpload.wsp".

The solution contains one feature, which has to be activated on site collection level.

After the feature has been activated, discussion lists will have a new link in the list properties.

If you click on the link, it will bring up a settings page for the feature.

Enabling the feature in the properties will add the Webpart to the NewForm and EditForm of your discussion list. Disabling it, will remove the Webparts.

Update:

Instead of this solution you can use my Custom Files and Images Upload Field.

If you want to use it, please make sure you disable this feature on the discussion list and on your sitecollection.

Download

Download Solution

Download Source code

Technorati Tags: ,

FilterParts for SharePoint

A while ago Microsoft released some filter Webparts on MSDN.

SharePoint Filter Webparts including:
– BDC MultiFilter: Similar to the BDC Data Item Builder web part provided with MOSS 2007 Enterprise Edition, except it provides up to 4 additional filter connections containing BDC entity attributes to allow display of more entity-related data
– ShowFilter: Diagnostic display of any filter connected
– ShowFilterMap: Displays a Virtual Earth map when passed a filter containing a street address
– ShowFilterSearch: Displays MOSS search results when passed a filter connection containing a search query

 

Webpart to show Sitecollections/Subwebs

This Webpart will show Sitecollections from the current Webapplication or Subwebs from the current web.

In the Webpart properties you can choose what the Webpart will show.

It uses the Logo URL of websites, if they are specified. The description of the website will show up as tooltip.

I am using the RepeatedControls class to build the items. This class really makes it easy to add entries by moving the layout functionality into an own class.

Create a new class

class Links : RepeatedControls
{
    private readonly Table _Table;
}

 

Add a default constructor

In the constructor, you can modify the header, footer and separator for the entries.

public Links()
{
    HeaderHtml = "<div>";
    FooterHtml = "</div>";
    SeparatorHtml = string.Empty;
 
    _Table = new Table {CssClass = "ms-itemstatic", CellSpacing = 0};
    _Table.Style.Add("padding", "3px 0px 3px 4px");
    Controls.Add(_Table);
}

 

Add elements to the class

public void AddHyperLink(string text, string toolTip, string url, string imageUrl)
{
    var row = new TableRow {Height = Unit.Pixel(16)};
    row.Attributes.Add("title", SPHttpUtility.HtmlEncode(toolTip));
    row.Attributes.Add("onmouseover", "this.className='ms-itemhover';MMU_PopMenuIfShowing(this);");
    row.Attributes.Add("onmouseout", "this.className='ms-itemstatic';");
    row.Attributes.Add("onclick", "window.navigate('" + url + "');");
 
    var imageCell = new TableCell();
    imageCell.HorizontalAlign = HorizontalAlign.Center;
    imageCell.Style.Add("padding-top", "1px");
    var image = new Image
                    {
                        AlternateText = string.Empty,
                        ImageUrl = (!string.IsNullOrEmpty(imageUrl) ? imageUrl : "/_layouts/images/setrect.gif")
                    };
    imageCell.Controls.Add(image);
    row.Cells.Add(imageCell);
 
    var linkCell = new TableCell
                       {
                           VerticalAlign = VerticalAlign.Top,
                           Width = Unit.Percentage(100),
                           CssClass = "ms-descriptiontext"
                       };
    linkCell.Style.Add("padding-left", "3px");
    var link = new Label {Text = SPHttpUtility.HtmlEncode(text)};
    linkCell.Controls.Add(link);
    row.Cells.Add(linkCell);
 
    _Table.Controls.Add(row);
}

 

Now that we have our own class to deal with navigation entries, we will use it.

Usage

var links = new Links();
Controls.Add(links);

 

To add items, simply type:

links.AddHyperLink(objects.Title, objects.Description, objects.Url, objects.ImageUrl);

Advantage

Why would you use your own class derived from RepeatedControls?

  • don’t mix functions and layout
  • keep you code small
  • improve the readability of your code

If you want to use this solution, you have to install the WSPBuilder Visual Studio extensions!

Download solution

Download source code

26. Oct. 2009 – Update to 1.0.1.0

Showsubwebs now uses web.ServeRelativeUrl

Wiki Webpart 2.0

The next generation Wiki Webpart is there! Sounds good J The (stupid) name remains, but the core has changed.

What is it?

With the Wiki Webpart you can upload images and documents from a Wiki edit page into existing picture/document libraries. After the file has been uploaded, a link will be inserted into the Wiki Content.

This is either a <img> or a <a> tag, depending on the uploaded file.

How does it work?

After uploading the image/file, it will be put into your Wiki Content via JavaScript. There is no reload of the Wiki page required any more.

Why can’t I upload files when I create a new Wiki Page?

Because MS decided to change the normal "NewForm" behaviour in Wiki libraries. Unlike in lists/document librariew a new item is created through "_layouts/CreateWebPage.aspx" and not the NewForm.aspx. And since this one is not unique for the Wiki library, I can not adjust it.

Requirements

.NET 3.5 (SP1) on all of your frontend servers 

Installation

The Wiki Webpart comes as a SharePoint solution (wsp file), which will be installed on your SharePoint farm via "stsadm -o addsolution -filename WikiWebpart.wsp".

The solution contains two features.

One has to be activated on site collection level (it will allow you to use the Webpart).

The second feature has to be activated on each web, where you want to use the Wiki Webpart.

After the features have been activated, there is a new entry in the General Settings of a Wiki library.

Enabling the Webpart in the Wiki properties will add the Webpart to the EditForm of your Wiki library. Disabling it, will remove the Webpart. There is no need to add the Webpart with the console application anymore!

Upgrade from previous version:

If you already have an older version installed, the installation steps are similar.

  • stsadm -o upgradesolution -filename RH.WikiWebpart.wsp -name RH.WikiWebpart.wsp -immediate –allowgacdeployment

After upgrading the solution, you have to retract and redeploy it in the central administration. This step is necessary, because the features within the solution have changed!

Update 30. Nov 2008:
A small bugfix release.

Update:

Instead of this solution you can use my Custom Files and Images Upload Field.

If you want to use it, please make sure you disable this feature on the wiki, the web and on your sitecollection.

Download

For all the (security) guys who wanted the source code, you can get it now.

Download solution

Download source code

 

Tags:

TagCloud Webpart

Categorizing posts with keywords is not new. There are solutions which create a new column for your blog, where you can define categories.

My Webpart will look in your posts for Technorati links. Many posts are tagged with Technorati links, so that you can look for a tag, and find posts on many blogs for this tag.

You can create Technorati links with the Live Writer, if you want to blog with it.

How does it work?

The Webpart will look for links <a href="technorati.com/tag/ and generate a Tag Cloud from the links. If you have other links which you would like to use for Tags, you can configure the link in the Webpart properties.

Selecting a Tag from the Webpart by clicking on it, will show all related posts. This way you can navigate within your blog posts by selecting Tags and not going through the Technorati page, if you use a Tag Cloud generated by them.

The Webpart uses a SPQuery to find all posts with the link in it, groups them and generates the Tag Cloud. A click on a Tag will bring up a list with all related posts.

For performance reasons, the Webpart caches tags for 5 minutes. With the Refresh Button at the bottom of the Tag Cloud you can force a reload of all tags.

  Download Solution

  Download Source

  Download Update Source

Updated WikiWebpart

Since so many people asked for support to upload documents as well, I have implemented this functionality into my WikiWebpart. Now you can add pictures and files directly into your wiki by uploading them from the clients.

As always, you have to install the solution, and activate the WikiWebpart feature for you Sitecollection as described in Updated WikiWebpart + Tool to install it.

The Webpart will detect an existing picture and document library, and use it. If you have multiple libraries on your website, you can configure which one to use in the Webpart properties.

Note: This version of the Webpart will install itself into the GAC.

  • Download WikiWebpart Solution
  • Download AddWikiWebpart Tool
  • Access Fileserver Data via SharePoint

    Update:
    The Webpart is not (yet) working as expected. Ajax only works for postbacks. The initial load will take longer, if you have many directories. I am working on this…

    Update2:
    Almost done! Ajax is working fine. Ajax is registered, so you don’t need to modify the web.config yourself.
    Todo: Performance.
    Hang on just a little more.

    Update3:
    Done. I have worked on my Webpart. It will now be faster and it is working 🙂
    If you have previously installed the Webpart, please uninstall it, and reinstall again. You can use the setup program.

    Update3:
    A new version has been released. Take a look at Major Update to the Fileserveraccess Web Part.

    I guess everybody knows this scenario. You are with a customer or at home, and need a file from your company’s fileserver very badly. What can you do? VPN is not possible, and you can’t phone a colleague who can then send you the file via email because nobody is in the office. Don’t bother any more. The solution is here J

    With my Webpart you can access files from e.g. your fileserver via SharePoint / Browser.

    All you have to do is install the solution, activate and deploy it. When you drag the Webpart onto a SharePoint page, you configure the root path from which you want to share data, and your users are able to download the files through the Webpart.

    All files and folders are security trimmed. Meaning you can only download files and see folders, which you would see on the directory itself.

    Of course this Webpart is translated to English and German. If you want it in your language, contact me.

    Sorting the four columns allows your users to find the files they are searching more quickly. The paging size can be configured in the Webpart properties.

    This Webpart requires the .Net Framework 3.5 on your WFE (Web Front End) Servers and you have to modify your web.config files to use AJAX. There is an Installation guide here. Be careful to change the version number from Version=1.0.61025.0 to Version=3.5.0.0!

    Installation:

    After you have added the solution via stsadm, you have to activate the feature on your webapplication and site collection.

    Update:

    The Webpart can now be installed with a setup program. It will automatically adjust your web.config, so you don’t have to manually put in all AJAX configuration elements.

    Before you activate the feature on your sitecollection, activate the feature for the web application in the central administration. This will do all steps for you.

    Update 5.6.08:

    A small update. Added danish language support (thx to Anja!) and a small performance tuning.

    Update 19.6.08:

    A small update. Installing the solution via installer does not work as expected. So I will have removed the installer, and uploaded a plain old wsp.

    Update 29.9.09

    If you are running your SharePoint Farm on a Windows Server 2008, you might want to read this KB article. I is titled "You cannot upload files that are larger than 28 MB on a Windows Server 2008-based computer that is running Windows SharePoint Services 3.0"

    Update 12.01.12

    Major Update to the Fileserveraccess Web Part

    Download the solution here

    Technorati Tags: ,,

    Updated WikiWebpart + Tool to install it

    I updated my WikiWebpart. You can now download it as a SharePoint Solution.

    Steps to install the solution:

    1. Install the solution via "stsadm -o addsolution -filename RH.WikiWebpart.wsp"
    2. Go to your "Central Administration > Operations" and deploy the solution

    3. Active the Feature for your Sitecollection
      Go to "Site Actions > Site Settings > Site Collection Administration > Site collection features" and active the feature
    Add the Webpart to your Wiki library

    Now you are done. You can add the Webpart to any Wiki library you like. To make this process easier, I wrote a little tool for it. You call it with the weburl and the Wiki library name as parameters.
    RH.AddWikiWebpart.exe http://sharepointurl/somewikipage "Wiki Pages"

    Done.

    One more note. Right now the Webpart only displays english text. When I find a solution to add the resource assemblies for german, I will update the Webpart.

    If you have previously installed the Webpart manually, remove it from all Wiki library EditForm.aspx, from the Webpart gallery, and from your web.config and bin folder.

    Update:

    Multilanguage Support is back 😉
    You can download the solution and update it via
    "stsadm -o upgradesolution -name RH.WikiWebpart.wsp -filename RH.WikiWebpart.wsp -immediate"

    Update 23. Apr 2008:

    I have released a new version. Bugfixing only.

    Update 5. Jul 2008:

    A new version with support for uploading files additionally to pictures.

    Display all my alerts

    The "old" SharePoint Server 2003 offered the ability to display all alerts from a user on his/her MySite. MOSS and SharePoint 2010 lacks this functionality. So I wrote a Webpart, which will display all my alerts. Of course is multilingual. Currently there is English, German and Spanish language support included. And it will work on Windows SharePoint Services V3 as well ass SharePoint Foundation. You don’t need the Office Server / SharePoint Server 2010 for it 🙂

    You can configure which columns shall be displayed, and if you want to see all alerts from all websites within your SharePoint farm.

    The Webpart will iterate through all websites, and look if there are alerts for the current user. You can then modify the alerts, or navigate to the corresponding website and list by clicking on the appropriate entry in the context menu of the alert.

    To install this Webpart, install and deploy the solution via stsadm:

    1. stsadm -o addsolution -filename RH.MyAlerts.wsp
    2. stsadm -o deploysolution -name RH.MyAlerts.wsp -immediate -url http://yoururl

    Instead of deploying the solution using stsadm, you can deploy it in the central administration of your farm.

    Creating the solution wsp file is very easy, if you use the WSPBuilder.

    Download the solution.

    Download the source code for the Webpart.

    (Please set the trust level of your web.config to ‘Full’!)

    Keywords: SharePoint, alert, all my alerts, benachrichtigung, alle meine benachrichtigungen anzeigen

    Update 16.12.07
    I fixed an error and the Multilanguage support is back

    Update 12.05.08
    Another small update. Handling search alerts is improved and the assembly will not install in the GAC (Global Assembly Cache) to get rid of the FullTrust setting in the web.config.

    Update 11.06.08
    This update deals with the problem that SPContext.Current.Web.CurrentUser is sometimes null.

    Update 31.08.08
    The Webpart does now include an update check in the Webpart properties.

    Update 01.10.08
    A small bug fix update.

    Update 26.10.08
    I have implemented Spanish localization.

    Update 08.11.08
    A small update to 1.0.4.0 with bugfixes

    Update 22.07.09
    HtmlDecoding for the GroupBy field value (the title for webs)

     

    Update 1.9.09 – Version 1.0.6.0
    Fix to prevent Access Denied e.g. for SSP Sites.

    Update 20.12.2011 – Version 1.1.0.0
    Small update to improve SharePoint 2010

    Updated Wiki Webpart

    Please use my custom field type. It is more flexible –> http://www.hezser.de

     

    I updated my Wiki Webpart. For all of you who don’t know what it does:

    The normal Wiki Edit Form misses the ability to upload pictures. My Webpart, which has to be included to the EditForm.aspx, allows you to upload a picture. It also creates a link in your Wiki post, which displays the uploaded image.

    This release of the Webpart is multi lingual. Meaning it will present text to the user in english and german. If you would like this Webpart in your language, drop me a note 🙂

    Installation steps:
    (If you need help: look here)

    1. copy the dll to the bin folder of your SharePoint virtual server
    2. create an entry in the safecontrol section of your web.config
      <SafeControl Assembly="WikiWebpart, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b17a955c3eada4c1" Namespace="WikiWebpart" TypeName="*" Safe="True" />
    3. change the TrustLevel in the web.config to either "WSS_Medium" or "Full"
    4. add the Webpart to the Webpart gallery of your sitecollection
    5. modify the EditForm.aspx of your Wiki Page with SharePoint Designer, and add the WikiWebpart beneath the standard EditForm Webpart
    6. you are ready to use it 😉

      Download the Webpart

    Update 23. Apr 2008:

    I have released a new version. Bugfixing only.

    Display a single listitem

    You can display multiple list items with SharePoint and SharePoint Designer quite easy. But how do you display a single listitem? I worte a Webpart, which does this. If there are more than one listitem, you can page through them. And if you like, you can pass an itemid via a Webpart connection.

    In the Webpart properties you can select the list/library. If you like, you can specify a view other than the default view.

    SafeControl Entry for your web.config:
    <SafeControl  Assembly="RH.DisplayListItem, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7850e867f7381714"  Namespace="RH"  TypeName="*"  Safe="True" />

     Download Webpart
     
    Download Webpart Source