New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: d.publicMethods is undefined #129
Comments
I'm not sure what this could be. Easytabs has a |
I tried enabling Strict Warnings in Firebug, but I still couldn't get the error. When I switched to the non-minfied version, I noticed I had commented out lines 700 through 702 because the error was breaking other scripts.
|
I re-uploaded the easytabs library to my server and now I'm getting this: Firefox:
Chrome:
Firebug:
It's obviously line 698. What could be causing it not to recognize |
That is super weird. After the page loads, open the console and try something like
and see what it says. I haven't done any testing yet with jQuery 2.0. I'm wondering if maybe it returns something other than |
I tried switching to jQuery 1.10.2, but that didn't change anything. However, I tried |
Instead of calling var el = $('#navbuttons');
var plugin = new $.easytabs(el.get(0));
el.data('easytabs', plugin); And then try: console.log($('#navbuttons').data('easytabs')); |
Oops! I forgot that I am using no conflict with jQuery! When I put in:
I get:
I tried using I could not test turning off the conflicts because it would break anything and everything jQuery on the page, but does the easytabs library use the |
No, the library uses Can you explain what you mean by "not specifying the options and event hooks would cause errors on the page anyways"? The intention was to instantiate easytabs while bypassing the code that causes the errors so that you could see the value of Anyway, it looks like you got the console log to work. But that Also, how exactly did you call the |
Oh, I see, you're calling OK, so Of course, in the console, we don't need to call Though if you have multiple instances on the page with the same selector, maybe that's why it's returning true instead of the object. If that's the case, try this from the console instead:
And see what that returns. |
Oh okay, I thought you were saying you had multiple instances on the page. I have to say, I'm totally stumped. I have no idea why it would have |
Actually, I am using the HTML5 Doctype. I really prefer HTNL5 over the old HTML4. What's odd is that this just randomly started happening. |
Can you maybe list all the JS libraries that are being loaded on that page? All I can think is that some library is messing with jquery's data function or even patching JS Object's prototype (a big no-no). |
Same problem here, tested jQuery 1.7, 1.8 and 1.9 all same problem. Also using HTML5 doctype but that shouldn't be the problem as the demo website is also using it. Tried disabling other plugins but with no success. My hrefs are matching the ids of the panels, even when i just literally copy the demo HTML it is not working. |
I wonder if it's jQuery UI causing the issues. Can you try without that? Also, what browser(s) is this? |
Same error here. I've tried disabling jQuery UI, bootstrap.js, and all other JS except jquery.js... no luck :( Using jQuery 1.10.2. However, I found that the error disappeared if I removed data-easytabs="true" from the containing div. That was markup I had incorrectly copied over from the examples, and it was causing the error. |
nicolasconnault's solution worked for me. Just remove data-easytabs="true" |
@nicolasconnault I can confirm, this gets rid of error in console |
@nicolasconnault works!! |
@nicolasconnault you're my savior ! |
@nicolasconnault solution worked for me. Just remove data-easytabs="true" |
I recently re-uploaded the EasyTabs script to my website (v3.2.0) and must have undone an edit I made to it. The EasyTabs do not load the Ajax content and when clocking on a tab, it goes to a bad URL. On pages without any EasyTabs , I get no errors. However, on the page there is I get this:
Recently, I noticed that it stopped doing this, but the other problems metioned still remain.
Here is my code:
jQuery 2.0.2
Firefox 23
The text was updated successfully, but these errors were encountered: