Buttonlink parameter does not consider permalink settings

This plugin acts as a wrapper to the native WordPress audio shortcode to add some additional styling so it is unlikely to be possible to add features that do not exist in the audio shortcode.

Hi cubecolor,

thanks for the quick response and a great plugin.

Maybe there is a misunderstanding here. I was talking about the audiotrack shortcode that comes with the audio album plugin. I do believe it hard codes the ‘/?p=’ because I see it in every link that the shortcode renders, independent from the permalink setting I chose in WordPress. And it also always opens the link in a pop up window. That’s why I was wondering whether the function that parses the shortcode could be changed accordingly.

Best regards,
George

Apologies I forgot about the pop up link in the plugin.

This was requested by the owner of the site I was creating this plugin for, as a way for him to display song lyrics whilst the song was playing.

It was agreed at that time that a popup link using the numerical post id of the page containing the lyrics in a shortcode parameter would be appropriate for this. The format of the link should not affect how it works on a site with pretty permalinks. You can see this working at:
https://davedrapercreations.co.uk/music/raynes-park-recordings/ which uses pretty permalinks.

The plugin is unlikely to get any updates beyond ensuring it continues to work if any issues or conflicts arise with a future WordPress update.

It should be possible to create a version to add additional flexibility to this popup feature as you have described, however I would not be able to devote any time to work on this unless it was commissioned as a paid job – which can be discussed via the contact form on cubecolour.co.uk

Hi cubecolor,

thanks for the reference site link. It also creates the ‘/?p=’ but obviously it works with pretty permalinks. It must be because the post ID was used instead of the pretty permalink post name that I tried it with. I will test that and it might already solve my problem.

I definitely understand your requirement for downwards compatibility for any change to the plugin and also that you would charge for an enhancement. At this time, however, I cannot place such an order. If I find a way to achieve my use case with little enough effort I will post it here.

Thanks again and best regards,
George