Site Template and webparts in Publishing Pages

Hi
I've created a couple of webparts in SPD and added these to the pages in the Pages Library (Publish). I then export the site as a template (switching publish off first) and create a new sites from the template. Unfortunately the weparts are missing from
the publish pages but are available in the new site Webparts Gallery. The Site Pages have the Webparts available but the Publishing pages dont. When I exported the SC root web I switched off publishing for the site.
Why aren’t the weparts appearing on the page created in Pages Library. Ive switched on publishing now in the new site but its made no difference. ?
I found this blog but it doesnt appear to provide a solution :http://blogs.technet.com/b/stefan_gossner/archive/2007/09/19/save-site-as-template-option-and-the-publishing-feature.aspx
Thanks

As I said, templates are not supported when you turn on publishing. That's why there is no "save site as template" link after you turn on Publishing in a Site Collection. I assume you are using one of the hacks to navigate directly
to the page that lets you save the site as a template, since the link isn't there. That will work for some sites, but clearly won't for yours. There is no workaround. Site Templates aren't supported in Publishing environments because they
aren't reliable. If you want Page layouts then you need publishing. If you use publishing then you can't use site templates.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Similar Messages

How to programmatically add webpart to publishing page

How to add visual webpart in publishing page please let me know.
Thanks in advance

