I was able to fix mine finally. While it may not be a conflicting plugin, it is quite possible that the theme you are using is calling its own scripts in away that makes the DOM skip BP’s loading of jCrop. (I could be way off and may not even be using the terms correctly. In the end, jCrop was inserting into the source code but it seemed like it would be after everything else had ran.) In my case, I looked into my theme’s folder, and found that it had its own “includes” folder. Inside this folder was a “scripts.php” function. From there, I read where it was pulling its scripts from. I then dropped the jCrop into the directory that it was looking into, and inserted the code to load up jCrop. It fixed it. I know this won’t work for you probably, but I hope that I was able to explain it enough of a way that you will be able to find and fix it similar to my example.
Hopefully this will somehow get fixed in the next update, but who knows how long it will take?
Good luck, and I wish I could give a more cookiecutter way of fixing it.
It seems v1.2.4.1 has removed that piece of code. So far, out of scouring the internet for almost a week, I still have seen no type of help or aid in this. A few people have pointed to plugins interfering with the crop functionality but the only plugins I currently have are BP, and the BP Template Pack. I’m still trying to discover a fix myself but would greatly appreciate it if someone a little more code savvy has stumbled upon the fix.
It seems to revolve around jCrop not being a function. However, I inserted the function straight into the page but still can not get it to recognize as a function, which is quite interesting.
