Hot answers tagged publishing-site
3
I would suggest the use of native policies (like in our case the expiration policy) that you can attach to a specific content type and trigger an action / workflow when the policy is met. In this case it will be when an item's age is reached. (eg : http://technet.microsoft.com/en-us/library/cc262112%28v=office.12%29.aspx)
What I've been doing for a customer ...
3
I prefer not to create sub-sites for navigational structure alone - mainly because it is hard to change the structure again. But you actually have some good alternatives when you are willing to create a custom navigation data source. Below are two options that will also not require you to create folders in your Pages library. They also make it harder to ...
3
The type of pages available by default (wiki vs. article and web part pages) is the primary difference.
Since wiki pages in 2010 allow for web parts to be inserted, many people are now choosing enterprise wiki sites over publishing sites. The only big thing you lose with wiki sites over publishing sites are page layout templates. Wikis have some basic ...
2
All good answers, I'll just add that both WebPart and UserControl are derivatives of System.Web.UI.Control, and as such are just two different tools in the same box.
Normal practice is to build the UserControl, then add a WebPart that simply loads it. This gives you both options for use.
In your case you are probably going to use UserControl since ...
2
It depends on what you want to achieve.
User Controls are controls which in general are ment to be statically placed on a specific pagelayout or masterpage. Like forinstance the QuickLaunch or GlobalNavigation are static controls in the masterpage, as they are ment to be shown on every single page, regardless of where you are on the site.
Webparts on the ...
2
Sorry Mihir I misread, you need to look at the MSDN real world branding post.
Code from MSDN:
<div class="customTopNavHolder">
<PublishingNavigation:PortalSiteMapDataSource
ID="topSiteMap"
runat="server"
EnableViewState="false"
SiteMapProvider="GlobalNavigation"
StartFromCurrentNode="true"
StartingNodeOffset="0"
...
2
If this is a publishing site (like i think you said it is), each user can decide whether to hide or display the ribbon. Maybe one user has selected to show it and the other one has decided to hide it.
See this old question for some screenshots: automatically show ribbon on publishing site
EDIT:
Are both users in the Site Members group? See this ...
2
Sounds like I am a little late with this response but you do not have to make it a publishing site just to apply branding. Most branding can be achieved with CSS which can either be applied at a site level or on specific pages as needed. If a custom master page is actually required then you can still access the page to select a master page using ...
2
It's hard to say as you did not specify number of users, number of wiki entries and overall planned size of these libraries. I would only opt. for separate site collections if you will have more than of 200 GB of content in each wiki.
This is how I would design it it:
Create a single site collection with a home page (root site)
Grant everyone permissions ...
1
After lots of blind trials and search, I had following finding:
The behavior that clicking "master pages and page layout" gallery in subset setting and being directed to the top level site "master pages and page layout" gallery is because, like the ressource here: ...
1
This may be an obvious answer, but it could be that you need to specify the approval users under the Versioning settings.
Under General Settings of the list/library, click Versioning settings.
In the Draft Item Security section, under Who should see draft items in this list or under Who should see draft items in this document library, click the group of ...
1
Maybe you can try this script? The script takes three parameters, the old or current page layout name, the new page layout name and an optional –all parameter which will traverse all the sites of a site collection.
# Description:
# Update the layout page for all matching pages of the current page layout
# Checkout, Change layout, Check-in pages in a site ...
1
Determine which lists are conflicting and rename the existing lists (sorry Grooverinthesouth, not trying to steal your answer, but yours is a comment :().
Depending on the list (columns) of the existing lists, you might also be able to export the list to Excel, and then import them back to a list with different name.
1
To be honest if you are running this locally, the object model is lacking in features for this and you are far better just calling stsadm for your needs, or even running the powershell from your code (Powershell is fully accessible) on a standard SharePoint installation.
so...
PowerShell ps = PowerShell.Create();
ps.AddScript("Add-PsSnapin ...
1
You can use SPWeb or SPSite to activate features on subsite or a certain site collection respectively. Here is an example of SPWeb.
try
{
SPWeb oWebSite = SPContext.Current.Web;
feature = oWebSite.Features[new GUID("94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB")];
if (feature == null)//if feature is not activated
...
1
You can just create an accouncements list on any site using "Site Action" | "More Options" and choose "Announcements"
Once the announcements list is created you can insert the list web part for it on any page.
If the site doesn't have the announcements list you can either active the visible Team Collaboration Lists feature or the hidden announcementslist ...
1
The variation mechanism will solely copy publishing pages from the "Pages" library and no other list. There are solutions (eg on codeplex) to increase the scopes of this process but it's not the expected native behavior.
You could try to refactor your process to either :
locate common information at the root of your site collection and have a language ...
1
I think that's expected behaviour. When you set-up Variation, only pages will be copied from source site to target sites. It does not includes lists etc.
If you are just beginning with Variations, I would recommend you read this: http://technet.microsoft.com/en-us/library/cc262404.aspx
So that you get a high level understanding of variation functionality.
1
Create a custom publishing site definition using Visual Studio solutions. Check out this link for instance: http://www.sharepointnutsandbolts.com/2007/08/creating-deploying-and-updating-custom.html.
1
I can't find it but I found this that I will quote for you because the page is a mess:
I found the answer. To make additional site Definitions or Site
Templates available in a site based on the Publishing Portal you need
to go to Site Actions > Site Settings > Modify All Site Settings. On
the Site Settings page click the Page Layouts and Site ...
1
If you place CSSRegistration for your custom css on first line and specify After property to corev4.css as shown in example below
<SharePoint:CssRegistration name="<% $SPUrl:~sitecollection/Style%20Library/Custom.css %>" After="corev4.css" runat="server"/>
<SharePoint:CssRegistration name="<% $SPUrl:~sitecollection/Style ...
1
The reason it did not work was because I was manipulating the AssociationData using XDocument. When I dumped the xml back into the string it attached
<?xml version="1.0" encoding="utf-16">
at the top which in turn caused the xml to be rejected in some weird way. Doing a regular string replace worked just fine.
1
The equivalent to a user control is a Visual Web Part, which is a web part based on a user control. This gives you all the advantages of the designer and markup editing, as opposed to a regular web part which follows the model of an ASP.NET custom control.
The advantage of building a web part, as opposed to just an ASP.NET control of either type, is that ...
1
The are different things :-
UserControls are intended as a way to package a.. well.. control.. to make it easy for developers to re-use in other parts of a project
WebParts are intended as a way to package a piece of functionality
for re-use in SharePoint by end users.
1
Can you describe what you mean by "issue"?
Related to #1, SharePoint 2007 does not support IE8 unless SP2 has been deployed. As long as your SharePoint 2007 environment is patched to SP2, then IE8 standard view is supported for both SharePoint 2007 and SharePoint 2010, so compatibility should not be required.
Related to #4, Medium-Low is the default ...
1
From what I can understand, you wants to automate a site creation process. Meaning to say that the created site should have some predefined settings according to your client request.
I have done something like that.
What I did was,
I created a new site (based on the Team Site template), modified that site design, create some new document library and add ...
1
http://vogtland.ws/markedwardvogt/?p=750
http://social.msdn.microsoft.com/Forums/en-US/sharepointworkflow/thread/404d5023-25e2-4ae1-a414-af89ab1084bd
http://social.technet.microsoft.com/Forums/en-US/sharepoint2010setup/thread/010a581b-3dd8-47b0-8f91-e0e5ecf7e201/
...
1
Though this thread is already marked as answer, still would like to add more to it. As mentioned above,"_IncludeSubsitesInNavigation" and "_IncludePagesInNavigation" properties can be added to the SPWeb property bag and made to work in sandbox scenario. Now these two properties are common for global as well as current navigation. For a scenario where we ...
1
I managed to solve this one today.
@Vardhaman is correct: the Microsoft.SharePoint.Publishing.dll assembly simply isn't sandbox compatible -- so none of the methods or properties in this assembly will work (even though Visual Studio doesn't throw any warnings or errors at compile-time!). If you reflect this assembly though, you can see that the navigation ...
1
The PublishingWeb class is a part of the Microsoft.SharePoint.Publishing library. This library is not allowed in the Sandbox. Instead of Microsoft.SharePoint.Publishing.PublishingWeb.Navigation, you can try using the Microsoft.SharePoint.Navigation class which is allowed in the sandbox.
Only top voted, non community-wiki answers of a minimum length are eligible
