ben_del

In my case, I’m animating certain elements of the SVG code using JavaScript. But since the SVG code is loaded after the page load has finished, my animation script is failing, as there is no code present to animate (yet) when it fires.

So, it would be useful if I could specify a callback function(s) that would be fired at the ‘complete’ event of the get request for the SVG code.

I could see two ways to do it:

1) A ‘global’ function to call, which would receive each given SVG as an argument. This could be an option of the plugin. Just a simple text field that would store a function name, which would then be called, passing each returned SVG as it’s main argument each time it’s called. This would be useful if, say, I knew that ALL my animations were going to need to fire an “animateSVG” function.

2) SVG-specific function names. This could perhaps be assigned PER SVG. Somehow at the point of insertion/selection of the SVG image in the WP editor, a function name could be supplied by the user. This would then be stored as a data-callback-XXX attribute on the rendered SVG root node. Then the SVG Support script would search the DOM at the onComplete for elements that had a data-callback- prefix and fire their corresponding functions, again, passing the SVG element as an argument to the specified function.

Those are just how I saw it happening. I’m sure there are many ways you could do it.

Thanks for the reply and for considering the feature addition.

best,

Ben

Right, but that assumes only one way of getting those parameters into the $.fn.almFilter function call. I am allowing my user to select various filters from a <select> menu and am then calling the almFilter function from within my javascript, passing those arguments dynamically. So I am not using data attributes in my HTML at all. I assumed that the key names would just match the shortcode key names. Seems to me like since you are making the $.fn.almFilter available as a public method, that you should not limit it to ONLY being useful if one chooses to use the data-attribute method. Or at least explain that in the docs more clearly. At this point, your example assumes that is the only way someone would use it.

cheers

Doing some more digging… and found that when I have preloaded="true" the AJAX request is NOT getting sent when I use $.fn.almFilter(). If I set it to false, it works.

Seems like this sort of defeats the purpose. If I’m filtering — in my case, using a <select> element to choose a new parameter — I’d like to have the results show up instantly. Instead, as it is now, the user would have to make a selection and THEN hit the “Load More” button to see the results.

Any thoughts on how to workaround this?

thanks.

I did some more tinkering and found that I was causing the problem by updating to the latest jQuery. Here is the code that was causing the ALM script to not load (seems strange that this would cause that). ??

if( !is_admin()){
    wp_deregister_script('jquery');
    wp_register_script('jquery2', get_template_directory_uri() . '/js/vendor/jquery.js', array(), '2.1.4', true);
    wp_enqueue_script('jquery2');
}

Is there a way to continue to use ALM and still use the code above?

Thanks.

I was not able to determine the exact cause of the problem — I checked error logs, but they led to nothing conclusive. I *did* finally choose the “Reinstall Now” option from the Updates page. http://yourdomain.com/wp-admin/update-core.php

This worked for me. I hope it works for some of you as well.

—Ben