Hot answers tagged

3

Can you: probably yes i can see no technical reasons for why not, but haven't triede it. Should you: probably not Remember that cross site publishing doesn't move the content, just information about it. So you'll store these documents in the My sites. In my opinion it would break the spirit of the "My Site" as a storage place and playground for the ...


2

Root site collection can mean one of two things depending on the context of the article you are referring to. It could mean the root of the environment, like http://sharepoint.domain.com or it could be referring to the root of your site, like http://sharepoint.domain.com/sites/hr.


2

It doesn't seem to be available in Standard edition. At least a couple articles showing that it's available only on Enterprise: http://blog.blksthl.com/2013/01/14/sharepoint-2013-feature-comparison-chart-all-editions/ Technet: http://technet.microsoft.com/en-us/library/jj635883(v=office.15).aspx Here's a link for someone that got the same error: http://...


2

When using external resources in the cross-publishing scenarios it is important to plan ahead access to shared resources - e.g. are all users on the target site have access to source images, etc. - I believe Waldek M. (http://blog.mastykarz.nl/easier-working-assets-cross-site-publishing/) has very well described this - an option being to effectively use a "...


2

I've found a way to accomplish this given a situation where the managed property value I need to make the secondary/related CSWP lookup happens to be exposed in the URL of the primary catalog item. I.e., a People Catalog with a catalog item URL of (/directory/Last, First) --- I want to show activities related to that person (from an Activities Catalog at /...


2

There are a few things you can try like: Export/Import Content deployment Cross-site publishing (new) If you're using SharePoint 2013, be sure to check out cross site publishing! In any case, you'll still have to deploy your customizations to both sides.


1

Yes it is possible. Cross site publishing utilizes search and the content search web parts for aggregating content from designated catalogs. Cross site publishing odes take some work to configure however -it's not just a single feature you turn on and start using.


1

I'm working on addressing this challenge myself and I share your frustration, though I think I understand why it works this way OOB. The content being rendered in CSWPs isn't actually "within the page" in the publishing site - it is all being retrieved and rendered client-side through Javascript. Basically, I think the limitation is fundamentally that ...


1

What I can think, Cross-Site Publishing Features itself is standard but it requires a couple of dependent features( one of them showed the error is SearchDrivenContent feature) are Enterprise edition. Also, this is part of the publishing site and automatically showed in the site collection features list. Maybe Microsoft thinks it is good to show people the ...


1

Self answering questions; just wait for a while then it's working properly!


1

Yes, this is possible but you have to do the mapping for the managed property and crawled property yourself. SharePoint does not automatically create managed properties for the following column types: Lookup Calculated Task outcome Summary Links data Rich media data for publishing


1

here are the steps: Activate the Cross-Site Publishing feature in SharePoint Now go to DL/list which you want use as a catalog.Enable a library or list as a catalog in SharePoint Do a full crawl of the content source that contains the catalog. See [Manually request crawling and re-indexing][3]. Enable the SharePoint Server Publishing feature on the ...


1

It sounds like your urls aren't being rewritten. When you connected the remote list to your publishing site did you tick the box to "Make URLs relative to this site"? This video around 49:45 talks about it. Anonymous access only grants the search index the ability to share the content without requiring security checks. This video has more about it around ...


1

The solution for this ended up being a custom implementation. We enabled ratings and likings on the list that contained the items in the Authoring site, and then created a custom implementation that applied the likes to the items on that list. So the detail Page on the Publishing site collection wasn't liked or rated, the items in the authoring sites were.


1

When you create a catalog connection in SharePoint 2013, the following items get configured for you automatically: Result Source Managed Navigation Catalog Category Page Catalog Item Page When using BCS External Content Types, you have to configure all of the items above manually but it is definitely possible. These are some high-level steps: Create ...


1

No - there is nothing like this out of the box. You can develop something like this depending on what you need to push. If the environments are the same, you can rely on the export / import methods for merging content, but that wont activate features for you. If content is the same and there is no threat to overwriting production, you can move the ...


1

I found my way arround - I extended ContentBySearchWebPart webpart in a way that it modifies query string before querying sharepoint. It goes recursively by navigation terms from current up to root and per each node, one condition is added. Conditions are added to place in query string marked by string, so the condition can be enabled/disabled from UI. ...


1

If you create a new managed property you must run a full crawl before it becomes available. You don't necessarily need search to do a traditional full crawl of all content though - you can force it to just do a full on your intended site. In the settings for the library where the look up column exists, under advanced settings there is button to Re-Index ...


1

Modify the existing managed property "Title" and select the option to make it Sortable. Then run a full crawl. It will be easier to identify the Title field rather than reuse a RefinableString or create your own managed property. After the full crawl is complete, you should be able to select Title as a sortable property in the web part.


1

The answer is that children of a Top-Level Term are reused automatically but a new Term and all it's children must be added manually. So in order to have a proper Navigation if you want to reuse it from your catalog make sure that the Term-Store is set up on a pretty final version (at least all "top level" Terms should be included there).


1

The options are right in front of you. "Restrict by App" - At the moment you have it set to 'Current Site' which is actually 'Current Web'. You would need to remove this restriction to access the full index. Switch to Advanced Mode, ensure we are looking at Local SharePoint Results source and remove the query in the box. Add the following: Path:http://...


1

Create an External list and add a list view webpart. You will have the SharePoint user experience. You can use SharePoint Designer as well as Visual Studio for this. This is how to do using Visual Studio: Create SharePoint 2013 External List using Visual Studio 2012 Create an External List Using C# Modifying BDC Model Entity in Business Connectivity ...



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