I'm looking at using a Windows SharePoint Services 3.0 wiki as a metadata repository. We basically want a community-driven dictionary and for various reasons we're using Sharepoint instead of say MediaWiki.
What can I do to customize or completely replace searchresults.aspx?
Features I'd add if I knew how:
Automatically load the #1 hit if it is a 100% match to the search term
Show the first few lines of each result as a preview so users don't have to click through to bad results
Add a "Page doesn't exist, click here to create it" link in cases where there's not a 100% match
I've got Sharepoint Designer installed and it looks like I'll be able to use it to upload any custom .aspx files I create but I don't see that it will give me access to searchresults.aspx.
Note: Since I plan to access this search tool from an external site via URL parameters it should be fine to leave the existing searchresults.aspx unchanged and just load this solution as a complementary search option.
Yes, everything is possible but you will need to customize it a little bit.
I would recommend you to build a custom web part to display your results. Here is a nice article to start with: http://msdn.microsoft.com/en-us/library/ms584220.aspx
Related
Is there any way to make a full backup of Sharepoint Online web site based on Office 365 without third-party tools? Tried to google it, but found only ways to manually backup list or libraries. I'm need to save user properties, permissions, webparts, etc.
Thanks for help!
Since it is SharePoint online, you won't be able to perform a full-backup as you'd be able to do with Backup-SPSite.
However, you can save your site as a template. If your publishing feature is enabled for this site, you'll need to enable saving the website as a template via SharePoint Designer. Under the "Site" tab, select “Site Options”, find "SaveSiteAsTemplateEnabled" and set to "true". Then
add this to your site's url:
/_layouts/15/savetmpl.aspx
Fill out and submit the form. In my experience, that should take about 10 minutes, or the working on it screen might never change. If the later happens, you can check for your solution on this page:
/_catalogs/solutions/Forms/AllItems.aspx
This option might not work if your site is over 50MB, so you might need to forgo checking the option that allows including your list content in this backup.
I have around 9 web parts and 3 pages to be deployed. Each page will be having 3 webparts.
From a deploymnet perspective, i think i have the following two options:
Deploy the pages using a feature. The pages will have webparts present.
Create a custom site definition with a document library and have the three pages as part of the document library.
Can you please let me know which one of the options is better or is there any better solution?.
Please note that the solution needs to work on WSS 3.0 as well.
I would code the whole thing as a feature. You can staple it to the site definition for the site type you want it activated on.
If ever you need to migrate to the next version of SharePoint or another server it is easier to not have any custom site definitions. Also, the features leaves the site in a normal out-of-the box state; if you ever remove the feature nothing breaks.
Also, unlike the site definition it will also allow you to run it on sites that where created in the past.
First you need to deploy the webparts using WSP. Once it populated in webpart gallery you can copy the pages from page library and can paste in production.
I am stuck with a problem. I am having tool part where I get all the Lists present in the Site.
I have other web part which should get the selected List in the tool part.
I see that the web part is loaded first then the tool part. so the web part is unable to the List selected in the tool part.
Please note that the text box is in a User Control.
Please help me.
I have looked at your code and found the following:
First things first. You need to move AWAY from using ToolParts and the SharePoint native webpart. they are deprecated and are a remnant from SPS2003. In MOSS / WSS 3.0 you can and should use the ASP.NET WebPart.
Secondly, I think you are mixing things up. The ToolPartGetLists is not a toolpart, it is a webpart, that in itself loads the CustomToolPart, which in turn allows you to select a list.
This toolpart is only shown when you edit the shared webpart in the UI. The list you select is then persisted to the SelectedList property of the webpart using the toolpart.
The connected webpart then tries to read the SelectedList property I guess.
Like I said, I could go and try to fix the code for you, but it is not the way to go, you really (REALLY) need to switch to ASP.NET WebPart based webparts. The native sharepoint one WILL be fased out in the (near) future.
Here you can find an example, with code! (scroll to bottom for download link). As a bonus, it uses the built in sharepoint listpicker
I don't know of any way you could control the load order of elements (web parts) on the same page.
Sounds more like you want to have your second web part (the display of the lists) have a "default" when the page loads--which could be empty. Then it would be changed to the selected list only when the user clicked a new selection in the other web part (the list of lists).
I have a sharepoint list with several views. I can modify the view pages (such as AllItems.aspx) via the sharepoint designer. However I would prefer to modify the underlying template instead.
Now I could directly modify the default view page template located in templates\pages\viewpage.aspx but this would affect the whole sharepoint installation.
I would rather make a copy of this template and make my list (or views) point to it. Is there a way I can accomplish this?
Note: The list/views were created via the Web UI without any custom XML.
Check out this blog:
http://weblogs.asp.net/soever/archive/2006/11/11/SharePoint-Solution-Generator-2D00-part-1_3A00_-create-a-site-definition-from-an-existing-site.aspx
Basically, use the sharepoint solution generator to create a VS solution of your SharePoint list. The solution will contain a file called schema.xml that defines the list and associated views. You can then customize the aspx pages like viewlist.aspx and point the schema at your custom pages. When you deploy the solution/feature it will deploy your custom pages with it.
There's really a wealth of info out on the internets, it's just difficult to find when you don't know what you're looking for. But this should get you started in the right direction.
Also, in my experience, once you create the solution you should port it (read: copy teh contents) into an STSDEV project. STSDEV really shows you what's happening behind the scenes, whereas the other VS tools for SP development can do some hand-waving magic which will leave you in the dark when things go wrong. Just my 2 cents.
Can someone give me some directions on how to setup SharePoint Search Center so I can get results from the list and that they have some custom (modified) link?
I have Forms authentication (and anonymous access) enabled with alternate access mapping.
Right now in the Default zone I get results from the data in lists and they all point to the AllItems.aspx. If try search from the Internet zone I don't get any results from the lists and I am guessing that this is because of some security settings. But if make them to show how will I customize resulting link so that list items are shown with some publishing page.
For example if I keep news in the News list and when I do search I want to get result with link in following format
http://somesite/Pages/News.aspx?itemId=12
where the itemID is he id of the news item.
Can I customize link in the result ?
You can customize the result link using the Core Search Results web part. It is all in the XSL which is available if you modify the shared properties of the web part.
The problem is that this page is meant to show search results of all types including documents in SharePoint, files potentially outside of SharePoint, web pages, business data, etc.
You may want to have a custom search results page that uses a specific scope or managed property query such that you can be sure the results will be list items. This can probably be done without any coding (if you don't consider XSL coding) and you could still use the Core Search Results web part.
Another option may be similar, but use the Data Form/View web part (through SharePoint Designer) or the Content Query Web Part (Publishing Infrastructure feature required).