I am trying to: display an audio player for each song listing in the loop, the first item does not load the player but keeps spinning, the second item plays the audio from the first item, but displays all the other information for the item correctly
Link to a page where the issue can be seen: hidden link (scroll down to view all songs)
I expected to see: the audio player for the first item stop spinning and play the associated audio, and for the other players to play their respective audio.
Instead, I got: the audio of the previous item.
The audio player is generated by the WavePlayer shortcode.
All of the views using a song listing are having the same issue.
I've deactivated all plugins except Toolset, WooCommerce and Waveplayer and switched themes to TT1, the issue is still persisting.
Code in loop is
<div class="container">
<div class="item first">
[waveplayer skin = "inline-play" size = "md" ]</div>
<div class="item second">
[wpv-post-link]
[types field='mood'][/types]
</div>
<div class="item third">
[wpv-woo-product-price]
</div>
<div class="item fourth">
<a class="button" href="[wpv-post-url]">View and Buy</a>
</div>
</div>
I've given admin access via the temporary login plugin - the link is in the username field below.
Hi,
Thank you for contacting us and I'd be happy to assist.
I noticed that the view "List all songs" is set to use the content template "loop-item-in-list-all-songs", to show the individual loop items.
I included the suppress_filters="true" attribute in that template's shortcode and the audio player is fixed now:
( ref: https://toolset.com/documentation/programmer-reference/views/views-shortcodes/#wpv-post-body )
[wpv-post-body view_template="loop-item-in-list-all-songs" suppress_filters="true"]
It appears some content filter from the active theme or a third-party player was affecting this and by including suppress_filters="true" attribute, the extra content filters are removed from the template's output.
regards,
Waqar
Waqar - thank you so much for your assistance, very grateful indeed.
My issue is resolved now. Thank you!