Hot answers tagged

7

First, you can change the O365 landing page, but you can't specify a URL for the new landing page, it's a dropdown menu. See https://blogs.office.com/2014/09/18/new-office-365-home-page-fast-access-services/ for details. Second, this setting is a per-user one. An admin cannot change this setting for all or specific users at this time. As it's said in ...


6

That's the "Welcome Menu". While not an official Microsoft source, that is how the class structure and API defines it, and Heather Solomon's CSS chart covers it here.


4

That's actually a User Control called Welcome menu <%@ Register TagPrefix="wssuc" TagName="Welcome" src="~/_controltemplates/Welcome.ascx" %> The menu items can be observed by opening C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\CONTROLTEMPLATES\Welcome.ascx


3

No you can't. The whole point of a personal (MySite) site is that it is a silo not connected to anything else. That’s why you get a Site Collection usually under the wildcard inclusion /personal of the MySite Host root Site Collection. To accomplish this effect you need to build/configure something of your own. But since there are a lot of dependencies to ...


3

SharePoint 2010 ribbon doesn't have anything in common with 2007's DisplayFormToolBar. The custom action Location attribute should be set to "CommandUI.Ribbon" for adding something to ribbon. Then, you should provide special XML for button. Since SP2010 ribbon is a client-side thing, no C# code is involved here. You can find a simple example of adding a ...


2

I have now discovered why I couldn't save the custom properties in the GUI. I was closing the Current Web Object from the SPContext. Apparently this should not be done as it's handled by the framework. Once I removed my CurrentSite.Dispose() from my finally in the webpart user control, I was able to properly save the custom properties.


2

If you are going to put a web part on a page multiple times, each instance of the web part needs to have a unique id. Here's a sample of something you could do: control.ID = this.ID + "_ProjectDetailsControl";


2

Create the property as a dropdown box and the Personalization scope should be PersonalizationScope.User. Sample code might look like below. public enum UserColor { Blue = Blue, Green = Green, Yellow = Yellow } private ItemCount uColor= UserColor.Blue; ...


2

2013 allows people with contribute access to 'Personalize this Page'. This user clicked their name, clicked 'Personalize this Page', then minimized the web part. To revert the change, had the user click their name, then 'Reset Page Content'. Note that this option only appears after the page has been 'personalized'. Hope no one else spends as much time on ...


2

I acually found some people at my company that had made a similar function and together with them I was able to find a somewhat satisfying solution. If anyone else in the future want to do the same thing as this I though I would share how I've done this. Question 1: Is Add In Part shared or personal I could not find any property on an AddInPart for if it's ...


1

You need to modify the views of the lists and remove the field with property linked to item with edit menu. Instead you may use the field with linked to item property.


1

I believe what you are looking for is called Personalized Pages. It's a little obscure, but allows you to do exactly what you are asking: That people can personalise their page, meaning they can change the content on the page, the webparts, the order of the webparts. It's similar to personalized views on lists and personalized webparts (kind of). It may be ...


1

To reset the personalisation you simply need to call a JavaScript on that button. javascript:SP.SOD.execute('browserScript', 'MSOWebPartPage_RestorePageDefault') When the user clicks the button he will be asked to reset the personalisation. Once the user confirms this the personalisations are gone.


1

the code above didn't work for me directly (SP2013) because for some reason the Users "PersonalSite"-Attribute was not filled, so I modified the foreach loop as follows (a bit crude, but you get the idea): foreach($profile in $AllProfiles) { $DisplayName = $profile.DisplayName Remove-SPSite -Identity $profile.UrlToCreatePersonalSite -GradualDelete ...


1

Refer the following links, http://office.microsoft.com/en-in/office365-sharepoint-online-enterprise-help/manage-personal-and-social-features-HA102772280.aspx How to delete a my site for a single user - SharePoint 2013 on premises To delete using powershell, use the following code #PowerShell Script - Delete All Users Personel Sites - SharePoint 2010 ...


1

After some experiments, here is seems-to-work solution : var web = SPContext.Current.Web; var mgr = web.GetLimitedWebPartManager(file.ServerRelativeUrl, System.Web.UI.WebControls.WebParts.PersonalizationScope.User); var wpFile = web.GetCatalog(SPListTemplateType.WebPartCatalog).RootFolder.Files["somewebpart.webpart"]; /* Elevated the process just for ...


1

Update Inadvertently figured this one out while working through an unrelated issue. I had another property defined as <Personalizable> Public Property IDs As IEnumerable(Of Int32) later in the code. Can't serialize an interface though, especially one that represents an in-memory query - so it was killing Personalization altogether on my page. I ...


1

A bio would typically be the About Me section of the user profile. It shows up on the public person.aspx page for the user. That not fitting the bill?


1

WebPartManager.DisplayMode gives you the mode of the page: Browse, Edit, ... WebPartManager.Personalization.Scope gives you the scope of the page: Shared or User


1

I hope you will get different way to do achieve this by following url: How to hide/show My Site link on portal in personal menu?


1

Web Part properties with PersonalizationScope=PersonalizationScope.User have the possiblity of storing that setting for individual users as well as for shared. BUT the individual value is only set when editing the web part after selecting Personalize this page and the indivual value is only used when the page containing the web part is in Personal view. ...


1

Develop the code as described by @Deepu. When you add the web part to a WebPart Page (NOT a wiki page) the users have the option of going to the hidden personal menu and select Personalize this Page and then edit the web part. The only properties they can edit in this mode are the User scoped ones and they only modify them in their personalized view


1

Add a content editor webpart to page with the following script: <script type="text/javascript"> function ReplaceText() { MSOStrings.ResetPagePersonalizationDialogText = 'Custom Message'; } _spBodyOnLoadFunctionNames.push('ReplaceText'); </script>


1

If you view the source of the page, you can see that it refers to itself as a "PersonalActionMenu".


1

I think you have complicated your solution :) Firstly, btnSubmitZipCode_Click will get executed after Page_Load. there is no need to use the "ParentWebPart" property. If you want remove the ability to change the option in "Edit Webpart" you don't need the property pZipCode. Simple solution would be : Seperate the Webservice call which might include ...



Only top voted, non community-wiki answers of a minimum length are eligible