public void AddTaskListsWebPart()
            SPLimitedWebPartManager manager = null;
            SPFile file = null;
            try
                SPSecurity.RunWithElevatedPrivileges(delegate()
                    using (SPSite spSite = new SPSite(site id))
                        using (SPWeb spWeb = spSite.OpenWeb())
                            spWeb.AllowUnsafeUpdates = true;
                            file = spWeb.GetFile(pageurl);
                            if (file.CheckOutStatus == SPFile.SPCheckOutStatus.None)
                                file.CheckOut();
                                manager = file.GetLimitedWebPartManager(PersonalizationScope.Shared);
                                if (manager.WebParts.Count <= 0)
                                    TaskLists objTaskLists = new TaskLists(); //Replace
TaskLists with your webpart name
                                    manager.AddWebPart(objTaskLists, "zone1",
0); //replace zoneid and index with yours one.
                                    manager.SaveChanges(objTaskLists);
                                    //pnlTaskLists.Controls.Add(objTaskLists);
                                    file.Update();
                                    file.CheckIn(string.Empty);
                                    file.Publish(string.Empty);
                                    spWeb.Update();
                            spWeb.AllowUnsafeUpdates = false;
            catch (Exception ex)
                Utility.SPTraceLogError(ex); //Handle your error as per your logic
            finally
                if (manager != null)
                    manager.Dispose();

What is difference between Site template and web template

What is difference between Site template and web template

Both are almost same, are you referring to Site Definitions vs web template?, if so, refer to the following post
http://blogs.msdn.com/b/vesku/archive/2011/07/22/site-definitions-vs-web-templates.aspx.
--Cheers

May Release: New partner support, Infrastructure updates, Site templates and bug fixes

Link: http://www.businesscatalyst.com/_blog/BC_Blog/post/May-release-New-partner-support-Infrast ructure-updates-Site-templates-and_bug-fixes/
We are announcing a new Business Catalyst release, scheduled to go live on Thursday, May 3rd. With this release, we are continuing our investments in system performance and stability by increasing our web servers capacity, enabling HTTP acceleration to provide faster site loading times, and improving the site creation speed by using pre-generated sites.
On the product side, we have completely revamped our partner support workflow taking advantage of the Adobe support infrastructure and tools, enhanced the site templates workflow for partners, and included lots of bug fixes and improvements. Read through the following sections to get detailed information about this release:
Partner support
Infrastructure updates
Features and enhancements
Issues fixed by this release
What's next
You can jump to the corresponding section by clicking the above links.
Partner support
Updated Help & Support partner experience
Following Adobe ID support, we have upgraded BC support tools (cases, chat, documentation) with standard Adobe tools. As a partner, you can now benefit from the same support tools as the rest of Adobe Creative Suite, and can track your support cases with Adobe BC, Dreamweaver, Muse or Photoshop in a single place.
Partners with more than 100 paid sites will get 2nd level chat support, which includes a higher priority, by default. If you have more than 100 paid sites, but spread across different Partner Portals, please ask support to enable 2nd level chat for you.
Support experience for your Small Business owner clients can now be owned by partners (see below).
Custom Help & Support URL for your clients
As a partner, you are probably already offering various additional services to your clients besides building & maintaining their BC site. Support, tailored specifically to your client needs, is usually one of these value-added services. We are now enabling you to take your Support service to the next level. In Partner Portal Settings, you have the option to set a custom URL for what will open when your client clicks on Help & Support inside Admin Console:
If you have multiple partner accounts, for different verticals, you can specify a Support URL for each of these.
The default Support experience provided by BC for your clients will be updated in a few releases to be similar to the partner support experience. This includes BC-branded support cases and documentation. If you'd like to keep a white-label experience for your customers, please set your own Help & Support URL in Partner Portal.
For more details please read the Improved support workflow and new forums announcement on our blog.
Infrastructure updates
Between our April release and the following infrastructure updates have been enabled
Limited trial sites for free partners – starting with our May release, the number of trial sites a Free Partner can have will be limited to 100. Once the limit is reached, Free Partners that need to create a new trial site have the options to upgrade to a higher partner plan, upgrade some of the trial sites to paid or delete unused/expired trials.
Automatic trial expiry extension - with this release, trial site expiry date will be automatically extended with 30 days every time an admin user logs in the system through the admin interface or through FTP.
Installed additional hardware - we have installed additional web servers on all our data centers, that translate into an increase of the existing capacity with over 70%.
Updated DNS infrastructure - we have improved the DNS resolution for email delivery so that we can increase the rate at which we're sending the system operational emails
HTTP acceleration – all sites static assets are served from a new cache engine (images, CSS and JavaScript files, together with improved headers that should allow the browser to cache them better for a browsing session). This update has been turned on along with our April release, and has made all the BC sites load faster on first and on subsequent loads.
Accelerated site/partner creation – we've changed the way new sites are created for faster speed, pre-creating them and reusing pre-created sites when needed, and have also improved the creation process for new partners, minimizing the impact of new CCM customers on the existing datacenters.
Adobe ID for partners - in order to support an integrating experience between the various Adobe tools a partner may use (Dreamweaver, Muse, Support forums) we have added Adobe ID support for Business Catalyst partner accounts. Starting April 19, partners are asked to merge their current Business Catalyst account with their Adobe ID accounts. For more details about the transition process and FAQ please read the Introducing Adobe ID blog post.
Updated Terms of Use - Along with several other changes in our processes in the past few months, we also revamped our Terms of Use and the signature process by requesting every admin user to sign a TOU. We have completed the rollout for partners, and we might be pushing an updated partner Terms of Use version within the following weeks. For more details and questions about this change, read the New Terms of Use for Business Catalyst blog post.
Features and enhancements
Site templates
To support the increasing number of partners building, sharing or reusing templates to create new sites, we're extending our site templates support from our partner portal with a new template type and improved management support. The update is going to enable partners to mark sites as templates and choose between making them available in Online Business Builder and keeping them private in their partner portal. A template site will not expire and has the same limits as any other trial site.
Based on your partner level, you can create private or public templates using the Site Details screen or the Tools>My Site Template section from your Partner Portal. Standard partners can only create private templates, while Free Partners can only view site templates that have been transferred to their accounts by other partners.
The number of templates a partner will have will be limited and will vary based on partner level: free partners can store up to 5 templates in their partner portal, standard partners have up to 100 site templates while Premium Partners might have up to 200 templates. Paid sites marked as templates are not counted against these limits.
Business Catalyst Partner fixes
While we are really focused on making the Business Catalyst integration into Creative Cloud a smashing success, we are slowly resuming our efforts to deliver fixes that have been requested by our partners. This release includes the following partner fixes:
Improved product custom fields - we have increased the maximum number of characters for product custom fields to 1024 (previous limit was 256); this gives partners and customers additional space to use when working with products
Improved Secure Zone subscribers list - we have added the customer email address in the Secure Zone Subscribers list to enable partners better filter and manage customers
Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
Social plugins integration updates
Starting with our May release, we are updating the social plugins support to require users to get the plugin code from the third party provider and saving into his Business Catalyst website. The module tags and configuration will remain unchanged, but will render an empty tag until the partner or site owner will update the module template to include the corresponding module code snippet from the third party platform provider.
For more information about how you can enable the Social Plugins on a Business Catalyst websites, read the Social Media: Integrating Facebook and Twitter knowledge base article.
Other changes
Updated weekly emails - Starting with our May release, the information in the site weekly emails has been filtered based on the site's plan. For example, webBasics site reports will no longer include the sales report.
Localization - we improved and increased the coverage of the admin interface translations into German, French and Japanese
Site Settings -> Ignored IP addresses has been relocated under Reports -> Visitors -> More.
BC-Dreamweaver integration performance improvements
Development Dashboard has been removed, as it didn't provide a clear useful, ongoing benefit. The information present in the development dashboard has been integrated into our new Help & Support section.
Payment gateway settings - for more privacy and data protection, we have updated the Payment Gateway configuration screens to obfuscate the sensitive login information. Fields that have been obfuscated are now requiring confirmation.
Report abuse badge on trial sites - for compliance reasons, a "Report Abuse" link has been added to the front-end of all trial sites of free partners that don't have any paid sites. When they click the Report Abuse link, site visitors are redirected to a form submission page on businesscatalyst.com site.
Issues fixed by May release
Issues 3051303, 3168786 - Workflow notifications - Fixed a problem preventing workflow notifications emails from being sent.(see get satisfaction forum discussion)
Issue 3164074 - Fixed a bug causing the lightbox gallery created from Muse to be displayed behind page elements
Issue 3162810 - Fixed a bug in rendering engine to prevent content placed between body and head tags being incorrectly moved inside the body tag
Issue 3166610 - Fixed a broken link to Partner Portal in Internet Explorer
Issue 3175003 - Fixed an issue that caused an incorrect price display for the Year One-Off Setup Fee when upgrading a site from Admin using CB
Issue 2567278 - Fixed a bug causing site replication to ignore product attributes
Issue 2947989 - CRM passwords are now case sensitive
Issue 2723731 - Removed CSS files from the head section of the Layouts files, when downloaded and opened in Dreamweaver, via the BC extension
Business Catalyst new admin interface updates
Added "Save and Add New" button in Web App Item Add & Edit screens (see get satisfaction forum discussion)
Updated Quick Actions menus to add more actions (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to display deleted items (see get satisfaction forum discussion)
Fixed a display issue on File Manager making top buttons unreachable (see get satisfaction forum discussion)
Fixed the scrollbars in Email Marketing>Campaign>Stats>Bounced Emails reports (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to brake after selecting the current page from the Recent Items menu (see get satisfaction forum discussion)
Replaced the Success notification displayed when selecting Users or Permissions tabs from User Roles with an Warning
Change the action label displayed in User Roles list from View to Edit to match the list pattern from Admin Users
Fixed a missing file JavaScript error occurring when trying to open image manager from product details-> Attributes -> options
Moved System Emails section from Site Setting to Site Manager (see get satisfaction forum discussion)
Updated Domain Management interfaces to close the modal window and refresh the domain list after successfully adding a domain
Fixed an issue preventing the Hyperlink Manager to function properly (see get satisfaction forum discussion)
Updated the confirmation message received after copying a page to match the new workflow and button names
Fixed an issue causing the current screen or section to not be highlighted in the menu
Updated styling on the new dashboard, user management and email accounts interfaces
Updated dashboard reports filters and chart display; made the chart and the filter use the site time zone
Fixed an issue preventing users from inviting new admin users or create new email accounts on Internet Explorer 8
Fixed an issue preventing users from deleting Email Accounts or Admin Users in Internet Explorer 8
Fixed some issues preventing password recovery email from being sent
Removed the alert message displayed when the user or email account limit has been reached
Added localization for the simplified dashboard
Fixed display issues for site limits, domains and user list in the simplified dashboard
Added Custom reports for webBasics plan
Fixed a bug generating a "500:Collection error" on the simplified dashboard when user did not had View users permission
Added TOU checkbox in the email account setup screen
Updated Site Preview link in the dashboard to load the default domain
Fixed an issue in the new File Manager forcing a user to press Undo twice in order to see the change take effect if the code that was previously formatted contained any <"tag" with more than 2 lines
Fixed an issue causing the File Manager editor toolbar to incorrectly render if page URL path is longer than certain value; starting with this release, the site URL is trimmed
Fixed an issue causing the invite users to be displayed as [object Object] in dashboard and admin user list
Fixed a bug in the new admin causing the interface to become unresponsive when using the browser Back button
Fixed an issue in the new File Manager causing "Save Draft" button to publish the default page template instead of creating a draft version
Fixed a broken invite link issue in the Email Account invite email
Updated loading indicators in File Manager and Email Accounts screens
What's next
The first item on the what's next list might not be news for many of you, but it's definitely one of the most important milestones this year. The Creative Cloud launch is just around the corner, and Business Catalyst is playing an important role in that, as the publishing platform for Adobe® Muse and Dreamweaver. This launch will capture all our attention within the next weeks as we want it to be our best ever.
We'll start our next development cycle on May 15th, while the next Business Catalyst release is going to be pushed live in mid June. That being said, the following items are already on our launch plan for the next release and a few more will join the list. Please expect an update on our 2012 plans around mid May.
HTTP throttling – all page load and API calls to BC will be protected against attacks, this might trigger problems for API heavy sites. We are looking into enabling this update along with our June release, and will help make sure that a reasonable number of requests will be accepted from the same computer per minute.
Automatic site deletion - Starting with the June release, we are going to start automatically delete expired trial sites and canceled sites. Customers will be notified twice before we are going to proceed with deleting the sites.
Thank you,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

How to place a WebPart in Publishing Page Content

Hi,
when you use a publishing page you are able through the ribbon to add existing webparts into the content of the publishing page.
I would like to add programmatically a webpart into the content of the publishing page. I couldnt find anyting to that question on the web.
Can someone help?
regards
yavuz
Regards
Yavuz
www.ybog.net | Field notes on software development and technology

Try below:
http://sharepoint2010mind.blogspot.in/2012/06/add-webpart-programmatically-publishing.html
http://sharepoint.stackexchange.com/questions/86026/add-programmatically-custom-web-part-to-page-without-web-part-zone
PublishingWeb pWeb = PublishingWeb.GetPublishingWeb(web);
string pageName = "NewPage.aspx";
PageLayout[] pageLayouts = pWeb.GetAvailablePageLayouts();
PageLayout newPage = pageLayouts[0]; //Body only type of page layout
PublishingPageCollection pages = pWeb.GetPublishingPages();
PublishingPage nPage = pages.Add(pageName, newPage);
nPage.Update();using (SPSite site = new SPSite("http://win2008/sites/publishing"))
SPWeb web = site.RootWeb;
SPFile page = web.GetFile("Pages/Lipsum.aspx");
page.CheckOut();
using (SPLimitedWebPartManager wpmgr = page.GetLimitedWebPartManager(PersonalizationScope.Shared))
Guid storageKey = Guid.NewGuid();
string wpId = String.Format("g_{0}", storageKey.ToString().Replace('-', '_'));
XmlElement p = new XmlDocument().CreateElement("p");
p.InnerText = "Hello World";
ContentEditorWebPart cewp = new ContentEditorWebPart
Content = p,
ID = wpId
wpmgr.AddWebPart(cewp, "wpz", 0);
string marker = String.Format(CultureInfo.InvariantCulture, "<div class=\"ms-rtestate-read ms-rte-wpbox\" contentEditable=\"false\"><div class=\"ms-rtestate-read {0}\" id=\"div_{0}\"></div><div style='display:none' id=\"vid_{0}\"></div></div>", new object[] { storageKey.ToString("D") });
SPListItem item = page.Item;
string content = item["PublishingPageContent"] as string;
item["PublishingPageContent"] = content.Replace("|", marker);
item.Update();
page.CheckIn(String.Empty);
http://sharepoint.stackexchange.com/questions/86026/add-programmatically-custom-web-part-to-page-without-web-part-zone
http://www.zeemanj.net/?p=291

How to programmatically add timeline webpart to publishing page

Can we add timeline webpart programmatically?
If yes then please let me know how we can add it?

Hi Jason,
Thanks for your reply. It helped me lot but i want to add something to your code.
1) Added web.AllowUnsafeUpdates to resolve error of disallow to update.
2) Added TimelineType and SourceSelection properties else it shows add setup properties of webpart
3) manager.WebParts.Count >= 0 Added condition else on every request it adds control.
Also i want to know few line of code from your answer:
1) What is the purpose of using storagekey? Why it is needed?
2) Why you update page items?
try
                using (SPSite site = new SPSite(SPContext.Current.Site.ID))
                    using (SPWeb web = site.OpenWeb(SPContext.Current.Web.ID))
                        web.AllowUnsafeUpdates = true;
                        SPFile page = web.GetFile("/Pages/Home.aspx");
                        page.CheckOut();
                        using (SPLimitedWebPartManager manager = page.GetLimitedWebPartManager(PersonalizationScope.Shared))
                            if (manager.WebParts.Count <= 0)
                                SPTimelineWebPart timelineWebPart = new SPTimelineWebPart();
                                timelineWebPart.TimelineType = SPTimelineWebPart.TimelineTypeTaskList;
