Since Microsoft got rid of MCMS (Microsoft Content Management Server) and rolled its web page authoring features into SharePoint (2007 to Online) the product has supported the creation of an article that can be set to go live automatically at a specified date and time. This is a feature that I’ve been asked about loads and recently had to provide some detailed steps. Enjoy!
Scheduling a page for publication at a later date
- Create a new page or navigate to the article that you want to schedule for later publication
- Click Ribbon > Publish > Schedule
- Set the publishing schedule for the article as desired and click OK
- Note that the author is informed of the scheduled publication date
- Click Ribbon > Publish > Publishing > Publish
- Add optional editorial comments and click Continue
- Note that the article is now published and will become available to readers on the scheduled date and time
Not seeing the “Schedule” button on the ribbon?
In order to schedule publishing the following configuration needs to be in place on the Pages library storing your articles.
- Navigate to an article where you want to enable scheduled publishing
- Click Ribbon > Page > Page Library > Library Settings
- Click General Settings > Versioning Settings
- Ensure that Content Approval = Yes
- Ensure that Document Version History = Create major and minor (draft) versions
- Click OK
- Click General Settings > Manage item scheduling
- Ensure that Enable Item Scheduling = Yes
- Click OK
If you have an autohosted SharePoint app that requests tenant scope permissions and you set the target site to a local URL you might run into a problem when debugging from Visual Studio.
The certificate is added and the app deploys fine. The user is then prompted to grant the app permission but a message notifies us that the current user does not have permission to trust the app.
Sorry, only tenant administrators can add or give access to this app
So in order to grant a user “tenant administrator” rights in a local farm complete the following:
Add the account (not via a group) to the Farm Administrators role in Central Administration
Do an IISRESET after granting the permission.
When you re-deploy the app from VS the account should now be able to click the “Trust It” button.
And you’re off to the next hurdle…
I’m starting my journey into the new apps model for Office and SharePoint and so far the documentation at http://dev.office.com has been pretty good. It’s also become clear that I can no longer ignore www.oauth.net :-p
I would suggest starting with these great, free videos:
- Module 1: Introduction to Office 2013 and SharePoint 2013 development
- Module 2: Develop apps for Office 2013
- Module 3: Create document-based apps for Office 2013
- Module 4: Create mail apps for Outlook 2013
- Module 5: SharePoint 2013 app model for developers
- Module 6: SharePoint 2013 developer tools
- Module 7: Create hosted apps in SharePoint 2013
- Module 8: Create cloud-hosted apps for SharePoint 2013
- Module 9: SharePoint 2013 client object model (CSOM) and REST APIs
- Module 10: OAuth and application identity in SharePoint 2013
- Module 11: Develop SharePoint 2013 remote event receivers
- Module 12: Workflow changes and features in SharePoint 2013
- Module 13: Business connectivity services changes in SharePoint 2013
- Module 14: Search features and changes in SharePoint 2013
- Module 15: Enterprise content management changes in SharePoint 2013
- Module 16: Social features in SharePoint 2013
- Module 17: Office services in SharePoint 2013
- Module 18: Create mobile apps for SharePoint 2013
- Module 19: Project Professional 2013 training for developers
- Module 20: Project Server 2013 training for developers