Tag Info

New answers tagged

0

You can do it in a couple places, it makes the most sense to me to include these as search exclusion rules within CA. This helps trim down your index, making it more relavent. This would be done by creating rules that exclude content like *://*allitems.aspx*. If you are doing this on a search results page, you'd do it like Steve Mann demonstrates in this ...


0

It looks like you hard coded loadsiteframe to false so the LoadSiteViewer is not getting called. Try debugging the JavaScript and see what happens when you change it to true.


2

So I figured out that the html for the "PurchasingSearch" page was not published. Both the .js and the .html need to be published.


0

The Search Query Tool (SQT) and SharePoint webparts use the same API to retrieve the results. Could you use the standard "local sharepoint results" result source and put in your query? It should then give you the same result as with SQT, right? If so, your result source is broken. If not, use the Live Monitoring on-premise tool (bundled with SQT) to see ...


0

I discovered there are a number of things you have to check out. Provision User Profile Service and Synchronization (I did this) Configure My Sites with self-service site creation Provision the Search Service Application (I did this) Grant Service application service identity privileges to search for people and profiles inside the UPS (go to Manage service ...


0

I would check and make sure you don't have any best best / promoted results configured. If it's a natural search result - you may have to reset your index and then do a full crawl. EDIT You may be able to remove items directly. When you review your crawl logs do a search for this item via URL. If you select the item in the log there is an action there to ...


2

You can use following query to get the result path:"https://siteurl" (ListID:{CC6FB9E2-92CE-444E-85C7-2E126DFF9ED0} OR contentclass<>SPListItem OR) The above query will give you all results which are not of type SPListItem. If you observe there is an OR condition where we are including search results from a single list. So in your case you should ...


0

You can handle the OnPreRender handler. Here is a pseudo code you can try with ctx.OnPreRender = preRenderHandler; function preRenderHandler(ctx) { //Get the Page's user is following here //Remove the result here by accessing ctx.ListData.ResultTables[0].ResultRows } While retrieving Followed pages data you should hold back the call by ...


0

Funnily enough I had the same issue today. But it resolved after I removed all Content Sources and cleared the index and tried setting up a crawl.


0

I would crawl the list (best case is create a new content type for the list item.) Then create a display template that shows the details you prefer and associate a Result Type rule for the content type to show the display template.


0

You do not need to create display template for each result type. Instead, you can create your own result type and one display template for this result type. When creating the result type for the sitecollection - do not specify any additional conditions. In this case it was used by default, and the results will be applied to your display template.


1

Their are couple of ways you can do it. Method # 1 ( i am assuming you have the same kind of web application) take the backup of content DBs from Stagging restore into Dev farm, Detach the Old DataBase from SharePoint Dev farm Web App and Attach the New DB(stagging) deploy any solutions if you have. Make any changes to Web .config(if any). Method # 2 ...


0

Actually the incremental crawl must have not taken place so you can see the items in search. Try to do full crawl to verify the searhc results.


1

One option that comes to my mind is using jQuery. On page load check if the search box has any values, based on that Show/Hide the results. Something like jQuery(document).ready(function(){ var searchValue = jQuery('#searchboxid').val(); if(searchValue == null || searchValue == '' || searchValue == 'Search...') { jQuery('#webpartid').hide(); ...


0

Can you not find the document via All files --> Document library and edit its metadata from there?


3

The ideal way is to edit the document library view and add additional columns on which you can filter and find the document. Another option is to modify the search results webpart and enhance the results view to add an extra link to (Edit/View) document properties. Here is a sample XSLT I took from this site <!-- A custom template to display a link to ...


1

I am very embarrassed, but it looks like that search development just needs a lot of patience and carefulness. It looks like two things might have worked here for me: The first one Save the template file and navigate to the site collection Search Result Types settings page. A warning "Property Sync" should be visible - click on the suggested "Update" ...



Top 50 recent answers are included