1.- Load your search.aspx with http://server/search.aspx&Mode=Edit?PageView=Shared

2.- Enter in design mode using “Modify Shared Page” menu

3.- Select the csegSearch Webpart and put it on page

4.- Go to the original “Search Results” webpart and modify properties, at the end there is a property called ResultListID, it has a list name, remember the name.

5.- Now delete the original “Search Results”

6.- Edit the csegSearch properties and locate the ResultListID, write the same name that the old webpart.

Jugando con mi nuevo webpart csegMiniWiki, he caído en la cuenta que en la lista de contenido hay ciertos campos ocultos (los que tienen todas las listas) de modo que he cogido mi webpart csegScriptWebPart para examinar la lista y ….

Como es lógico están todos los campos ocultos, bien ahora cómo csegMiniWiki puede reemplazar el nombre de un campo por su contenido he probado a ver que pasa y ….

This weekend I have finished the first version of csegScript, now are two webparts in the package, the first webpart is the 0.99 version with some improvements in the code, the operation basically is the same one. (See previous post)

The second new webpart uses a list to store the scripts, and has three slots to pass parameters to the webpart. (Thanks to Stramit by your idea)

The list fields are:

Introducing csegDocLibTools

The past week, looking how to show the missing folder view in document libraries, I had a good idea about how to improve my documents libraries, in this moment I had a clear idea over three things:

First I needed Copy and Paste documents in the library, because this is an essential feature to organize the library. There is a good solution to do from Syntergy, they have a cut and pase webpart.

csegDocLibTools properties

Well, there is a preliminary version available, I’m testing it in my production machine and the result at the moment its perfect.

The properties are separated in two groups, the first group, contains the document library on which it works and the webpart if this is attached to one.

The second group contains the webpart options. The four new options in the context menu, (Copy, Paste, Explore from here and Explore from root). There is also an option to show the files inside of the folder when the tree view is showed and an option to enable and disable the top menu.

There are things that I do not understand (too many) of SharePoint, today I have paid attention in the actions menu in image libraries, there is an action called “View all Folders” that not exist in document libraries, trying to solve this problem, I have had the idea to how to do a pretty webpart to Copy and Paste documents in documents libraries (this is in mind).

But, first les us solve the problem of view all folders in document libraries. I have spent an interesting short time  while seeing as the pages generated by sharepoint work, and there is an stupid trick to solve the problem.  It is enough with adding a link with javascript.

Yesterday looking a XML editor to edit complex xml files that I have in a Project that E&Y did in my company, I downloaded a trial version from  Stylus Studio XML IDE and I’m really surprised.  We could make a hard work in minutes. (Edit the data in a grid, sort the grid by levels and sublevels  etc…)

Normally I dont need tools like this for my diary work but I am considering this for my personal use (home edition is only 49$.)

Some users have reported some small errors with csegSearch, and some doubts,

- the colorize results only runs in the first set of results (fixed) 
- some extended results are in incorrect site (fixed)

Try this new version (with care this is not the 1.2 final), first uninstall previous version

csegSearchWebPart12.zip (11,45 KB)

stsadm –o deletewppack –name csegSearchWebPart.cab
iisreset

Stsadm –a addwppack –filename csegSearchWebPart.cab [-globalinstall –force]
iisreset

Plase use the forums to comment bugs and the doubts in foros.ideseg.com

Imagine test your webparts without compile, imagine an VBA for sharepoint, that was what I imagined yesterday and this is here… I have desire to say Yeahhhhh

Screenshoots (better an image than thousand words)

csegScript showing code

Properties

Show Code – Show the code with line numbers to identificate errors
Run Code – The code is executed when you applies changes
Script References – Write here the references of the project (.dll files)

SharePoint - Loading html documents inside of sharepoint pages One of the problems that I have been is when I have html documents in a document library and show this in a webpart page with the webcontent webpart. (I’m using the csegContent webpart that gets a querystring)

Sharepoint index them and after when you search, the query results show a link to them but when you load the document the context is missing, you have a window with the complete page without menu, quicklaunch etc…