I checked it and it looks like the player is also loading with an ajax call rather than being immediately available, is this something that's customizable? Could you let it fixed in the page to avoid this conflict with the Toolset ajax calls?
I checked their plugin and it looks like there's some code meant to remove the player depending on the type of event:
delete window.generated_the_eddmp;
This could be the culprit but it needs some double-checking.
To help address this, I recommend contacting the plugin developers of 'Music Player for Easy Digital Downloads'. Please explain that the audio player works correctly on initial page load but disappears or fails to reload after using AJAX filters provided by Toolset Views. Suggest that the issue could be related to the player not being re-initialized properly after the AJAX call, which might be preventing it from rendering on the page.
Also, please mention that they can use the following jQuery function to catch the Toolset AJAX filter events and execute the necessary code to load or reinitialize the player:
jQuery(document).on('js_event_wpv_pagination_completed js_event_wpv_parametric_search_results_updated', function(event, data) {
// Code to reinitialize or reload the player
});
This function triggers whenever an AJAX event completes, which should allow them to re-run any initialization code required to display the player correctly. It looks like there's a function eddmp_force_init() within the file music-player-for-easy-digital-downloads/js/public_src.js that can be used to rebuild the player but I couldn't get it to work, not even directly in the console.
By providing this information to the plugin developers, they might be able to offer more targeted support or suggest an alternative method to ensure the player displays correctly after filtering.
Please feel free to follow up if they provide you with new information so that we can reassess it.