//Task type list
                                timelineWebPart.SourceSelection = "Tasks"; //list name
                                manager.AddWebPart(timelineWebPart, "timelineZone", 0);
                        page.CheckIn(string.Empty);
                        page.Publish(string.Empty);
                        web.AllowUnsafeUpdates = false;
            catch (Exception ex)
                lblError.Visible = true;
                lblError.Text = ex.Message.ToString();
Once again thanks for your reply. Please if you can resolve my queries then please reply it.

DW Template and table jump from page to page

Hi,
I have put together a rather quick, basic site for a friend
in need (meaning=bare bones here to get it started faster). It's
template-based and table-based.
The site is generally working okay except that the content in
terms of the tables jumps slightly to the left or to the right
during navigation between pages. It all hangs together, but it
shifts slightly, so I know something is out of line.
The navigation is done with Fireworks CS3, so there may be
something wrong with how my slices are set up. I've tweaked them a
bit and made them better, but everything still shifts between
pages.
I appreciate any help or assistance anyone could offer.
Here's the Url:
Billy Marcus Website
Many Thanks, Frank B.

I saw no evidence that this was occurring. Or maybe I looked
after you
fixed it? Looks like it.
Replace what you have with this -
:root { overflow-y:scroll; }
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"brightbelt" <[email protected]> wrote in
message
news:gngtao$a86$[email protected]..
> Thanks, I found the answer in this forum search.
>
http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?forumid=12&catid=189&threadid =1420064&highlight_key=y&keyword1=pages%20jump

