First published on TECHNET on May 01, 2018
Wanted to make sure you were aware of this change that affects only SPO.
Beginning June 2018, in SharePoint Online, Microsoft will remove the in-product UI entry point for automatic translations. The configuration options during variation use will be removed and hardcoded to false. The APIs will be marked as deprecated with limited support, but will continue to remain available if users want to integrate directly via custom code.
Microsoft recommends that users leverage the Bing translation APIs directly. However, users will still be able to continue accessing the existing APIs via custom code, but support is limited. Please see this document for more information about SharePoint Machine Translation (Variations).
For SharePoint on-premise, Microsoft we will not remove the UX entry points or API, but will communicate that this feature is deprecated.
Beginning in June 2018, the UI entry point to SiteManager.aspx will be removed from SharePoint Online and direct access will be restricted to Site Collection Admins. For customers using the Site Manager, we recommend considering the modern file and library copy/move functionality. The main functionality of Site Manager has been implemented in modern file move and copy. You can learn more about File Copy/Move for SharePoint Document Libraries here .
For more information about how to move and copy files in a document library in SharePoint, see the following Microsoft websites:
To learn more about the differences between modern and classic lists and libraries refer to the article at https://support.office.com/en-us/article/differences-between-the-new-and-classic-experiences-for-li... .
You can learn more about File Copy/Move for SharePoint Document Libraries at https://support.office.com/en-us/article/Copy-files-and-folders-from-OneDrive-for-Business-to-a-Sha... .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.