Tag Info

Hot answers tagged

2

Instead of using foreach loop, try performing operation using a for loop. for($node=0;$node -lt $nodeC.Count;$node++){ $nodeVal = $nodeC[$node]; $nodeC.Delete($nodeVal);}


2

What you need is to create the UL and DIV element in the control template and push your content in it via the item template. Now because you are working with display templates, this can only be done onces the rendering is complete, because at that time, the HTML is placed on the page. My approach is to add your list items and description values to two ...


1

This is not a setting what you can change. This feature comes with the View of the List or Library. This option gets displayed on the View when the view Style is set to "Default" You can read this http://www.sbrickey.com/Tech/Blog/Post/SharePoint_Feature_Request_Deploying_View_Styles to find more about the Styles and how to set it via PowerShell.


1

I think you should change your approach. Create webpart zone in the place of Search WebParts. Then while creating the page choose this new layout. Then edit page and add the Search WebParts. If you have made customizations to the Search WebPart which you want to reuse, then "Export" the webpart and then upload it to the webpart gallery as a new webpart. ...


1

Another option would be to add a content query webpart in the page - edit webpart - click Change Query - set keyword filter as Query from the search box - give path:Your library path Apply and save the page and try it out. You could refer this blog article for more information on configuring the content query webpart: Configure Content Query Webpart Edit: ...


1

You can make use of query string filtering. Create a new view for the document library and set filter to use {FilterQueryString} and apply necessary condition Create a new wiki page and then add the library webpart - Then set the view = new view create in step1 above In home page edit the page and add a new Script Editor WebPart and use <script> ...


1

you need to customize the item display template, Go to Design Manger and then Go to Design Templates, download the item display template and then you can modify it and save it with a new name. here you go with an code example. ...


1

You can create a new display template.The display template defines what we want our results to look like. To check all available search display template go to Site settings --> Master pages and page layouts. In the Master Page Gallery, click Display Templates --> Search. Check these examples for more granular steps. ...


1

Modifying the display templates is the only option Open Display Templates -> Search Edit file Control_SearchBox Replace the value for the promt variable with the text that you want to display. Save the file. (If required publish and approve) Source - ...


1

Create result sources to limit the search results to the subsites only with the query like this: {searchTerms} path:http://sitecollection1/subsite1 Check this article: http://techmikael.blogspot.in/2013/04/limiting-search-results-in-sharepoint.html


1

There is an OOTB result sources called Documents, you can use that to limit the results to documents. For lists, create a result source with query like this: {searchTerms}contentclass:STS_List For list items, create a result source with query like this: {searchTerms}contentclass:STS_ListItem Check this article: ...


1

I think the problem relies on the nature of the search results web part. When you access the page from the browser the search results are returned from the server in JSON format. You can check this by using Fiddler and checking the response of the ASPX page. For obvious reasons, the crawler tends to ignore the contents of the "script" tags, thus not ...


1

I am currently tackling the same problem - there is a "no-code" solution for this entirely based on Display Templates - no deployment needed. a) Change the Search Box Result with your year filter b) adjust the Result Control and adjust the Data Provider. I got some inspiration from the following posts: ...


1

Okay here is what I implemented at the end. Add a Search Box webpart in that page. This webpart can be connected to the content search webpart, using webpart properties. Hide this webpart using CSS. Now in the content search webpart , edit the webpart properties and edit the query to accept data from the Search Box. On change event of dropdownlist , dump ...


1

Hi Mark it's hard to find documentation for this but at the end I resolved using this pattern: resultspage.aspx#Default={"k":"*","r":[{"n":"owstaxIdYourManagedProp","t":["cf32e33f-7ca2-470d-956b-29368e54e736"],"o":"OR","k":false,"m":{"cf32e33f-7ca2-470d-956b-29368e54e736":"TermName"}}]} It's important to note that: k:* basically it means "all documents" ...



Only top voted, non community-wiki answers of a minimum length are eligible