Publishing Site Template

Hi..
1. We created new publishing site Template and we did not find any Web Part Pages to add in Site Pages ( until we go and add in SharePoint Designer ) . Only Pages are available. So how to add web Part Pages in SharePoint 2013 for a new Publishing
Template Site without Designer.
2. Created a new Master Page from Design Manager for Publishing Site, when we set customized master page as default.
New Styles are applying only for Web Part Pages but not for publishing Pages ..so how to have styles for all the pages in it.
Ravindranath

Hi,
According to your post, my understanding is that you want to add web part pages in publishing site.
We can enable the Wiki Page Home Page site feature, it will create a Site Pages library, then you can add the web part pages in the site.
To enable the Wiki Page Home Page feature: Site Settings->Manage site features->Wiki Page Home Page.
For the second issue, you can check the master page reference for the publishing pages to make sure they have referred to the custom master page.
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Cannot publish Webpart - "Invalid SPlistItem. The SPListItem provided is not compatible with a Publishing Page"

Hello All,
I have seen this error message discussed in other posts on the forums here but the solution of deactivating and reactivating server publishing/infrastructure are not working for me. In fact I encountered additional errors when reactivating publishing at
the site level. Powershell was necessary to reactivate site level server publishing.
Here is detail of the error I get when attempting to publish:
Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 18/11/2014 08:59:05
Event time (UTC): 18/11/2014 08:59:05
Event ID: e2e43649e2164e399fe0aa85892a002c
Event sequence: 165799
Event occurrence: 17
Event detail code: 0
Application information:
Application domain: /LM/W3SVC/1827921427/ROOT-1-130607489469090399
Trust level: WSS_Custom
Application Virtual Path: /
Application Path: C:\inetpub\wwwroot\wss\VirtualDirectories\portal.cooperstc.com443\
Machine name: CTCSP2
Process information:
Process ID: 7392
Process name: w3wp.exe
Account name: COOPERS\svcSPPortalAppPool
Exception information:
Exception type: ArgumentException
Exception message: Invalid SPListItem. The SPListItem provided is not compatible with a Publishing Page.
Request information:
Request URL: https://portal.cooperstc.com:443/CLG/Student/Videos/Pages/Test101.aspx
Request path: /CLG/Student/Videos/Pages/Test101.aspx
User host address: 10.33.50.119
User: COOPERS\yangro
Is authenticated: True
Authentication Type: Negotiate
Thread account name: COOPERS\svcSPPortalAppPool
Thread information:
Thread ID: 41
Thread account name: COOPERS\svcSPPortalAppPool
Is impersonating: False
Stack trace: at Microsoft.SharePoint.Publishing.PublishingPage.GetPublishingPage(SPListItem sourceListItem)
at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageStateControl.RaisePostBackEventForPageRouting(String eventArgument, SPRibbonCommandHandler control, RaisePostBackEventDelegate raisePostBackEventDelegate)
at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageSaveAndStopEditHandler.RaisePostBackEvent(String eventArgument)
at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

