angular.element(...).fullpage is not a function

Question

angular.element(...).fullpage is not a function

trsh opened this issue 8 years ago · comments

Janis commented 8 years ago

Any ideas on this

modules.js?hash=f6ba1da…:23670TypeError: angular.element(...).fullpage is not a function

??

Mathew Kleppin · Answer 1 · Wed May 18 2016 02:12:13 GMT+0800 (China Standard Time)

are you including the full-page library? Could you put up a plunkr or jsbin example that I could take a look at?

Janis · Answer 2 · Wed May 18 2016 14:38:42 GMT+0800 (China Standard Time)

No I cant. I'm using meteor. Big decency tree :(. And I am including full-page library. One thing comes in my mind is that full-page is set as fn of JQuery, anuglar.element is JQLite and another scope. By idea it should not work. Your thoughts?

Janis · Answer 3 · Wed May 18 2016 14:45:50 GMT+0800 (China Standard Time)

When changing in that line angular.element to $, it works. Any thoughts?

Janis · Answer 4 · Wed May 18 2016 14:48:37 GMT+0800 (China Standard Time)

P.S. im on angular 1.5.5

S.Virmasalo · Answer 5 · Mon May 30 2016 19:02:17 GMT+0800 (China Standard Time)

@trsh, I looked at angular-fullpage.js and notised that the directive is not full-page but fullPage.
Atleast the error disappears when you change that.

Janis · Answer 6 · Tue May 31 2016 14:28:42 GMT+0800 (China Standard Time)

@svirmasalo strange. I have lot of directives like BlaaBleeBaa, and they work by using them like blaa-blee-baa. Angular handles that.

S.Virmasalo · Answer 7 · Tue May 31 2016 14:31:54 GMT+0800 (China Standard Time)

@trsh yeah I think that was not the problem after all. Got things to work after I re-ordered scripts like they are presented at the Install part of readme.

Mathew Kleppin · Answer 8 · Wed Jun 01 2016 05:05:24 GMT+0800 (China Standard Time)

@svirmasalo You should actually load jQuery first, before angular. That way angular doesn't have to load its jQuery Lite library alongside jQuery. (my docs show angular first,ill update that). The directive is camelcase, but for putting it on dom, you should use hyphens instead of camelcase (at least that's the way it is in the style guides)

closing this issue because it seems to have been resolved? let me know if the issue is still present for you @trsh after the fixes in this thread

Janis · Answer 9 · Wed Jun 01 2016 22:03:01 GMT+0800 (China Standard Time)

@hellsan631 I resolved It by changing angular.element to $ in directive (original line -> angular.element(element).fullpage(sanatizeOptions(scope.options));). So The original code is still throwing the same error. I'm loading libs in correct order.