FinalsClub / karmaworld

KarmaNotes.org v3.0
GNU Affero General Public License v3.0
7 stars 6 forks source link

jquery not found when running note-editing branch in prod-like environment #400

Closed btbonval closed 9 years ago

btbonval commented 9 years ago

Both my local VM and Beta are using the same cloudfront CDN and S3 bucket.

Beta, the staging system, has no jQuery errors. Everything looks fine. It is including jQuery as part of a compressed JS file: https://d2ry5v6uki5dz0.cloudfront.net/static/CACHE/js/b96ad19ec98b.js

Turns out the local VM, running note-editing branch, is also using the same compress JS file for jQuery (no updates were made to that chunk).

Yet the VM server is causing jQuery missing errors on console (and notes don't load visibly, although they load in the network tab).

ReferenceError: $ is not defined 1st-lecture:875
ReferenceError: $ is not defined setup-ajax.js:14
ReferenceError: $ is not defined pxem.jQuery.js:12
ReferenceError: jQuery is not defined annotator-full.min.js:16
"Annotator requires jQuery: have you included lib/vendor/jquery.js?" annotator-full.min.js:16

ReferenceError: $ is not defined  1st-lecture:907
btbonval commented 9 years ago

On the VM local version of the site, the network tab says it took 9108ms to download https://d2ry5v6uki5dz0.cloudfront.net/static/CACHE/js/b96ad19ec98b.js and that it was 200 OK. So jQuery should be available.

btbonval commented 9 years ago

reverted VM to master, loaded page, no jQuery errors. Only a 403 forbidden against some typekit link.

btbonval commented 9 years ago

I'll do commit-by-commit regression testing later :(

btbonval commented 9 years ago

testing held up because #397 is going on again. keep getting error 500 from offline compression and disabling it does not seem the appropriate course of action.

btbonval commented 9 years ago

So far no problems with jQuery on the note-editing branch. There's no HTML to be shown, of course, for the chosen example which was based on a migrated static note.

btbonval commented 9 years ago

This error appears to have cleared itself since the newer code was written and a fresh migration was performed.