Error Creating Control Web Part Add Updatepanel Sharepoint 2010
for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us SharePoint Questions Tags Users Badges Unanswered Ask Question _ SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top SharePoint Designer 2010 - Error Creating Control - WebPartAdderUpdatePanel up vote 1 down vote favorite When I open any page in SharePoint Designer I receive an error that says: Error Creating Control - WebPartAdderUpdatePanel Unknown server tag 'WebPartPages:WebPartAdder'. I still seem to be able to use SharePoint Designer without any problems. Any ideas what might cause this, and how can I fix it? Thank you for your help. 2010 sharepoint-designer error share|improve this question asked Sep 29 '11 at 18:37 Ben 2827 Position has already been activated, reactivation did not help –Silva de Vuple Jun 17 '14 at 10:49 add a comment| 1 Answer 1 active oldest votes up vote 2 down vote accepted I had the same issue when editing the master pages for the 'Companyweb' site on SBS 2011. It seems to be permissions related and I was able to get rid of the error by logging into sharepoint with the site owner account (as opposed to a 'normal' site editor) and did the following: Go to 'Site Actions' at the top right of the page then click on 'Site Settings' Under 'Site Collection Administration' select 'SharePoint Designer Settings' Tick 'Enable Managing of the Web Site URL Structure' After doing this the error went away. I should point out that I'm new to SharePoint and 'just fiddling' rather than dealing with a production site, so I can't comment on whether or not it's actually a good idea to do this or not! share|improve this answer answered Jan 8 '12
Web Part Adder/Update Panel August 28, 2012 Heather Solomon 9 Comments The problem A very common request with custom SharePoint branding is to convert the master page and CSS to a centered, fixed width design. For instructions on how to do this, check out my Creating a centered fixed width design in SharePoint 2010 blog post. A lot of designs like to use "960px" for the width value. Unfortunately this creates a problem for the SharePoint Web Part Adder/Update Panel (the WebPartAdderUpdatePanel control found in the http://sharepoint.stackexchange.com/questions/20499/sharepoint-designer-2010-error-creating-control-webpartadderupdatepanel SharePoint master page). A 960 pixel fixed width SharePoint master page isn't wide enough for the panel. Depending on which browser you are using, the bottom buttons (Add and Cancel) will be hidden or partially cut off when the panel is active. Here is a screenshot of what happens in IE: I got mixed results in Firefox. Sometimes the http://blog.sharepointexperience.com/2012/08/fixed-width-sharepoint-master-page-web-part-panel/ buttons are completely obscured while other times the buttons displayed just fine. Go figure. If we adjust the fixed width to 1018 pixels, the buttons appear again: So "1018px" (or larger) is the magic width value but changing your site design width to this size may not be acceptable. Luckily there is a quick CSS fix you can do. The fix The culprit behind this problem is an inline style set for a DIV element that wraps the web part description. Below is a screenshot showing the description area and the corresponding code. The DIV also uses a class, so that can be used in a new style statement that overrides the width of the DIV element. Since the width is set using an inline style, !important has to be included with the new value. /* Reset the width of the wrapper for the web part description text in Web Part Adder/Update Panel */ .ms-wpadder-descriptionArea { width: 265px !important; /* !important used to override OOTB inline SharePoint style */ } That is the end of the CSS f
SharePoint, SharePoint 2010, SharePoint Development, Web Parts Cannot use an UpdatePanel in a SharePoint 2010 Sandbox Solution Alex December 14, 2010 5 Comments I have been working on a SharePoint 2010 web part recently that uses an EditorPart to allow the users http://www.sharepointalex.co.uk/index.php/2010/12/cannot-use-an-updatepanel-in-a-sharepoint-2010-sandbox-solution/ to set some properties for the web part. I wanted to use an UpdatePanel within the EditorPart to avoid postbacks and as I understood it the SharePoint 2010 masterpages already have a ScriptManager in them. http://www.jamestsai.net/Blog/post/How-To-Create-AJAX-enabled-SharePoint-Web-Part-with-UpdatePanel-and-UpdateProgress-in-10-minutes.aspx Sadly it seems this is not possible – if you try to add an UpdatePanel within the CreateChildControls method you will get an exception – ‘The control with ID UpdatePanel1 request a ScriptManager on the error creating page’. This indicates that you need to add a ScriptManager to the page which is strange as the masterpage should already contain one! If you try to add a ScriptManager to your web part you will get a InvalidOperationException– ‘The PageRequestManager cannot be initialized more than once’. This indicates that a ScriptManager already exists on the page – which is correct as the masterpage contains one. Unfortunately you are not error creating control able to get a reference to this ScriptManager as ScriptManager.GetCurrent() returns null. I created the same web part as a farm solution and low and behold I am able to add an UpdatePanel straight away with no problems and ScriptManager.GetCurrent() returns the ScriptManager! *Update – Wictor has commented on this post describing why you can’t get a reference to the ScriptManager object in the sandbox: Hi, this is not a bug. It’s a feature of the Sandbox. The SB creates its own copy of the Page object and “copies” some information from the real Page object to the SB page object – but not everything such as the ScriptMgr reference etc. Hope this helps #SP2010 .NET AJAX Development MasterPage ScriptManager SharePoint 2010 UpdatePanel Web Parts 5 thoughts on “Cannot use an UpdatePanel in a SharePoint 2010 Sandbox Solution” Wictor Wilén December 14, 2010 at 10:51 am Hi, this is not a bug. It's a feature of the Sandbox. The SB creates its own copy of the Page object and "copies" some information from the real Page object to the SB page object - but not everything such as the ScriptMgr reference etc. Reply ↓ Alex December 14, 2010 at 10:58 am Hi Wictor, Thanks for the reply i
Issues you should know about >> Oct 27 2008 ASP.NET // Programming // SharePoint How To Create AJAX-enabled SharePoint Web Part with UpdatePanel and UpdateProgress in 10 minutes An article by James 277 Comments In this post I am going to show you how you can setup your SharePoint site to support Microsoft ASP.NET AJAX framework and create a basic AJAX-enabled SharePoint Web Part. You can find many great articles on MSDN on how to do these and they explained in more details, but if you are looking for a way to get it up and running in 10 minutes, this is it. An AJAX-enabled web part with update button and display current time every time when button is clicked. Loading image and text displayed during the update. Goal Enabling SharePoint site with ASP.NET AJAX framework support Create AJAX-enabled SharePoint web part with UpdateProgress control for visual feedback in browser when web part is updating with AJAX request event script to hide UpdatePanel while web part is updating Add AJAX-enabled web part to page and see it in action Solution Enabling ASP.NET AJAX framework support for SharePoint site 1. Go download and install - Microsoft .Net Framework 3.5 (if you haven't already) Service Pack 1 for .NET Framework 3.5 is not required here, but it is recommended to install it for future capabilities 2. Register ASP.NET AJAX server controls as safe controls. You can either: If you like the text-editing challenges - Go spend an hour follow the steps in this article and hope you don't get any errors :p (It is still recommended to read and understand how/what to change web.config to make AJAX working) Or if you are lazy and really want to get it working in 10 minutes - Go download this SharePoint Feature (Change web.config for ASP.NET 3.5 AJAX support). This project is created by [MVP] Steven Van de Craen. After you deploy this feature, you need to activate it from SharePoint Central Administration > Application Management > Manage Web Application Features. And it will register those server controls for you in web.config Create AJAX-enabled SharePoint web part Above diagram shows the basic structure of AJAX-enabled web part created in this example. The orange and purple blocks are the classes you'll need to implement in this example. Both blue squares are the ASP.NET AJAX server controls and other blue round squares are the common ASP.NET server controls. Their purpose will be explained in the following steps. 1. Create