Highlighted content web part not showing videos
Where do video files need to be stored (what type of library or list) and of what file type or content type do they need to be to be picked up by the highlighted content web part when it is set to show only content of type Video in the site collection? I have used an assets library and mp4 files. They files play fine in the app itself, but the highlighted content web part is not showing them when I configure it to show Video files. (I do see that the files are being indexed as I can get them showing if I ask the web part to for example show content added today, so my question is more related to the query applied by the web part not really working for me.)
SharePoint Modern Page WebParts with Audiences
Hello all, I am trying to use the Modern Site Pages in SharePoint Online, but I think one feature may be missing. I have a somewhat personalized view, where I show or hide webparts using Target Audiences (based on the specific role of the User). Can I accomplish this in the Modern Site Pages feature? Is this not supported? In case this is not supported, are there any workarounds or tips on how to implement this? What I want to do is to have 3 different views inside a webpart based on which of the three roles the user has. Thanks, G.Modern pages with text web parts upgraded from CKEditor v4 to v5 lose image positioning
We have lots of pages where images are positioned next to each other like so: This positioning can be done in pages that are programmatically created. When editing the page, the images stay as they are - next to each other. All good. Currently SharePoint is upgrading the rich text editor backing the text editor web part: CKEditor. And this causes issues. So far the text editor was based on CKEditor v4. Now, for new pages and selected old pages SharePoint is using CKEditor v5. Old pages are upgraded to the new version when editing those pages. (But not all pages. Not sure how those to be upgraded are chosen.) Note: the new text editor version can be detected by inspecting the editor styles. If rte--ck5 is in use, it's a v5 page. Otherwise v4. Inline image handling changed in the new CKEditor v5 version. In v4 pages there was a hidden image web part for each inline image. In v5 pages this changed and there are no hidden image web parts anymore. Here's the issue: after upgrading old pages that contain adjacent images, they are no longer adjacent, but stacked on top of each other. Note: recently, there were problems when upgrading tables from CKEditor v4 to v5 (see https://github.com/SharePoint/sp-dev-docs/issues/9160). In my books this is another issue with the new text web part based on CKEditor v5. Images that are adjacent in CKEditor v4 should stay next to each other in upgraded pages as well, otherwise formatting of those pages is seriously negatively affected. I'd love to have input on this from somebody in the know. Edit: I'm providing a PowerShell script that creates a test page to reproduce the behavior. Although whether you see the behavior or not is dependent on whether the page will be upgraded to v5 on your tenant, or not. https://github.com/WikiTransformationProject/library/tree/main/issue-related/ckeditor/inline-images.Announcing SharePoint page approvals
We are happy to announce that we will be releasing SharePoint page approvals to Targeted Release. We expect to start the rollout of this feature to all Targeted Release tenants by end of July 2018. Rollout status Current rollout status: July 31st, 2018 - Deployed to 10% of Targeted Release tenants August 3rd, 2018 - Deployed to 50% of Targeted Release tenants August 6th, 2018 - Deployed to 100% of Targeted Release tenants January 8th, 2019 - Deployed to all tenants in SharePoint Online Documentation: 1. Configure page approval 2. Page approval flow Known issues If the page is checked-out by another user and you (the author in this case) submit the page for approval, the page will not notify and proceed with the approval. The flow will run and send an email indicating to the author indicating an error occurred in publishing the page. If you have only major versions enabled for the Site Pages library, submit for approval will result in int he following error: Could not complete that action: The type of data at position 0 is different than the one expected. There an issue with the Flow service for the UK region. Any existing UK tenants created before March 2018 will work while it affects only new tenants created after March 2018. We expect to have this resolved by end of September if everything goes according to the plan. See this thread for more information. Good news is that these will be fixed soon are fixed! If you have any feedback, please make sure you discuss here! Configure page approval Site owners can configure page approval to add to the standard publishing process for a site. After adding page approval flow, new and updated pages will be not be published directly. Instead, only the completion of the approval flow will make changes visible to all readers of the site. A site owner can configure page approval flow from the Flow menu of a pages library. Submit page for approval Once the page approval is configured, authors will be able to submit page for approval. The publish button will be replaced by a submit for approval button. The page will be published once the page is approved. Rejecting a page will put that page back to draft status. Approve page Approvers will get an email regarding the page approval request. They can either approve the page directly in the email (in email clients that support actionable messages) or open the page from the email to review and approve the page in SharePoint. Customizing the page approval flow Since page approvals use Microsoft Flow behind the scenes, the page approval flow is available to site owners to modify and add any custom business process items in the flow. After creating the flow, the site owner can click on Flows -> See your flows in the pages library to find the page approval flow. For example, The default approval type is set to ‘anyone can approve’. Site owners can modify the flow and change the approval type to ‘everyone must approve’ if that is the requirement.
pusblished site page - site page details discrepency
Our pages in SharePoint online have their Date property displayed in dd-mm-yy format, while this is supposed to be in dd/mm/yyyy format (as per our Belgium regional settings). Is there a solution to this? FYI: 1 - the page details show the desired format. see attached screenshot. 2 - we are using the OOTB page Properties webpart 3 - the date format in ListViews is dd/mm/yyyy (JSON formatting as the only solution) If you want to see my question posed differently, please see the below picture:
Bug/issue with modern news thumbnail if team site has header image
I'm experiencing a rather strange issue with modern team news. I have this issue on two different O365 tenants. When a team site has a header image - the news thumbnail will render the site header image, not an image from the news post. This is the news web part - the news item thumbnail is the same image as the site header: Even though the news item looks like this:
