Tag Info

New answers tagged

0

Fetched Properties property in People Search Core Results web part editor corresponds to CoreResultsWebPart.SelectColumns property.


3

The real answer here is to create a result source where you for "Type" choose "People Search Results". You don't need to add ContentClass=urn:content-class:SPSPeople For example: {?({searchTerms})} {?OR (({searchTerms}) spcontenttype:contact)} will give people + results of contenttype=Contact When testing this in the query wizard it will append ...


1

Check the result sources: People: {?{searchTerms} ContentClass=urn:content-class:SPSPeople} Local Content: {?{searchTerms} -ContentClass=urn:content-class:SPSPeople} For local the minus in front of the content class excludes the people results. For people the contentclass excludes your list. Create a copy of the people result, add your custom list ...


0

Update: It resolved itself "magically", no idea why it just decided to work but it could be work behind the scenes (read: network sec) that I did not know of but nevertheless it was resolved.


1

You need to make sure you also run at least Incremental search crawl after profile update for the content source containing source starting with address sps3://, where is the URL for the Web application where you deployed the My Sites site collection.


0

Below function is working . you can put either in master page or in .js file that is reference in master page. $(function () { var theSearchBox = $('ctl00_PlaceHolderSearchArea_ctl00_S3031AEBA_InputKeywords'); var ctl00_PlaceHolderSearchArea_ctl00_ctl04 = '0'; var preferredSearchText = "Enter Search Term"; ...



Top 50 recent answers are included