New answers tagged custom-actions
Please follow the following approach. Create a Sandbox solution rather then creating the SharePoint App Deploy your solution to your SharePoint Online Solution Gallery Activate your solution Activate the feature of your newly activated solution I know this is not the ultimate solution but this solution worked at my end. Let me know whether it helped you ...
I am no exeprt yet, but spent the last days on CustomActions and REST because the New Library View has nothing SharePoint left but CustomActions (and no JSOM on the page it for creating/changing them) There are two types of CustomActions/Scriptlinks involved here: Type 2 = Site(Collection) Executes on every page inside the SiteCollection ...
Earlier it was not possible to inject scripts from CDN to ScriptLink location, you had to use ScriptBlock location to do that. I did some tests and now it is possible, at least in o365! So I updated the Chrome SP Editor chrome extension to support this too. So now, all injections will respect the sequence and will load in correct order.
To hide the standard "Delete this site", try to set the GroupId to SiteTasks: SiteAdministration is for SP2007, while in SP2010/2013, the link has moved to the section "Site Actions". The same applies for your new custom action. So, you should have now: <?xml version="1.0" encoding="utf-8"?> <Elements ...
Top 50 recent answers are included