Hot answers tagged web-part
In your Ajax code, we read: url: "/Layouts/SendUsEmail/Handler1.ashx", While it should be: url: "/_Layouts/SendUsEmail/Handler1.ashx", note the '_' in front of "Layouts".
Yes. First you should register the ascx file in the Markup of your webpart <%@ Register Src="~/_controltemplates/15/Folder/Page.ascx" TagPrefix="uc1" TagName="PageAscx" %> Then add the control using <uc1:PageAscx runat="server" id="PageUC1" />
There are multiple ways to edit the "InfoPath Form" associated with your site. Generally, the InfoPath Form will be associated to an existing list or library on your site. There are two main methods, to updating the form. Firstly, InfoPath using Browser. Secondly, SharePoint Designer. InfoPath To customize your list form in the browser, just browse to ...
If you only want the users to be able to work with documents, you can break the role inheritance on the document library. Then you give the editing users higher permissions only on that library and not on the whole site. Details on how to break permission inheritance is found here
To stress test this, your best bet would be a PowerShell script adding multiple items with various Sleep intervals. Will it scale to several hundred users? It depends. Mostly on your server's hardware resources, how SQL is setup, the solution itself, how large are the documents etc. Personally I don't think there would be an issue, as I remember doing this ...
There is no OOTB webpart available for this activity. But you can create a custom Web Part for this. Programmatically find out the number of site-collections within a web application. SPWebApplication.Sites would help you get the site-collection present inside web application. Check these for more info: ...
We had the same issues as you have, i must admit it is really awkward the behaviour you face. One of the transformer you are injecting in your method is a not allowed type on webpart pages. Our issue was that we used the following transformer type: RowToParametersTransformer , this one is not supported and should be changed with the following: ...
Only top voted, non community-wiki answers of a minimum length are eligible