The ICANN (International Corporation for Assigned Names and Numbers) responsible for management and control of domain names has reported that at the end of this year the extension xxx is going to be available for the use of porn sites.

I'm curious... does this mean that porn sites are going to use this extension instead of the current sites? I don't believe that.

At the other hand it would be better for the internet and easier to filter these types of sites out. Especially with children on the internet.

Lets wait and see, it is good start for a cleaner internet :)

 

In one of the portals we removed the "Site settings" link from the page to prevent users clicking on it. For some additional users which have administrator rights we created a WebPart containing links to the most needed functionality. This custom WebPart contains a direct link to the settings of the current page, a direct link to the settings of users of the current page and a link to delete the current page and its children.

When designing websites and no texts are yet delivered by your customer you need "Lorem Ipsum"

"Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum. "

I found a site which generates "Lorem Ipsum" texts for you :)

http://www.lipsum.com/

I got a question from someone if it is possible to remove the help link from the webpart menu. And if possible to remove the whole webpart menu itself. The answer the first question i did some digging and found out the following stuff.

If we take a custom webpart, to remove the menu, or one or more menu items it is relative very easy. I wrote already an article about this. This can be easily accomplished by overriding the CreateWebPartMenu() method. and if needed setting the this.WebPartMenu = null;

To remove the Help from the menu you could also go into "Modify Shared WebPart" and clear the "Help Link" field under the "Advanced" category.

If we take a default webpart like a list or event, it seems that it does not work that way. These default webpart have already a "Help Link" filled in. Clearing the "Help Link" will not do anything and going into the "Modify Shared WebPart" will return the original url. It is possible to change it and it is reflected when you select the help from the menu but as soon as you go into "Modify Shared WebPart" it is returned to its original state. Meaning that when OK or Apply is pressed you back to start.

Why? I don't know. Feature or bug? I also don't know

I was looking for some answers on some questions i had through google when i came across this post which explains how to get your own scripts included in SharePoint pages. The article is from last year but its definitly the trouble reading it. Nice work :)

Changing the existing .js files like the ows.js file will work and keep the pages ghosted. But as described these files could be replaced by service packs or feature updates.

The solution is changing the <project> element in the ONET.xml file which will keep the pages ghosted and is not replaced by updates.

<Project Title="Blog Site" ListDir="Lists" CustomJSUrl="/_layouts/1033/cBlog.js" xmlns:ows="Microsoft SharePoint">
...
</Project>

The artice:

http://dev.collutions.com/blogs/sample/DisplayPost.aspx?PostID=8

For multiple .js files:

http://www.sharepointblogs.com/dustin/archive/2004/08/24/718.aspx

Another method of hooking in script logic is to use behaviours:

http://markharrison.co.uk/blog/2004/12/client-side-scripts-available-in.htm

 

Maurice wrote last year an article about the benefits of closing an disposing SPSite and SPWeb objects. In most cases it is therefor usefull to use the using functionality of .NET.

IMPORTANT:But as he stated in his last post you should never call dispose on a reference got from a SPSite by calling the method SPControl.GetContextSite. Only call Dispose() and Close() on your own objects.

http://www.bluedoglimited.com/SharePointThoughts/ViewPost.aspx?ID=175

Thanks Maurice for pointing this out to us! :)

 

Mike Fitzmaurice is talking about the SharePad project which can be found on GotDotNet. If you want to add document library support for your own editor you will have to use the FrontPage RPCs according to Mike. As stated on the website of GotDotNet:

"SharePad is a reference application demonstrating Microsoft Office-style SharePoint integration techniques. This application illustrates the use of the Front Page RPC calls exposed by SharePoint among other SharePoint integration APIs."

The following functionality is available:

Open a file that’s stored in a SharePoint document library

Save a file to a SharePoint document library

Navigate through the libraries in a SharePoint site

Check out the file

Check in the file

Register it within the WSS/SPS environment so it launches your editor automatically (like we do for Word, Excel, and PowerPoint documents)?

Set custom properties on the file as you save it

Read a file’s custom properties at the time you open it

http://blogs.msdn.com/mikefitz/archive/2005/05/30/423276.aspx

 

Tech-ed 2005 in the Netherlands is taking placed from july 5th til 8th and has some interesting sessions about SharePoint 2003. I have listed the descriptions of each session and they can also be found on the website for tech-ed. One session is not yet described and i'm looking foward to see wat the contents will be.

One of the sessions "Best Practices for an implementation" is about ten key areas of planning needed when desiging your portal. It also discusses what todo when a SharePoint Portal is already deployed and how to make adjustments in the design.

Sessions so far:

Developing Site Definitions and Templates for Windows SharePoint Services>

Developing with SharePoint Portal Server 2003, Outlook and Exchange: Advanced Integration

Getting Back to Normal: SharePoint Backup and Disaster Recovery

Maximizing SAP with SharePoint and Other Microsoft Technologies

MS IT: SharePoint Products and Technologies: Performance and Capacity Planning Best Practices and Lessons Learned

SharePoint Portal Server 2003: Best Practices for an Implementation

Bil Simser wrote two articles about so called YAUSF (Yet Another Undocumented SharePoint Feature). One article is about a telephone pattern were he is still working on. And the second article describes a hidden DisplaySize property for defining the length of a text field.

Both involves changes in some xml files but are not documented by Microsoft. The risk will be there that in a next version of SharePoint this is obsolete or changed. Lets hope that the guys at Microsoft read these articles and hopefully decide to leave this in and start documenting :)

http://weblogs.asp.net/bsimser/archive/2005/05/28/409568.aspx

http://weblogs.asp.net/bsimser/archive/2005/05/29/409642.aspx

 

For one of our customers a SharePoint portal is build containing monthly reports for their customers. For each customer a tree-like structure of sites and sub sites is created showing the report data in several ways. We created a WebPart which makes it relative easy for the customer to generate the tree-like structure of sites. A short and long name are entered for a new customer and generates the site and sub sites.