Forum Discussion
Modern team/communication site - Suite Bar branding
MicrosoftAt first glance this looks like a CSS branding issue. Do you have some CSS Customizations on your master page? Overall this should not be related to the issue we were seeing yesterday.
It's a modern communication site and we have not applied any CSS or master page because I believe modern pages don't respond to custom CSS/masterpages. All web parts added to this page are OOO ones. Just deployed a header and a footer message (inside DIV tag) inside header/footer placeholder using SPFX app customizer. I think the SPFX app customizer won't push the page DOMs below for this alignment issue. Surprisingly I created a new communication site and the same issue is not happening. I am confused.
Today I noticed the issue is no more. The alignment is proper. Seems fix has been pushed to our tenant.
- Sam Larson
I am currently investigating the issue .
Looks like the Yammer webpart has got the error again.
Something went wrong
If the problem persists, contact the site administrator and give them the information in Technical Details.ERROR: Cannot read property 'match' of undefined CALL STACK: TypeError: Cannot read property 'match' of undefined at M (https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-yammerembed-webpart-bundle_en-us_cd1f87ae915957b3d91341dcf9c08662.js:84:14779) at t.logEvent (https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-yammerembed-webpart-bundle_en-us_cd1f87ae915957b3d91341dcf9c08662.js:84:19194) at t.logEvent (https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-yammerembed-webpart-bundle_en-us_cd1f87ae915957b3d91341dcf9c08662.js:84:92984) at t.onInit (https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-yammerembed-webpart-bundle_en-us_cd1f87ae915957b3d91341dcf9c08662.js:84:91074) at t._internalRenderInViewPort (https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-pages-assembly_en-us_567068f25f8c399da5f2e1a9b9fefd40.js:541:29875) at e._renderWebpartInViewport (https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-pages-assembly_en-us_567068f25f8c399da5f2e1a9b9fefd40.js:541:17053) at e._checkVisibilityAndRender (https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-pages-assembly_en-us_567068f25f8c399da5f2e1a9b9fefd40.js:541:14564) at e.register (https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-pages-assembly_en-us_567068f25f8c399da5f2e1a9b9fefd40.js:541:12227) at t._internalDelayedRender (https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-pages-assembly_en-us_567068f25f8c399da5f2e1a9b9fefd40.js:541:29194) at https://spoprod-a.akamaihd.net/files/sp-client-prod_2018-01-26.004/sp-pages-assembly_en-us_567068f25f8c399da5f2e1a9b9fefd40.js:541:29106- Sam LarsonWe might need to look a bit deeper here. Feel free to PM me more details on the site collection in question or we can look at getting you a support ticket opened.
