Develop Reference

Buddypress jq.cookie not a function

Having some issues with Buddypress, I have installed nearly every version since 2.7 and I still get the same issue with
Uncaught TypeError: jq.cookie is not a function
I found in the folder
plugins/buddypress/bp-themes/bp-default/_inc
there is a js file called
global.js
first line in this file is
var jq = jQuery;
I realise this is not correct as my jQuery uses $ not jQuery
I tried changing this, however.
console log still shows that its not a found function.
I'm using $. cookies in other javascript. So jQuery cookies are installed.
Also, no matter what i change in this global.js
it still results in the same output as a
# VM31193:1784
in chrome inspector as the original file.
Can anyone help me with this?

Enabling OimoJs in babylonJS

I've got a little project running that uses Babylonjs to render a game, I've got the game 'rendering' and am happy with the progress and have decided to add physics, I went with oimojs as its the standard and was informed that 'enabling' it was as simple referencing the oimo.js file and calling:
scene.enablePhysics();
But when I call this I get the following error:
babylonjs.js:20 Uncaught TypeError: OIMO.World is not a constructor
The only thing I can think of is if the error is perhaps the file I'm referencing is the incorrect one? I pulled the file from:
http://lo-th.github.io/labs/
Is there something new you have to do now? Am I missing something? Or am i just silly and referencing the wrong OIMO.js file?

This seems to be a very old question (and I wonder how I missed it so far), but just for future reference -
Babylon.js has the oimo.js version that is tested and working directly in the repository. If you look here - https://github.com/BabylonJS/Babylon.js/tree/master/dist , the Oimo.js file you see there will work the the latest Babylon version.

Errors in Ajax Control Toolkit's JS files after upgrade?

I upgraded Ajax Control Toolkit to v15.x and have been working on cleaning up the code after doing so. I'm running across exceptions being thrown, and VS breaks at points in the toolkit's JS files. I'm not sure why or how.
I've already double-checked that any scripts are not referenced multiple times, as was the leading suggestion on Google, but I still haven't figured it out.
I really need some help with this, as I have two months invested in this project. By the way, I'm using VS2013 and the project is in ASP/VB.
Here are a couple of the errors (to get the next, I've hit Continue):
Unhandled exception at line 1647, column 38 in
http://localhost:50236/ScriptResource.axd?d=D9drwtSJ4hBA6O8UhT6CQmpVfriIlRNRich93DvwGtp67E1h_mWKZOFWLDGS9BMtlj8olqCr6zhXtNsVz0umlIymKK0GfDoqTLzNLe2YQI2ElwoX58_2MZEcEFLKjdG6fbv26oE3vanxWpdhskXpgCIAYbDVlsaWWDXPE-98sV01&t=ffffffffb53e74b8
and
Unhandled exception at line 785, column 42 in
http://localhost:50236/ScriptResource.axd?d=D9drwtSJ4hBA6O8UhT6CQmpVfriIlRNRich93DvwGtp67E1h_mWKZOFWLDGS9BMtlj8olqCr6zhXtNsVz0umlIymKK0GfDoqTLzNLe2YQI2ElwoX58_2MZEcEFLKjdG6fbv26oE3vanxWpdhskXpgCIAYbDVlsaWWDXPE-98sV01&t=ffffffffb53e74b8
0x800a139e - JavaScript runtime error: Sys.InvalidOperationException:
Type Sys.Timer has already been registered. The type may be defined
multiple times or the script file that defines it may have already
been loaded. A possible cause is a change of settings during a partial
update.
0x800a139e - JavaScript runtime error: Sys.InvalidOperationException:
Type Sys.Extended.UI.BoxSide has already been registered. The type may
be defined multiple times or the script file that defines it may have
already been loaded. A possible cause is a change of settings during a
partial update.
Any and all help is appreciated! Thanks!

As it turns out, I followed the instructions on the Ajax Control Toolkit website on "un-bundling" the scripts, and now everything works. Apparently I didn't do something right, or the instructions were wrong. More than likely, the former.

Socket.io failed to load websocket.js

I tried to use socket.io in an simple app.
When it is calling the following js file:
node_modules\socket.io\lib\transports\websocket.js
The following line failed to load (It didn't really fail. It actually returned some empty result and failed some later codes using protocolVersions):
var protocolVersions = require('./websocket');
I debugged a little bit and it seems that the intention of this line is to load the following js file:
node_modules\socket.io\lib\transports\websocket\index.js
However because there is also a "websocket.js" (the file being run) under the "transports" folder, the require functions always tries to load "websocket.js" instead, and return some unexpected results.
I changed the folder name to "websockets" and call "require('./websockets')" instead, and it fixed the problem. However this is a shared library I am not feeling comfortable messing up its codes.
I am trying to understand why this problem happened this way and what should be the best way to work around it. I am sure this piece of codes has been well tested before released.
You probably already noticed that I am using backslash '\' to separate the path. Yes I am running it on Windows! Will that create any difference?
Thanks!

Now.js Uncaught TypeError: Object#<Object>

I downloaded the example project from Now.js http://nowjs.com/guide
and when I run it I get
Uncaught TypeError: Object # has no method 'distributeMessage'
after attempting to send a message.
Ideas?

Turns out it was an issue with the PaaS not supporting websockets. Solution was just to explicitly disable them, via something like the following:
nowjs.initialize(server, {socketio: {transports: ['xhr-polling', 'jsonp-polling', 'htmlfile']}});
(resolved in #nowjs IRC)

It's hard for us to know with so little information. If you post your code, we are more likely to know what's going on.
Looking at the hello world demo on the nowjs.com site, it looks like maybe you don't have the helloworld_server.js file included in your page because that's where the distributeMessage() function is defined.
In the demo files here, helloworld.html has this line:
<script src="http://localhost:8080/nowjs/now.js"></script>
But, the demo tgz file doesn't include that. You are probably missing now.js in an appropriate path.