I was trying to implement a project using alasql in an IE8 environment but keep getting the same error. The alasql function isnt executing properly.
I get the following error-
Expected identifier
File: alasql.min.js, Line: 7, Column: 9848
i get this error even when trying to run the most basic code possible which is given below -
var res = alasql('select * from xlsx("xlsxURL")',[],function(res){
console.log(res[1])
});
Is there any way to make it IE8 compliant ?
Related
R version: 4.1.0
Shiny Server v1.5.16.958
Node.js v12.20.0
I have a shiny-server script that I'm having issues with. When I call this script using a web browser, I immediately get: "Disconnected from the server. Reload". Upon inspecting the browser debug console, I received this debug information that I'm not quite sure what to do about. Does anyone have any ideas on how I can resolve this? :
Listening on http://127.0.0.1:46259
gdata: read.xls support for 'XLS' (Excel 97-2004) files ENABLED.
gdata: read.xls support for 'XLSX' (Excel 2007+) files ENABLED.
Attaching package: ‘gdata’
The following object is masked from ‘package:stats’:
nobs
The following object is masked from ‘package:utils’:
object.size
The following object is masked from ‘package:base’:
startsWith
Attaching package: ‘bizdays’
The following object is masked from ‘package:stats’:
offset
Warning: Error in Calendar: could not find function "Calendar"
[No stack trace available]
Error in Calendar(hdays, weekdays = c("saturday", "sunday")) :
could not find function "Calendar"
shiny-server-client.min.js:1 The application unexpectedly exited.
We have figured out the problem. Bizdays has deprecated the function 'Calendar'. In our Server.R file we had to update the code to use 'create.calender' instead.
I remember getting this error a lot a while before. Today I wanted to show it to a friend unfamiliar with Javascript. Chrome and Safari instead gave me something like:
> const o = {};
< undefined
> o.doge()
< TypeError: o.doge is not a function (In 'o.doge()',' 'o.doge' is undefined)
Chrome and Firefox seem to be user-friendly as well.
How can I get an original error, without this helpful message?
You will never get that error in a modern browser; the error comes from js engine itself not the browser; and if there are no others other than that Type Error, modern engines will return a more developer friendly error by applying a (similar) /(w+)/ regex on what ever typed before () and placing it in the error message check out:
v8 (chrome) message templates that will make the error string (line 51, 52):
T(CalledNonCallable, "% is not a function")
and SpiderMoneky (mozilla) message templates (at line 51, 54):
MSG_DEF(JSMSG_NOT_FUNCTION, 1, JSEXN_TYPEERR, "{0} is not a function")
non-callable test case in v8 and a SpiderMokney test case .
So the only way to a undefined is not a function error message in a modern browser is doing undefined() :)
undefined()
you can just try to find and download an older version of the browser which logged the original error. (if that version is still publicly available).
I trying to import/install a client certificate into IE but I'm getting following error in my js code.
function ImportClientCertificate()
{
try {
var objCertEnrollClassFactory = document.getElementById("objCertEnrollClassFactory");
var objEnroll = objCertEnrollClassFactory.CreateObject("X509Enrollment.CX509Enrollment");
var sPKCS7 = "-----BEGIN CERTIFICATE-----" +
"MIIDADCCAmkCCQ..." +
"-----END CERTIFICATE-----"
objEnroll.Initialize(1);
//->this line causes the exception
objEnroll.InstallResponse(3, sPKCS7, 1, "correctpassword");
}
catch (ex) {
alert(ex.description);
/*Exception being thrown: CertEnroll::CX509Enrollment::InstallResponse: Access is denied. 0x80070005 (WIN32: 5 ERROR_ACCESS_DENIED)*/
}
}
What could be the reason for this exception? I already tried to set the security level in IE to low but it doesn't helped. Manual installation of the cert into the users private cert store works fine.
Any help is highly appreciated.
I'm surprised this worked for you!
I found that I had to change the restrictions parameter (3 in your example) to be either 0 or 4. This is based on the MSDN documentation at https://msdn.microsoft.com/en-us/library/windows/desktop/aa378051(v=vs.85).aspx:
E_ACCESSDENIED
This method was called from the web and either AllowNoOutstandingRequest or AllowUntrustedCertificate was specified in the Restrictions parameter.
After two days of research on the net, I finally find out how to get this script working. The only solution I found for IE 11, is to enable following option in the IE settings box.
I am using a JavaScript error logging tool to log any JavaScript errors on my mobile site and I am seeing a large number (22,000 in under a month) of this error:
Uncaught TypeError: Cannot read property '_pmh' of null
I can see from the addthis_widget.js code that it is originating from that script.
I can also tell that it only affects mobile Android and Google Chrome browsers, these in particular:
Android 4, Android 4.1, Android 4.2, Chrome 11, Chrome 18, Chrome 25, Chrome 26, Chrome 27, Chrome Mobile 18, Chrome Mobile 25, Chrome Mobile 26
I am using the following external JavaScript include:
http://s7.addthis.com/js/250/addthis_widget.js#username=xa-4b6adff375a64db9
and have the following configuration object set:
<script type="text/javascript">
var addthis_config = {
data_ga_property: 'UA-18721873-1', // real GA profile hidden for privacy purposes
data_ga_social: true
};
</script>
Is there anything I can do to prevent this error from occuring so many times on these browsers?
I have located the cause of this issue and it is down the following code.
if (window.addthis) {
window.addthis = null;
window._adr = null;
window._atc = null;
window._atd = null;
window._ate = null;
window._atr = null;
window._atw = null;
}
This was an attempt to cleanup the objects lying around when moving between pages dynamically to prevent memory issues.
addThis now provide support for this problem, their support department sent me the following link:
http://www.addthis.com/blog/2013/05/07/a-brief-history-of-using-addthis-dynamically/#.Uklx4RCKyas
and the following explanation/information:
Along with other information from my peers and such, I've come up with
the proper code which should be executed when moving from virtual page
to virtual page such as in your mobile application. Rather than
nulling any of the AddThis related objects, they must be left alone.
When the page URL or Title (or any other AddThis configuration option)
that you want to be used by our buttons changes, you should execute
our method:
addthis.update(type, key, value)
It takes the three parameters: type, key, value.
Type is either "share" or "config". The key is the same key you would
set according to our API documentation. What you likely need to know
are just the two keys: "url" and "title". The value is of course the
value you want those options to have.
After you have updated all of the options you need to update using
that method, you need to invoke this method:
addthis.toolbox(cssSelector)
The cssSelector is usually going to be ".addthis_toolbox" but if for
some reason you don't want to refresh all of your toolboxes, you can
be more specific about it.
Once you have made those changes to your code, I believe that our
tools will work properly for you and that there will be no more "null
object" related javascript errors.
You can look at this JSFiddle to see an example of dynamically
changing content: http://jsfiddle.net/j5addthis/r6Utv/
I'm having the same issue, but it appears that there was, at one point, a fix to your specific case above by simply upgrading the script that you're using from addthis to version 3.0 by changing this:
http://s7.addthis.com/js/250/addthis_widget.js#username=xa-4b6adff375a64db9
To this:
http://s7.addthis.com/js/300/addthis_widget.js#username=xa-4b6adff375a64db9
Read more here: http://support.addthis.com/customer/portal/questions/1021465-addthis-widget-js-throwing-cannot-read-property-pmh-of-null-error-on-android-and-chrome
Note though, as I mentioned above, my issue continues to persist even with version 3.0 despite the AddThis help desk stating that should work.
I am getting below exception in runtime, could anybody suggest what is wrong?
Microsoft JScript runtime error: Object expected
Exception is coming in very first line:
aspxAddHoverItems('tabMaster',[[['dxtcTabHover_Glass'],[''],['T0','T1','T2','T3'],['','T'],[[''],[''],[''],['']],['Img']],[['dxtcActiveTabHover_Glass'],[''],['AT0','AT1','AT2','AT3'],['','T'],[[''],[''],[''],['']],['Img']]]);
var dxo = new ASPxClientTabControl('tabMaster');
window['tabMaster'] = dxo;
dxo.uniqueID = 'ctl00$tabMaster';
dxo.RegisterServerEventAssigned(['TabClick']);
dxo.emptyHeight = true;
dxo.emptyWidth = true;
dxo.tabCount=4;
dxo.InlineInitialize();
aspxAddHoverItems is simply unrecognized as the error suggests. Be sure to include all necessary references and assemblies in your project.
This may be just what you need: How to: Manually Register DevExpress Extensions to Start Using Them in an MVC Web Application
Some additional reading: Google Search: aspxAddHoverItems is not defined