I'm new to JS/D3.js (so thanks in advance for any support). I'm trying to create a basic sankey diagram using Gerardo's d3.v5 fork https://bl.ocks.org/GerardoFurtado/ff2096ed1aa29bb74fa151a39e9c1387 however when I try to run the same script I'm getting the error:
"Uncaught TypeError: sankey.link is not a function"
What am I missing? Looking through the latest version of d3-sankey I cannot see the function, is this from a previous version of d3-sankey? Whats the alternative now if that is the case?
MB's v0.5.0 update to D3-sankey replaces the use of the sankey.link with d3.sankeyLinkHorizontal. Due to splitting out the script from the original HTML when copying this in to my text editor, it began calling the latest version that doesn't have the function.
After copying in the whole html code into a single file its working.
Recently I have updated the wocommerce version to 3.1.2. But I am fetching problem when going to add variable product or editing variable product. It showing "Uncaught Error: Option 'ajax' is not allowed for Select2 when attached to a element." js error when selecting product attribute or variation.
Uncaught Error: Option 'ajax' is not allowed for Select2 when attached to a <select> element.
at String.<anonymous> (ultimate-woocomposer-backend.min.js:1)
at Function.each (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-ui-position,jquery-ui&load[]=-menu,wp-a11y,jquery-ui-autocomplete,underscore,backbone,wp-util,wp-backbone,media-models,plupload,jquery-ui-tooltip&ver=4.8.1:2)
at d.prepareOpts (ultimate-woocomposer-backend.min.js:1)
at d.prepareOpts (ultimate-woocomposer-backend.min.js:2)
at d.init (ultimate-woocomposer-backend.min.js:1)
at HTMLSelectElement.<anonymous> (ultimate-woocomposer-backend.min.js:2)
at Function.each (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-ui-position,jquery-ui&load[]=-menu,wp-a11y,jquery-ui-autocomplete,underscore,backbone,wp-util,wp-backbone,media-models,plupload,jquery-ui-tooltip&ver=4.8.1:2)
at a.fn.init.each (load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-mouse,jquery-ui-sortable,jquery-ui-position,jquery-ui&load[]=-menu,wp-a11y,jquery-ui-autocomplete,underscore,backbone,wp-util,wp-backbone,media-models,plupload,jquery-ui-tooltip&ver=4.8.1:2)
at a.fn.init.a.fn.select2 (ultimate-woocomposer-backend.min.js:2)
at HTMLSelectElement.<anonymous> (wc-enhanced-select.min.js:1)
See the screenshot below;
I have googled about this problem but no solution found, most of them are saying it is a bug (I am not sure).
Please help to resolve the problem.
Regards
I know it's been a while, but I just want to share what I found and might can help someone else.
I got same issue with attribute section will stay in the loop, exactly same error I got in the console.
Here's I try:
Disable most common conflict plugin with this same error case I found online.
Disable Yoast SEO (which still not working for me, then just turn them back on)
Disable Visual composer, like page builder plugin, when I turn off "Ultimate_VC_Addons" this plugin, my attribute section is working agaian.
Might cause the conflict by theme, fall back to Wordpress default theme to check.
If cause by Advance custom field, you can check this thread.
Check this woocommerce doc if none of this help.
While upgrading dhtmlx to 4.1.3 pro, I am getting following error while loading dhtmlx js file in my document:
ReferenceError: dhtmlXCellObject is not defined in dhtmlxtabbar.js(line 1204)
Please do help if any one have got the same.
It seems like you're using tabbar source in your code and forgot to include sources\dhtmlxCommon\codebase\dhtmlxcontainer.js before it.
I am trying all ways possible to resolve the JQuery Conflict issue in magento. Verified a few forums too but of no help.
I have tried the following:
1.Added jQuery.noConflict(); at the end of the jquery files (still didnt work)
2.Created a variable for noConflict and used all functions (still didnt work)
I can see the Js and CSS files required for jCarousel to function in the output source code, however along with that i get the following error:
jQuery("#mycarousel").jcarousel is not a function
Line 80
Not sure what I'm missing.
I am a newbie to magento. Is there a possibility that I'm missing on some important files to update.
Please assist as soon as possible.
I'm Following the examples of JCarousel as closely as possible. It works fine without Magento, but in Magento error as mentioned above is returned.
Check out the view source and make sure that the JCariusel scripts are inserted after JQuery.
I had the same problem, the it would not load within the magento site. I did however figure it out. I found that my code:
jQuery(".time_slider").jCarouselLite({
btnNext: ".next_time",
btnPrev: ".prev_time",
circular: false,
visible: 4,
speed:1000
});
Was not being loaded into the theme due to it not having a
jQuery(document).ready(function() {}
I also made sure that the jcarousel had a no conflict within the file and that it was loaded before the slider itself in the page.xml file.
Hope this helps. I also found that i had trouble with my no conflict in jQuery. If this doesn't help that is where the problem lies.
I am trying to install a jQuery site tour, using the following tutorial http://tympanus.net/Development/WebsiteTour/
I think I installed everything correctly, and the navigation box seems to work ok, but only a couple of the tooltips show, and the tour doesn't seem to want to scroll down to my footer.
In Firebug, I'm getting the following error: $elem.offset() is null
[Break On This Error] var e_l = $elem.offset().left;
This is the site address: http://www.aeringuy.com/dev/
Can anyone point me in the right direction for trouble shooting this?
Thanks,
Yukon
The files 'ChunkFive_400.font.js' and 'pos-handle40.png' are missing and are returning the 'This Site is Under Construction' page with incorrect HTTP Status Code (200 OK) and I think that's causing the problem. Blame the 'Maintenance Mode Plugin' author, either disable it or fix those missing files.