Forum Discussion
New Wepart fails in modern team site
i add a news webpart to a modern teamsite i have created and as soon as i save the edited page it fails
Something went wrong
If the problem persists, contact the site administrator and give them the information in Technical Details.
TECHNICAL DETAILS
TECHNICAL DETAILS
ERROR:
t.toLocaleDateString is not a function
CALL STACK:
TypeError: t.toLocaleDateString is not a function
at Function.t._getFormattedDate (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-news-webpart-bundle_en-us_e70e6cf7bde438760037fef0d5323b27.js:175:32707)
at t.render (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-news-webpart-bundle_en-us_e70e6cf7bde438760037fef0d5323b27.js:175:40766)
at Dn (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-pages-assembly_en-us_845b731275cd8de3f4f57bff1bfafffa.js:912:420941)
at Mn (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-pages-assembly_en-us_845b731275cd8de3f4f57bff1bfafffa.js:912:420736)
at zn (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-pages-assembly_en-us_845b731275cd8de3f4f57bff1bfafffa.js:912:424105)
at Zn (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-pages-assembly_en-us_845b731275cd8de3f4f57bff1bfafffa.js:912:437004)
at Jn (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-pages-assembly_en-us_845b731275cd8de3f4f57bff1bfafffa.js:912:437385)
at gr (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-pages-assembly_en-us_845b731275cd8de3f4f57bff1bfafffa.js:912:443900)
at yr (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-pages-assembly_en-us_845b731275cd8de3f4f57bff1bfafffa.js:912:443280)
at dr (https://spoprod-a.akamaihd.net/files/sp-client-prod_2019-02-15.009/sp-pages-assembly_en-us_845b731275cd8de3f4f57bff1bfafffa.js:912:442309)
any ideas? every other part of the site works fine just news. i have added news still nothing same error.
- Pfff, Microsoft might rolled out an update to the WebPart that could be causing this error...what browser are you using? I have discovered recently that the News WebPart does not behave well when used in IE