DeActive and then ReActivate Sharepoint Site Publishing Infrastructure feature at both Site And Web level Scope.
To Deactivate at web level, Open SharePoint Site. Click on Site Actions -> Site Settings, then click on Manage site features and then Deactivate Publishing Infrastructure feature.
Similarly you can deactivate at site level, Open SharePoint Site. Click on Site Actions -> Site Settings, then Site collection administration and then go to Site collection features. there deactivate Publishing Infrastructure feature.
To Reactivate again the feature, follow the above steps.
http://www.c-sharpcorner.com/Blogs/15338/invalid-splistitem-the-splistitem-provided-is-not-compatibl.aspx
1.The simple thing is to try deactivate and reactive the publishing features both at site collection and site level.
2. If the above doesn't work then proceed to below PowerShell script.
$site = Get-SPSite "http://www.mysites/ "
$web = $site.openweb()
$correctId = $web.Lists["Pages"].ID $web.AllProperties["__PagesListId"] = $correctId.ToString()
$Web.AllProperties["__PublishingFeatureActivated"]="True"
$web.Update()
3. The key point is PublishingFeatureActivated bag which has to be true .
http://webcache.googleusercontent.com/search?q=cache:5xpx-C9kKgsJ:nagendra-gunaga.blogspot.com/2013/11/the-splistitem-provided-is-not.html+&cd=4&hl=en&ct=clnk&gl=in
If this helped you resolve your issue, please mark it Answered. You can reach me through http://itfreesupport.com/

