A Google Chrome Extension for creating and updating files (js, css) in SharePoint Online from Chrome Developer Tools
Here's a great introduction video by Jeff Jones
- 2.1 New Feature
- File editor: View and edit all files on current site
- white file icon = content file
- red file icon = ghosted file (Un-Customized)
- yellow file icon = unghosted file (Customized)
- Updated sp-pnp-js to 2.0.4
- File editor: View and edit all files on current site
- 2.0 Almost complete re-write
- Converted all pages to use riot.js ( Thanks @andrei-markeev )
- Updated sp-pnp-js to 2.0.3
- 1.7.2 Small fixes
- 1.7.1 Small fixes
- 1.7 New Feature
- List Properties: view, edit, add, remove and index list RootFolder properties
- Enhancements in Page editor: add & remove webparts by @andrei-markeev
- 1.6.1 Small fix
- 1.6 New Feature
- Page editor: edit webpart properties. created by @andrei-markeev
- 1.5 New Feature
- PnP JS Console: Write TypeScript using PnP-JS-Core definitions and execute on current context
- Updated pnp-js-core to v2.0.2
- 1.4 Bug fixes
- Fixed issue when saving files from another web/sitecollection
- Fixed issue about Scriptlinks were not always rendered
- Updated pnp-js-core to v2.0.1
- 1.3.1 Name and Icon change
- 1.3.0 Added possibility to create webhooks for lists
- Changed SharePoint Client Object Model to PnP-JS-Core
- Chrome SP Editor works now in classic and modern pages
- Chrome SP Editor works now with SP2013, SP2016 and SharePoint Online
- Fixed some rendering issues
- 1.2.18 Added possibility to create indexed webproperties
- 1.2.17 Small fix
- 1.2.16 Small fix
- 1.2.15 All injections will now respect the sequence, no matter if loaded from CDN or locally
- 1.2.14 Small fix
- 1.2.13 Added possibility to inject new file from add new file view.
- 1.2.12 Fixed issue where editors in different tabs could affect others settings.
- 1.2.11 Added default content to new js/css files created from the editor.
- 1.2.10 Bug fix. Edited file was always published as a major version.
- 1.2.9 Fixed major bug after latest improvements
- 1.2.8 Added notifications for all events. Removed rest of the alert boxes
- 1.2.7 Added file name to the notification
- 1.2.6 Changed alert boxes to notifications when saving a file
- 1.2.5 Added SP2013 OnPrem support
- 1.2.4 Added filtering for propertybag value listing
- 1.2.3 Small messaging enhancements
- 1.2.2 Small messaging enhancements
- 1.2.1 Small usability enhancements
- 1.2.0 Added support for view, add, edit and delete web propertybag values
- 1.1.0 Added support for chrome workspaces and querystring for injections
- 1.0.0 First published version
Creating and editing js / css files in SharePoint Online from any device which has Chrome desktop browser. Also possibility to add local and external js/css resources references with usercustomactions.
Install extension from Chrome web store https://chrome.google.com/webstore/detail/sp-editor/ecblfcmjnbbgaojblcpmjoamegpbodhd
Clone the repository
- git clone https://github.com/tavikukko/Chrome-SP-Editor.git
- Open Chrome with url chrome://extensions/
- Click "Load unpacked extension..." and select Chrome-SP-Editor folder
Go to your SharePoint site and open Chrome developer tools.
- Select SharePoint tab, select "Save to SharePoint" from left navigation" and select "Update changes to SharePoint".
- Select sources tab
- Select js/css file for editing
- Make changes and save (cmd+s / ctrl+s)
- You will get notifivation if the save was successful or not
- Select SharePoint tab, select "Files" from left navigation
- Write filename (.js/.css) and press add
- New empty file will be created in the Style library of the rootweb
- You can inject the file after adding it
- Select SharePoint tab, select "Scriptlinks" from left navigation
- Give sequence for the link to be added. The sequence will tell the order to load the files
- Add the URL to the file. Local js files, use ~sitecollection/path/to/your/file.js. Local css and external css and js files must use absolute url.
- From the dropdown, select if you want the file to be added only to current site, or to the whole site collection.
- Select SharePoint tab, select "Web properties" from left navigation
- Add new property and value and press "Add property"
- Edit or modify current properties from the list below
- click index in you want make the property searchable (you need to create managedproperty after the property has been crawled)
- Select SharePoint tab, select "List properties" from left navigation
- Select list from dropdown to see RootFolder properties
- Add new property and value and press "Add property"
- Edit or modify current properties from the list below
- click index in you want make the property searchable (you need to create managedproperty after the property has been crawled)
- Select list where the webhook subscription will be added
- Give the full path to the endpoint (endpoint must handle POST request and return provided validationstring)
- Write TypeScript using PnP-JS-Core definitions and execute on current context
- ctrl + d to execute
- for sp2013 change the headers of the request:
pnp.setup({
headers: {
"Accept": "application/json;odata=verbose",
}
});
- Edit the webpart properties using the the editor.
- Make sure the page is checked out to be able to save it back with changes.
- View all files and folder of the current web
- Ctrl + s to save edited file (select "Update changes to SharePoint" first)
- white file icon = content file
- red file icon = ghosted file (Un-Customized)
- yellow file icon = unghosted file (Customized)
- SP Editor works also when using Chrome workspaces, it saves the file to the disk and also the SharePoint.