First of all: With JavaScript, order matters. If a variable is defined only
after a function is executed that relies on this variable, the function will not work because it doesn’t know the variable yet. The same goes for plugins that rely on a JS framework. The core framework needs to be the first thing and any plugins/extensions/dependencies have to come
after that in the code, otherwise the plugins/extensions/dependencies don’t know what to do.
Look at your code again. Do you see this?
Code:
<script type="text/javascript" src="js/stratus.js"></script>
<script type="text/javascript" src="js/jquery-ui-1.8.18.custom.min.js"></script>
<script type="text/javascript" src="js/jquery-1.8.1.min.js"> </script>
The order is wrong, jQuery needs to come first:
Code:
<script type="text/javascript" src="js/jquery-1.8.1.min.js"></script>
<script type="text/javascript" src="js/stratus.js"></script>
<script type="text/javascript" src="js/jquery-ui-1.8.18.custom.min.js"></script>
Secondly, what’s this?
Code:
!-->Soundcloud player code<--!
…
!-->stratus.js<--!
Did you get that from SoundCloud or did you make that up yourself?
You can’t just write random stuff in your HTML code, proper HTML comments look like this:
<!-- (text here) -->. Like that and nothing else.
Lastly: jQuery’s
noconflict function should only be the very, very,
very last resort and
should only be used if you know what you’re doing (well, that goes for coding in general). Don’t just put it in and think it will immediately solve your problems. Again, order matters. But I’m not gonna explain the proper use of noconflict to you right now because you don’t need it anyway. If you still wanna know then
RTFM.
What does the SoundCloud documentation tell you about including the player code? What you posted here looks messy and is kinda unclear.