Remove reference to Publishing Feature from site template

Hi all, I have a custom site collection which I package as a wsp to deploy as a custom solution template to multiple sites.
Accidentally, years ago I've activated Publishing Features in my site template and then disabled them. I still work and create new templates from my site without any problems (ShP 2010).
Now, I've installed SharePoint 2013 and updated my site template to 2013. Then, I've created the new wsp but when I try to apply my template to a new site collection I receive an error message: "Failed to instantiate file "AlternateMediaPlayer.xaml"
from module "Style LibraryMedia Player_Features\PublishingResources": Source path "Features\PublishingResources\AlternateMediaPlayer.xaml" not found."
How could I remove all the reference to features belonging to Publishing Features?

Hi Elena_B,
According to your description, my understanding is that you want to remove reference to publishing feature from site template in SharePoint 2013.
You can do as the followings:
extract all files from WSP file by (a tool or) changing the wsp file to cab file and then extract all files to a working folder.
edit the Onet.xml file to remove the unsupported features and save the changes.
create a ddf file for makecab.exe to repack the wsp
run cmd: makecab /f my.ddf to generate the new WSP file
More information, please refer to the link:
http://lassewikmark.wordpress.com/2009/11/16/howto-remove-unused-features-from-a-site-template-file/
http://social.technet.microsoft.com/Forums/sharepoint/en-US/37e96410-7fb9-462b-a3e7-c150f2de7107/site-template-and-disabled-feature?forum=sharepointadminprevious
I hope this helps.
Thanks,
Wendy
Wendy Li
TechNet Community Support

