SharePoint Conference in Slovenia

Filed Under (SharePoint) by Boris Gomiunik on 24-06-2009

After last year’s booming success the second SharePoint conference in Slovenia is announced!

Where: in Murska Sobota, Slovenia

When: at the end of November 2009. Please keep tuned to the SharePoint Conference website to get to know the exact date.

Why: it’s going to be at the end of November 2009 because it’s planned to be after the SharePoint conference in USA where the new SharePoint will be revealed. It is expected to be one of the first events after the revelation of SharePoint 2010.

If you’d like to feel the last year’s beat you can see the photos from the past year’s conference here.

If you’ have a good topic on SharePoint you’d like to share, register as a speaker here, if you’d like to participate as a sponsor, click here and – important – if you’d like to attend the conference, pre-register here.

The official website of SharePoint conference in Slovenia.

Interactive stsadm help

Filed Under (MOSS, SharePoint, SharePoint administration) by Boris Gomiunik on 07-06-2009

At TehNet they’ve released a very nice silverlight interactive help for STSADM command which the SharePoint Admin almost can’t imagine living without.

Straight to the point:

stsadm for MOSS 2007
http://technet.microsoft.com/en-us/office/sharepointserver/cc948709.aspx

stsadm for WSS
http://technet.microsoft.com/en-us/windowsserver/sharepoint/dd418924.aspx

Limiting the People picker and profile import from AD to certain group

Filed Under (MOSS, SharePoint, SharePoint administration) by Boris Gomiunik on 02-06-2009

If you have a SharePoint environment which not every employee in the organization uses you’re stuck with two obsticles:

  1. How to limit that the person is not selected and/or added as a member of the site collection (because of licencing issues)
  2. How to stop MOSS from importing entire AD domain or forest. If you’re stuck with 100 users from 1000 to enter information manually can be a pain.

The solution can be that SharePoint will not recognize other domains/forests than the ones specified and limit the people from those forests to only certain groups.

Here’s what I did. Let’s say we have an AD domain called contosio.local. In this domain We’ve created OU called AccessGroups and in this OU we’ve created a security group called SharePoint. We want to do this for the site http://moss

1. To limit People picker to certain group in AD domain
a. limit the peoplepicker property only to specified domain by running the following command
stsadm –o setproperty –pn "peoplepicker-searchadforests” –pv “domain:contosio.local,contosio\administrator,adminPassword” –url http://moss

Note in the example above you have to enter the account with the right to read from AD and its password. If you want to limit the access to multiple AD domains, separate the values in pv with semicolon.

b. limit the peoplepicker property to custom LDAP filter by running the following command:
stsadm –o setproperty –pn peoplepicker-searchadcustomfilter –pv “(memberOf=CN=SharePoint,OU=AccessGroups,DC=contosio,DC=local)” –url http://moss

Now you’ll be able to add people only from the domain contosio.local – group SharePoint. Don’t forget to add users to security group.

2. To limit profile import only to that same AD group (MOSS ONLY)
a. Open SharePoint Central Administration
b. Open Shared Services Administration
c. Click User Profiles and Properties
d. Click View Import Connections
e. Edit the domain connection for the domain (if you don’t have one yet, you’ll have to create it manually)
f. Change the default value of the field  User filter from (&(objectCategory=Person)(objectClass=User)) to
(&(objectCategory=Person)(objectClass=User)(memberOf=CN=SharePoint,OU=AccessGroups,DC=contosio,DC=local))

Like that you now control from AD who can access SharePoint and who’s profiles get imported.

Edit properties – Access denied error in document libraries

Filed Under (SharePoint, SharePoint administration) by Boris Gomiunik on 25-05-2009

A very interesting symptom occurred to me the past time. In a document library I was trying to edit document properties but I received an error that I don’t have rights. Strange. Even if I tried to edit with a site collection administrator account, I got the same error.

After searching for a while, I’ve found the solution. Looks like a bug that is fixed with February update, but you have to fix the existing bugs manually.

