I recently embedded a feed on one of our SharePoint pages. The feed worked fine 2 days ago but today i get the following error:
Uncaught SyntaxError: Invalid regular expression: /^[^Ö-׿؀-Û¿Ý-ݿࢠ-ࣿï¬-ïï-ï·¿ï¹°-]*[A-Za-zÀ-ÖØ-öø-ʸ̀-Öà €-á¿¿â°€-﬜︀-﹯﻽-ï¿¿]/: Range out of order in character class
The error seems to occur at:
https://s0.assets-yammer.com/assets/yam-platform-feed-9bcb8d2f0391f8bdbf6bb270b9167e88.js line 57
Additional information:
This error only happen with this specific Yammer group
The error doesn't occur in other groups i tested it with
The Yammer Embed script is as is provided by Yammer (the network and group-id are changed)
Tested in both IE10/11 and Chrome 49.0.2623.112
Screenshot from Chrome Developer Tools
Can anyone with help with this problem?
Related
I developed a MERN application where everything runs perfectly normal on localhost. Now I put my application live, Heroku for the backend and Netlify for the frontend, and when visting my home url (https://bap-nmd-2020-2021.netlify.app/) the page just stucks. Nothing is loaded and the code stops executing.
I used chrome and firefox dev edition to see what could be wrong. What I found where the following errors
In chrome dev tools:
Uncaught SyntaxError: Unexpected token '<'
In Firefox dev edition:
The stylesheet https://bap-nmd-2020-2021.netlify.app/static/css/main.ab94b624.chunk.css was not loaded because its MIME type, “text/html”, is not “text/css”.
Uncaught SyntaxError: expected expression, got '<'2.c23262ff.chunk.js:1
Uncaught SyntaxError: expected expression, got '<'main.361ee52b.chunk.js:1
As I said, everything runs smooth on localhost without any problems so my paths to imported files should be ok. So I am totally clueless about what could be the issue here.
I've already read through some threads here concerning this issue but I could not found the same exact problem. Most of the people have wrong paths included in there hrefs, which is not the the case here I think.
Somebody has any idea please?
Thanks in advance!
I've been trying to understand why body.prependAsync() does not work only on Outlook for Mac (current UI with Microsoft365 Subscription). For all other browsers and Outlook for Mac (new UI with Microsoft365 Subscription), it is working perfectly; meaning the body of the email is being populated correctly. The API version being used is 1.7 and I can see that it's supported in this documentation.
The error that I'm receiving in the callback from body.prependAsync() is:
[2006] Invalid Format Error : The format of the specified data object is not valid.
In the error code documention, I see that this error could be caused by the following: The solution developer supplies an invalid HTML or OOXML string, a malformed HTML string, or an invalid OOXML string.
However, the body message needing to be displayed is a properly formatted HTML. I've even tried a regular string but still getting the same error.
The way I am calling it:
Office.context.mailbox.item.body.prependAsync(
'test',
{coercionType: Office.CoercionType.Html},
callback
)
Any advice is greatly appreciated. Thanks!
My site is slow after adding recaptcha, so looking at Google Developers Console I see some errors. I have been using v2 of recaptcha then tried to switch to v3 but had no luck, so I switch back and I think some of the errors are remnants or left over code from v3. I am not sure how to find and remove. I thought I had it all removed but must not.
I thought I had removed all forms of code related to v3 but with this error and that key I must not have.
Uncaught Error: Invalid site key or not loaded in api.js:
XXxXxXXXXXXXXXxxxXxXxxXXXxXxXXXxXXxXxXWXx
at Object.Gu [as execute] (VM3003 recaptcha__en.js:513)
at Object.execute ((index):273)
at executeOnHomepage ((index):273)
at A4 (VM3003 recaptcha__en.js:512)
at X (VM3003 recaptcha__en.js:518)
I would like to remove get rid of this error so my site loads faster and continue to improve my site performance.
I The example given on [PlaceAutocomleteAddressSearch][1] is not working for me.
I am getting 2 errors getting an Uncaught fc Tg error in the console
looks to be in line 97. error text is
throw _.gc(a+" is not a function");return function(){c.apply(d)}};
[1]:
the other error is cannot read property 'setBounds' of undefined.
I am using the exact same code as in the example so I don't get what is wrong.
https://developers.google.com/maps/documentation/javascript/examples/places-autocomplete-addressform
I found the problem since I am checking this on localhost, geolocation is disabled as of march 2016, so the geolocate example will not work since the browser doesn't support navigator geolocation if the site is not using https.
I'm trying to port the Twitter Notifier extension to FF.
I'm not too familiar with JavaScript so I just used extension factory to convert it to FF.
Unfortunately it is not working; I don't get any HTML5 desktop notifications.
I've looked at the code a bit and I think the problem is with twitter.js which should be found in the path 'resources\extension-data\js'.
http://pastebin.com/C0NqU4Ur
First I've changed
twitter.messagesDB = window.webkitIndexedDB.open("messagesDB");
to
twitter.messagesDB = window.mozIndexedDB.open("messagesDB");
but it still is not working.
The error console also doesn't show any error.
When I put a console.log command to the twitter.messagesDB.onsuccess function nothing is being outputted to the error console.
Also no output when I create an onerror function.
So I though to surround the functions with a try and catch clause but no error is being thrown.
So I tried to put twitter.messagesDB = twitter.messagesDB.result; out of the function and the following error shows up in the error console:
Error: uncaught exception: [Exception... "A mutation operation was attempted on a database that did not allow mutations." code: "6" nsresult: "0x80660006 (NS_ERROR_DOM_INDEXEDDB_NOT_ALLOWED_ERR)" location: "chrome-extension://gjlehiopfilnaggndcmbhphaglkbkekf/js/twitter.js Line: 28"]
What does that mean?
How can I make it work in Firefox?
Thanks in advance!
Edit: I'm using Firefox 12 on Windows
This is due to an incompatibility between the Firefox implementation of IndexedDB, which supports the latest IndedexDB protocol published December 2011, and the Chrome implementation, which supports the version previous to that.
The breaking change is how databases are created, where the older (Chrome) implementation uses the setVersion transaction whereas the newer version (FF) uses an onupgradeneeded event and callback.
To see this change, please star this issue.