Publishing Site template problems

Has anyone come across this. Can you offer some insight.
A site collection administrator has created a new site using the Publishing site template.
Not long after the site is created, all sites under that web application slows down. At first all users noticed the problem. However, after a while it only affects other site collection administrators and farm administrators. Other users don't see a problem.
We deleted the site and the issue went away.
After some testing we found that she could create the site with the blank site template and this didn't cause problems.
Another post was very helpful. It suggested that there was a problem with the draft version of the default.aspx. But why would it work with the blank site template?
Does anyone have any suggestions on how we can troubleshoot this.
The logs don't show very much. The only thing that led us to the problem was that the site kept showing up in the logs when i turned on verbose logging. I was going to try fiddler but I haven't been very successful using this in the past. Does anyone else
have any ideas.
LSTalbot

Hi,
As the web application stopped working after creating the publishing site, there might be some issue caused this case.
Could you please check the event log and ULS log to see if anything unexpected occurred?
To check event log, click the Start button and type “Event Viewer” in the Search box.
For SharePoint 2010, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS.
You can check the ULS log by the methods here:
http://blogs.msdn.com/b/opal/archive/2009/12/22/uls-viewer-for-sharepoint-2010-troubleshooting.aspx
http://msdn.microsoft.com/en-us/library/gg193966(v=office.14).aspx
Thanks,
Victoria
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Victoria Xia
TechNet Community Support

Can enable a site template for subsites via editing webtemp.xml but how do I change in my solution files?

I have a template wsp that I deploy then create a new top level site. The template is available perfectly.
I then try to create a subsite and the template isn't available. So I went to .../14/TEMPLATE/1033/XML/WEBTEMP.XML
I added in my template...
<Template Name="MYTEMPLATE" SetupPath="SiteTemplates\MyTemplate" ID="202">
<Configuration ID="0" Title="My Site Title" Hidden="FALSE" ImageUrl="" Description="A site I created."></Configuration>
</Template>
Now after an IIS reset the templates show under the "Custom" tab perfectly.
BUT the question is what file do I change in my actual solution files before I package everything up? What would add this to the webtemp.xml automatically for me when my solution is deployed?
Thanks,

The terminology is confusing, but what you are actually adding is a "Site Definition". Site Templates are .wsp files that can be saved as a snapshot of an existing site for re-use. These .wsp files are stored in the site template gallery of a
site collection. There are also Web Templates that are similar to Site Definitions since they use an ONET.XML file, but they are activated using a Feature. Together Site Definitions, Site Templates, and Web Templates are known as Site Templates
in the User Interface. But each one is deployed and activated differently. Site Devfinitions are normally added to the environment by using Module features to deploy the site definition in its own subdirectory where the other site definitions are
stored. A custom webtemp file is also deployed instead of editing the existing file. SahrePoint will pick up any file that is stored in that location that starts with webtemp and ends in .xml. So you can deploy a new webtemp file called Webtemp_custom.xml.
If you are actually deploying a site template then you just upload it to the site template gallery of the site collection. If you still aren't seeing it in the custom tab then its probably because the root site has restricted the available site templates
for creating subsites. This is common in Publishing sites, but can be done in any site. In Publishing sites there is a link on the site settings page that you can use to select what site templates are available to create sub sites. In non-publishing
sites it requires powershell
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