You can find the solution on Social TechNet. Using Visual Studio create a console application and copy-paste the code published there. I’ve made slight modification to the code, because I needed to have this fix in a subsite:

Old code:

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.SharePoint;
using System.Xml;

namespace CA_TestingHotfix
{
    class Program
    {
        static void Main(string[] args)
        {
            FixField(args);
        }

        static void FixField(string[] args)
        {
            string RenderXMLPattenAttribute = "RenderXMLUsingPattern";

            //Console.WriteLine("Please enter the URL of the site: (Press enter after typing):");
            string weburl = args[0];

            //Console.WriteLine("Please enter the Document Library Name: (Press enter after typing):");
            string listName = args[1];
            SPSite site = new SPSite(weburl);
            SPWeb web = site.OpenWeb();
            SPList list = web.Lists[listName];

New code (changes marked with bold)

using System;
using System.Collections.Generic;
using System.Text;
using Microsoft.SharePoint;
using System.Xml;

namespace CA_TestingHotfix
{
    class Program
    {
        static void Main(string[] args)
        {
            FixField(args);
        }

        static void FixField(string[] args)
        {
            string RenderXMLPattenAttribute = "RenderXMLUsingPattern";

            //Console.WriteLine("Please enter the URL of the site: (Press enter after typing):");
            string weburl = args[0];
            string subwebUrl = args[1];

            //Console.WriteLine("Please enter the Document Library Name: (Press enter after typing):");
            string listName = args[2];
            SPSite site = new SPSite(weburl);
            SPWeb web = site.OpenWeb(subwebUrl);
            SPList list = web.Lists[listName];

 

After you have the code ready, compile the program, put it on the server and run the command

[programName].exe [http://site_coll_url] [subweburl] [document_library_name]

If you need to run it for example on the top level web see the example below

fixDocLib.exe –url http://testSite:8080 / “Shared Documents”

Fixing / Reattaching / Changing the Lookup list

Filed Under (MOSS, SharePoint, SharePoint administration) by Boris Gomiunik on 19-05-2009

Today the strangest thing happened. During the content migration suddenly the target list lost the proper destination. The result was ALL the lookup values missing and the dropdown empty when adding /editing. Horror! if this would have been a short list the first thing I’d do is to restore it from backup and recover the lookup values. But this being the couple-thousand-records-and-growing-daily list I couldn’t afford that.

With a bit of research into Lookup Field Schema XML I’ve discovered that the LookupList and WebID properties (GUIDS) were wrong. Using SharePoint Manager I could correct the WebID but not the LookupList.

Fortunately after a short period of googling around I’ve discovered this post:

Reattaching LookupList Property to a new List

and that worked like a charm! All the values magically reappeared and lookup dropdowns are back in action.

Utility to quickly reapply themes in all subwebs

Filed Under (CodePlex, SharePoint, SharePoint branding, css) by Boris Gomiunik on 11-05-2009

If you’re in SharePoint branding, this small command-line utility might come in handy. If you have a custom template made and deployed to server and after a while you need to make a small modification, you can already be stuck with hundreds of subwebs using your custom template. If you make a change to the existing template, the change won’t be visible in the existing templates until you apply another theme and apply the same theme again to each of those webs.

Because this can be a painstaking job, I’ve composed a simple command-line utility to cycle through all of the webs in a site collection and apply default theme and reapply existing theme.

You can download it from CodePlex.

Usage is simple. Download it to the server running Windows SharePoint Services site you wish to reTheme. Open command prompt in the download folder and run command retheme http://site_collection_url.

Enable site/web specific theme elements and branding

Filed Under (Uncategorized) by Boris Gomiunik on 08-05-2009

I’ve had an interesting challenge recently. I’ve needed to create a custom site theme where certain subwebs would have their “identifiers” in design. What I mean by that: The site collection would have a specific theme applied, but in certain subwebs you should have the option of changing the banner for example.

The solution is actually quite simple:

When creating a theme you have to customize the theme.css file. Instead of putting all your class and id css definitions in theme.css, create additional CSS – for example main.css and put all of them there. Next, in theme.css import that file and right after this import, import another css in a document library (for example customCSS). So the whole scenario would be as follows:

theme.css

/*Main theme css*/
@import url('main.css');
/*enable custom styling*/
@import url('../../customCSS/custom.css');

main.css

/*all your CSS styling here*/

and in the (sub)webs where you need custom styling just create a document library called customCSS and inside put custom.css where you override the styles in main.css

Here’s an example:

Default theme:

image

main.css

td.ms-bannerContainer {
    border-bottom: 1px solid #326666;
    padding-left: 0px;
    padding-right: 0px;
    padding-bottom: 100px;
    background: #ece9e4 url('header.jpg') no-repeat left bottom;
}

Customized theme

image

main.css

td.ms-bannerContainer {
border-bottom: 1px solid #326666;
	padding-left: 0px;
	padding-right: 0px;
	padding-bottom: 100px;
	background: #ece9e4 url('header.jpg') no-repeat left bottom;
}

../../customCSS/custom.css

td.ms-bannerContainer {
     background: #ece9e4 url('header.jpg') no-repeat left bottom;
}

Get the month name in calculated column

Filed Under (SharePoint) by Boris Gomiunik on 07-05-2009

Before you go and make a long series of if clauses check the following:

If you need to get the month name from a date (and time) field, simply use the following formula:

=TEXT([DateField];"mmmm")

if you just need the three letters of the month name, replace “mmmm” with “mmm”. Now the problem may arise if you try to sort/group by month name. To keep them sorted, you can add the month number in front

=TEXT(month([DateField]); "00")&" "&TEXT([DateField];"mmmm")

Technorati Tags: ,

ERTE 1.2 released

Filed Under (ERTE, Flash, JavaScript, SharePoint) by Boris Gomiunik on 06-05-2009

Thanks Michael for pointing the issue out. I’ve finally caught up on some work that needed to be done on ERTE and now the new version is available for download. The updates are as follows:

  • Fix for IE8,
  • wrapped the thing in a function so you can run it on custom event
  • added support for _spBodyOnLoadFunctionNames array if it exists
  • set the button image location in a variable
  • added French language supprt. Thanks Slash71
  • isolated so it inserts only the <embed… </embed> part of code (to help bypass some limitations on truncated announcements views, if the embed code has <object,…></object>.

Curently there are only 3 languages supported – English, Slovenian and French. If you have 5 minutes of time, you also could contribute to this project. All you need to do is translate one line of text and send it to me. Maybe you can even post it as a comment so you’ll be recognized :)

Download the latest version from CodePlex site

Oznake ponudnika Technorati: ,,,,

Service Pack 2 available and promising!

Filed Under (Uncategorized) by Boris Gomiunik on 29-04-2009

If you’re reading this, head over to windows update and start downloading the Office system service pack 2 (available from yesterday – 28th apr). Then you can continue here. I was just going through list of bugs that SP2 fixes (xslx) in Office system and especially in SharePoint Designer (Thanks, Joel for posting link). Just to name couple of which I was already writing about and also wanted to blog about:

  • “After you back up a SharePoint Server site that spans multiple CMP files by using SharePoint Designer, you cannot restore the Web site.”
  • “Custom list forms do not support attachments.”
  • “Editing a page that contains Web parts that participate in Web part connections causes the connections to be broken.”
  • “When you restore a SharePoint site from an STP site template, data views are broken because of errors in the GUID.”
  • “When you use a data form against a SharePoint Server list that uses lookup fields, SharePoint Server does not submit the form correctly if the lookup source has 20 or more values.”
  • “You cannot successfully configure a Web part connection that contains a SharePoint Server filtering Web part.”

And tons more. In the Excel with changes you can find links to all other updates in Office and Office servers SP2.

ads
ads
ads