Microsoft introduced a new feature in SharePoint 2013 called Cross-Site Publishing. This new functionality allows content in one site collection to be more easily shown in another site collection.
If you're like me, challenges are what make being a developer fun. Sometimes, however, these challenges can be daunting. With piecemeal information at one's fingertips, it can be aggravating to say the least to try to solve a vexing problem.
It’s important to properly manage how site collections are placed into content databases within a SharePoint Farm. This is because a content database size can negatively affect performance, especially when it grows to hundreds of gigabytes or even terabytes of data.
{#if $T.length == 0 && $P.root} <div class="no_cats"> <span>No Categories</span> </div> {#else} <ul class="cat_list" catId="{$P.parentId}"> {#foreach $T as cat} <li class="cat_item" order="{$T.cat.Order}" catId="{$T.cat.Id}"> {#if $P.select} <input class="cat_select" id="cat_cb_{$T.cat.Id}" name="cat_cb_{$T.cat.Id}" catId="{$T.cat.Id}" type="checkbox" /> <label for="cat_cb_{$T.cat.Id}">{$T.cat.Name}</label> {#else} <a href="{$T.cat.Url}" cat="{$T.cat.Name}" class='cat_link'>{$T.cat.Name}</a> {#/if} {#if $P.edit} <div class="cat_delete"> <a href="#" class="cmd_try_delete"><span>Delete</span></a> </div> <div class="cat_delete_confirm"> <span>Are you sure?</span> <a href="#" catId="{$T.cat.Id}" class="cmd_delete">Yes</a> <a href="#" class="cmd_delete_cancel">Cancel</a> </div> {#/if} {#if $P.edit && !$P.isRootBlog} <div class="cat_move"> <a href="#"><span>Move</span></a> </div> {#/if} <div class="cat_childs" parentId="{$T.cat.Id}"></div> </li> {#/for} </ul> {#/if}
<span>Parent category:</span> <select class="cs_blog_categories_list_dropdown"> <option value="-1">--</option> {#foreach $T as cat} <option value="{$T.cat.Id}">{$T.cat.Name}</option> {#/for} </select>