Issue with AjaxControlToolkit for SharePoint 2013 Blog site template.

Hi,
Please find below the details of issue -
History - We are working with SharePoint 2013 and we are using AjaxControlToolkit in our project. Basically this is a migration project from MOSS to SharePoint 2013. So we have migrated code MOSS to SharePoint 2013. Previously in MOSS project, AjaxControlToolkit
was used so after migrating we have also used AjaxControlToolkit with updated version which can work in SharePoint 2013. This is working fine now.
Scenario - There is one web application in SharePoint 2013 farm. Under this web application there are two site collections. One site collection is created with Team site template and second site collection is created with Blog site template.
There are three feature in our wsp that we have created. One feature is at web application scope (which will do web.config modifications and it will add below entry in web.config file through SPWebConfigModification in section 'configuration/system.web/compilation/assemblies'
<add assembly="AjaxcontrolToolkit, Version=4.5.7.725, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e" />
). And there are two site collection features.
Now when we deploy our solution (wsp) to web application in SharePoint 2013 farm and activate the Web.Config modification feature which is at web application level, it has added above mentioned entry in web.config file.
Our application in first site collection is working fine which we are expecting but in the second site collection which is created using out of box Blog site template, 'comment box' and Post button are invisible as shown in below screen shot -
If we remove below entry from web.config file -
<add assembly="AjaxcontrolToolkit, Version=4.5.7.725, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e" />
and refresh the Blog site page then the Comment box and Post button is appearing again as shown in below screen shot -
We also tried with updated versions of AjaxControlToolkit (Version=4.5.7.1005 & 4.5.7.1213) but no success.
I will highly appreciate if you could help me in this.
Thanks for your time.
Thanks & Regards,
Rajendra Gaikwad.

Hi,
As you said, the issue only comes with the Blog site template.
I suggest you take a look at this blog about how to make Ajax Control Toolkit work with SharePoint 2013:
http://andreaswijayablog.blogspot.com/2013/12/ajax-control-toolkit-with-sharepoint.html
Another similar thread for your reference:
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/60fa19fe-86a0-446b-b61f-11a82fe4287f/how-to-implement-ajax-toolkit-for-sharepoint2013?forum=sharepointdevelopment
Thanks
Patrick Liang
Forum Support
Please remember to mark the replies as answers if they
help and unmark them if they provide no help. If you have feedback for TechNet
Subscriber Support, contact [email protected]
Patrick Liang
TechNet Community Support

How to publish pages made in third party software

On my "homepage" websites I can upload html pages created by third party software (Adobe GoLive CS2 in my case) onto my .Mac sites.
I can't find anything in iWeb about publishing custom-made webpages in iWeb and/or on the iWeb. Is this possible with iWeb? Or do I have to stick with the old way of doing things (creating new .Mac sites online and uploading my custom pages there)?

Well, I half-answered my own question here. I went into my iDisk folder, went to Web, Sites, iWeb, then chose the site I had created and put my own custom-built html page there. It uploaded automatically and now I can access it via the web without a problem. It shows up the way it's supposed to look as well.
So basically I can load them up, but there's not a way for me to fully integrate them with the other iWeb pages on that site. My custom page does not appear in the iWeb application under the site name, I can't add web counters to it, etc...

Is this possible in BC to choose site templates from given one ?

Basically, what i want to acheive is to provide an option in BC cms for choosing template and the selected template will reflect the appereance of complete site.

I have more than one template for my site. I just want an option (if possible) in Catalyst cms where I can change the template of my site from the listed one. Suppose I have a dropdownlist that displays the site templates and the template that I select changes the template of site, sets css, js files etc accordingly.
Or
Do I have to change the template of each page and webApp manually ?
I hope i made you clear !

Site Template and webparts in Publishing Pages

Similar Messages

Maybe you are looking for