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”).
Carsten Keutmann has released a new version of his great WSPBuilder. Here are the new features:
A Reference folder under GAC and 80/Bin is now supported for large dlls that do not need reflection for SafeControls and Permissions. New menu function “Recycle the Windows SharePoint Services Timer” implemented on WSPBuilder Extensions. Refactoring of “Copy to GAC” in order to improve the functionality. Bug fixed! “Unable to get solution id from manifest: Unable to extract manifest.
Setting up your SharePoint farm to be able to crawl PDF files and show the PDF icon is a manual task which involves changing the registry.
If you don’t want to go through the steps manually, try the stsadm command from here: http://notesfor.net/post/2009/07/14/Automate-iFilter-and-PDF-Indexing-support-to-a-SharePoint-Farm.aspx
You can find the CodePlex site here: http://notesforsearchfilter.codeplex.com/
After the stsadm extension has been installed, setting up PDF support is easy: <span style="color:#606060" id=lnum1> 1:</span> stsadm -o searchfilter -ext pdf -filter PDFlib –iconfile "
Look at this:
Hans Brender has posted a blog article (in Germany) with this screenshot.
I can’t wait to get hold of the bits 🙂
Inserted links are now relative.
Go to the original post for more information and the download link.
An item level restore solution is available at AvePoint. The DocAve SQL Restore Controller care restore items, sites and site collections from a SQL or DPM database, or a backup.
If you click on the download link, you have to provide an email address. A download link will be sent to you.
The files you have to download are 414 MB (Manager) and 40 MB for the Agent. But the download server is fast 🙂
Then you should install the SP2 and the April (or June) CU for SharePoint.
setting site collections to read-only during backups fixes to Backup/Restore of publishing sites Zac Smith has posted an article about the why.
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.
Back from vacation. 1 week with an offline version of feeds is hard. So I read the postings I got closely 🙂 One post I do want to bring your attention to, is about SharePoint Controls.
My post about using the SharePoint Controls shows how to use the controls you see in forms (TextField, NumberField, LookupField…).
There are plenty of SharePoint controls, which you can use. Robin Meure has written a post “re-using SharePoint controls”.
If you ran into the expired license issue after applying the Service Pack 2, you will be happy to know Microsoft has released an update to resolve the issue.
Quote from the SharePoint Team Blog:
The update can be applied before or after Service Pack 2 installation. If the update is applied prior to installing Service Pack 2 it will prevent the expiration date from being improperly activated during installation of Service Pack 2, if it is applied after Service Pack 2 it will remove the expiration date incorrectly set during installation of Service Pack 2.
Using AJAX or Silverlight from within SharePoint in Webparts requires you to modify the web.config to support the technology. I don’t mention that you have to install the .NET Framework 3.5 SP1 and Silverlight to be able to use it…
Instead of changing the web.config manually (.NET Framework 3.5 AJAX und Silverlight in SharePoint registrieren von Fabian Moritz), you can use my features. They do all the necessary changes for you.
Blogs on the SharePoint sites from Microsoft are using the CKS:EBE.
The first one to move is Yvonne M. Harryman, who is moving her blog from WordPress to http://sharepoint.microsoft.com/blogs/SharePointBeacon. I am sure other blogs will use the Enhanced Blog Edition soon.
It is great to see that your own work is useful 🙂
An SPQuery for lookup columns should be easy. Start the famous U2U Caml Editor, configure your query, and query the list. This query will get a result if the lookup column stores something like “1;#1”. But if its value is e.g. “1;#Title”, the query will not return an item. So what can we do about it? Add a LookupId=’TRUE’ to your query, so it will look like this: <Where> <Eq> <FieldRef Name='LookupField' LookupId='TRUE'/> <Value Type='Lookup'>2</Value> </Eq> </Where> Remember to omit the Query tags from the U2U Caml Editor when pasting the query into your Visual Studio source code!
My SharePointConsole has some new commands.
If you don’t know it, it is a command line utility which allows you to perform some common tasks. Currently the theese commands are implemented:
EnumContentTypes CreateContentType RenameContentType DeleteContentType DeleteAllListItems ShowInNewForm ShowInEditForm ShowInDisplayForm DeleteAllVersions RecycleAllVersions SetTitleWithFilename SetSearchCenterUrl SystemUpdate FeatureManager EmptyRecycleBin Download the SharePointConsole
Deploying a SharePoint solution (.wsp file) to a SharePoint farm should be easy. Even if the farm contains 4 SharePoint Servers.
Just stsadm –o addsolution –filename solution.wsp. Some waiting so the deployment is done on every server, and we should be happy.
Well, the result was an Error in the solution status. Additionally the ULS log showed
Updating SPPersistedObject SolutionOperationStatus Name=SolutionOperationStatus Parent=SPSolutionLanguagePack Name=0. Version: -1 Ensure: 0, HashCode: 38896601, Id: 87c32e71-13f0-4d85-a215-29f1d180d239, Stack: at Microsoft.
