New answers tagged


It is really unhelpful that there is so much confusion in the MS developer community about what is allowed in custom actions in SharePoint 2013. Trying to be helpful, Hermant Mane offered an answer and several comments above but gave examples for SharePoint 2010. The article linked to on is under the heading "Pre-SharePoint 2013" and was ...


Try the following CSS: /* Hide Calendar Ribbon Body */ #RibbonContainer ul[id$="Calendar"] { display: none !important; } /* To hide Calendar Ribbon tab */ #RibbonContainer li[id$="Calendar-title"] { display: none !important; } You can add the above CSS either to the Script Edito/Content Editor web part or embed into the page.


Number of things you can try here. Revert back to OOTB master page. If it fixes the issue, then obviously the problem is on the new master page. I don't think the problem is resolution. It could be the resolution of the picture, but it looks like all the buttons are disabled. If you are running in a regular IE window and the user has full access to the ...


You mean like using a link? Such as this one: {Site URL}/_vti_bin/owssvr.dll?CS=109&Using=_layouts/query.iqy&List={List GUID}&View={View GUID}&CacheControl=1 from the post Create Link to Export Library Contents to Excel


Check <script type="text/javascript"> function Custom_Submit(command) { SP.Ribbon.PageState.Handlers.showStateChangeDialog(command, SP.Ribbon.PageState.ImportedNativeData.CommandHandlers[command]); } </script> <input type="button" ...


Custom actions should still be around. On top of this, you only have to follow the very first steps of that article to see a new button in the ribbon (till "Deploying the App that contains the custom action markup shown above..."). So, the main step is only about copy/pasting the XML block. Can you show us what you have in your solution and your ...

Top 50 recent answers are included