Closed Tarang closed 11 years ago
from this https://groups.google.com/forum/?fromgroups=#!topic/meteor-talk/gYgYhv88nB4 it looks like 0.6.0 might be a problem
either way, it seems like the problem is actually with meteor scoping effects on x-editable, the 'package' itself appears to be still constructed properly as best i can tell
if you can provide a example project with this issue or at least significantly more details i'll take a look at it - finally upgraded my project to 0.6.2 and this works fine - closing for now, may reopen
My project only uses the HTML5 WYWIWYG editor, could you check your js console btw. Do you get a Uncaught TypeError: Cannot read property 'defaults' of undefined
. I'm also running 0.6.2 but still have the issue. Ill test a bit more and get back. I have got it working by copy pasting all the contents of the js files into the browser & it does work so it might also be a file order issue
OK so Ive played around a bit, I manually deleted my x-editable in meteor at /.meteor/meteorite/packages
and reinstalled it fresh and it got rid of the error attempting to read $.fn.editable.defaults.mode
. But the wysiwyg editor still throws up a Uncaught TypeError: Cannot read property 'Editor' of undefined
should be fixed
The new 0.6.0 version of meteor seems to break it. The error is a
Uncaught TypeError: Cannot read property 'defaults' of undefined
Perhaps its to do with the variable scoping?