Skip to content
This repository has been archived by the owner on Dec 4, 2020. It is now read-only.

undefined jquery and _ #11

Open
rbobrowicz opened this issue Oct 2, 2014 · 6 comments
Open

undefined jquery and _ #11

rbobrowicz opened this issue Oct 2, 2014 · 6 comments
Assignees

Comments

@rbobrowicz
Copy link

Not sure if this is the right place to report this, but I tried setting up taiga using vagrant. vagrant up completed successfully, but when I tried going to localhost:8000 all I got was a blank page. I checked the console and saw two errors:

Uncaught ReferenceError: jQuery is not defined libs.js:1
Uncaught ReferenceError: _ is not defined app.js?v=1412271620731:1

Is this an issue with the setup scripts or the app itself? If you need anything else from me to diagnose the issue let me know.

@niwinz
Copy link

niwinz commented Oct 2, 2014

This seems that some things was happened with bower install, some dependecies are not properly installed, can you try reprovision again and see if some error is happens?

@niwinz niwinz self-assigned this Oct 2, 2014
@rbobrowicz
Copy link
Author

I tried running vagrant provision and it completes without any errors that I can see, but the issue persists. I still get the undefined jquery and _ errors.

@rbobrowicz
Copy link
Author

So I had some time to debug this issue. The problem is indeed with bower. It tries to pull dependencies using the git protocol instead of https, the port git wants to use is blocked in my company's firewall. This wasn't clear from the vagrant output but become obvious when I ran bower manually and saw it time out.

I fixed it by running git config --global url."https://".insteadOf git:// to force git to use https.

You might want to consider adding this to your provisioning scripts.

@niwinz
Copy link

niwinz commented Oct 3, 2014

It's ok, I will add that to taiga scripts!

Thanks!

@sandeel
Copy link

sandeel commented Dec 11, 2014

I also had this issue with a college firewall. Solution was to rerun bower and gulp in taiga-front when outside firewall.

@gildegoma
Copy link

I also had this issue with a college firewall.

I was also bitten by this beast behind some corporate filters. This would be nice to make vagrant clearly fail and abort on networking errors (e.g. bower or gulp timeouts).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants