You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. We've used jquery-csv with no issues until we recently upgraded from Zurb
Foundation 2 to Zurb Foundation 3. Now we get a jquery error.
Here's a Foundation2 page which does work:
http://www.nwcouncil.org/reports/financial-reports/2014-99/legal/
And a Foundation3 page which causes an error:
http://www.nwcouncil.org/reports/financial-reports/2014-99/admin
Chart is supposed to appear under "Staffing" heading, but developer console
shows "Uncaught TypeError: Cannot read property 'toArrays' of undefined " at
the line:
$.get(path+"rngHistoryByFunction.csv", function (csvString) {
arrayData = $.csv.toArrays(csvString, { onParseValue: $.csv.hooks.castToScalar });
The Zurb Foundation seems the culprit because changing our two Zurb .js calls
(foundation.js, app.js) from Foundation3 back to 2 fixes the problem.
Original issue reported on code.google.com by [email protected] on 15 Apr 2014 at 6:45
The text was updated successfully, but these errors were encountered:
I'm not familiar with the Zurb Foundation framework or Umbraco CMS.
I assume it has to do with the loading order of scripts. For some reason,
$.csv.toArrays is being called before the jquery.csv.js script is loaded and
attached to the $ namespace.
The order of script definitions matter unless you're using a dependency library
like RequireJS or AMD to load external JS scripts.
Does $.get work without issue?
Are forcing the attached code to wait until $(document).ready() before loading
it? That might help.
I'm getting this too by trying to use $.csv.toArrays from a paste event,
calling it at the point I subscribe to the paste event works fine. I'm very new
to javascript though so I may be doing something wrong.
Original issue reported on code.google.com by
[email protected]
on 15 Apr 2014 at 6:45The text was updated successfully, but these errors were encountered: