-
Notifications
You must be signed in to change notification settings - Fork 4
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
Issue when using with WordPress jQuery #10
Comments
Example showing the issue in the browser console (the JS I just pasted in the jQuery followed by the skeletabs script) |
Thank you for raising the issue! It seems like we cannot reference jQuery at the time of skeletabs initialization. I will need to launch some tests to work around the issue; will get back to this as soon as I get time for it. |
Bumped a new version v2.1.3-alpha.0 with a fix to webpack configuration file. You can find a working demo with jQuery in WordPress build here. @wplit @nickpish Please try the new version, if the issue persists in your specific setups, please leave a comment. I will leave this thread open for a while. |
@findawayer Wow, thanks for the quick turnaround! I will try it today and report back. |
@findawayer I can report your updated version is working w/ my WordPress project- thank you! On a different note- I'm seeing that when the |
Glad to know it worked with your app! Skeletabs need a little more adjustments when it comes to a nested structure, like you just described so, I will take a look on the issue soon and try to find a solution. Please keep track of upcoming patches. 👊 |
Will do! Thank you for putting together such a great plugin! I will certainly use it in other projects. |
Only when using WordPress, there is an error when the skeletabs.js script is added to the page. This happens just by adding the script to the page.
skeletabs.js?ver=5.6:1 Uncaught TypeError: Cannot read property 'extend' of undefined
the browser console is pointing to this part of the code and afterward having issues..
classNames_classNames=$.extend({},defaults);
The text was updated successfully, but these errors were encountered: