Modern Experience
3 TopicsProperties Pane on Modern Task Lists broken
So I'm experiencing an issue on a tenant where the properties pane for items in Task Lists, in the Modern Experience are showing an error (See screenshot below). Upon further inspection it seems that there is a 500 Internal Server Error on the call that tries to get the items properties with the following call: https://<tenant>.sharepoint.com/sites/<site>/_api/web/GetList(@v1)/RenderExtendedListFormData(itemId=43,formId='editform',mode='2',options=15,cutoffVersion=0)?@v1='/sites/<site>/Lists/<list>' (I've replaced the actual name of things in the above for privacy reasons.) This all seems normal and it's only task lists affected. If anyone knows what's happening here, your feedback would be much appreciated2.7KViews0likes8CommentsGoogle tag manager preview mode debug pane not working on modern pages
Hello everyone! I tried to add the code for the Google Tag Manager in the browser's console while I was on a modern page, but unfortunately when I'm in the tag manager's preview mode, the debug pane does not open and this error pops up in the console: goog.asserts.AssertionError { message: "Failure: Bad value `d8aec69a-5e9c-4c7a-ae18-1f0ba39af3bc` for |filterCspNonceValue", stack: "AssertionError: Failure: Bad value `d8aec69a-5e9c-4c7a-ae18-1f0ba39af3bc` for |filterCspNonceValue at new goog.asserts.AssertionError (https://tagmanager.google.com/debug:46:1056) at Object.goog.asserts.fail (https://tagmanager.google.com/debug:49:89) at Object.soy.esc.$$filterCspNonceValueHelper (https://tagmanager.google.com/debug:738:137) at Object.soy.$$filterCspNonceValue (https://tagmanager.google.com/debug:706:443) at Object.gtm.debugui.soy.frame.renderContent (https://tagmanager.google.com/debug:748:488) at Object.gtm.debugui.frame.createInlineFrame_ (https://tagmanager.google.com/debug:756:404) at Object.gtm.debugui.frame.init (https://tagmanager.google.com/debug:761:237) at https://tagmanager.google.com/debug:761:385 at https://tagmanager.google.com/debug:762:3" Adding the same script from google tag manager in a classic experience page and opening the debug pane works fine, without the assertion error occurring. I also tried to use the SPFx extension (that seems to do pretty much the same thing) from this repository: https://gitlab.lsonline.fr/SharePoint/sp-dev-fx-webparts/gtm but the same issue occurs. I am using SharePoint 2019 but this error pops up in SharePoint online too.2.3KViews0likes0CommentsConverting classic site to modern ui.
I'm able to create new pages using the modern UI. However, site contents and site settings are using classic mode. I suspect it's the masterpage that's applied. Considering modern pages don't have a masterpage. How would I go about modernizing site content and site settings?1.7KViews0likes2Comments