Tony Hayes

@jeng22 I’ve replied on Github so I’ll close this ticket here.

@jaxrachel This seems to be happening when there is no current playlist. I’ve taken note of the problem to be fixed for a future update.

Meanwhile, if you are not needing the playlist to display for the particular widget you can set the widget/shortcode to not show playlists and this will bypass the problem.

Otherwise it can be safely ignored in any case, as it is just a warning where a variable is not defined before it is added to.

@begrafx How did you go? Can we close this issue as resolved or is there something further you need to know?

@jaxrachel You can add a custom HTML block to the meta block section this way:

add_filter( 'radio_station_show_meta_block_order', 'custom_show_meta_block_order' );
function custom_show_meta_block_order( $meta_block_order ) {
    $meta_block_order[] = 'website';
    return $meta_block_order;
}
add_filter( 'radio_station_show_meta_blocks', 'custom_show_meta_blocks', 10, 2 );
function custom-show_meta_blocks( $meta_blocks, $post_id ) {
    $website = get_post_meta( $post_id, 'show_link', true );
    $meta_blocks['website'] = '<div><a href="' . esc_url( $website ) . '" target="_blank">Visit Show Website</a></div>';
    return $meta_blocks;
}

As for getting other values, I’d suggest two approaches:
1. you could retrieve the data you want using the REST API as the data endpoints made available via the plugin. You can use javascript to retrieve this JSON data and write HTML from it. Of course you would need to be good with javascript to do this.
2. If the data you want to access doesn’t explicitly have it’s own post meta key already, or it isn’t in the format you want, you could use the save_post hook so that when the post is updated, you can grab whatever data you want and update a post meta value. Then you can retrieve and use that value in Elementor as you are already doing.

The bug with the update has now been resolved and 2.4.0.7 release is available on Github, and will be available shortly via the WordPress repository.

The issue was due to some debug information being output unconditionally. This was mangling JSON data endpoints (prepending to data making them unreadable) and redirections from working (headers already sent error.) Here is the issue on Github:
https://github.com/netmix/radio-station/issues/413

Since the Freemius SDK is indeed updated to 2.3.2 in Radio Station 2.4.0.6, we believe the “unauthorrised AJAX calls” that scanners still are reporting cannot be correct. The scan should pick up the new version with the security patch by Freemius in that version specifically to fix this. We will monitor this and make contact if it doesn’t change.

@jaxrachel If you can let me know any of the line numbers for those errors/warnings if you are still getting any after updating to 2.4.0.7, I can check those out too. I’d expect most/all of them would go away with this bug fixed.

This bug has now been resolved and 2.4.0.7 release is available on Github, and will be available shortly via the WordPress repository.

The issue was indeed due to some debug information being output unconditionally. This was mangling JSON data endpoints (prepending to data making them unreadable) and redirections from working (headers already sent error.) Here is the issue on Github:
https://github.com/netmix/radio-station/issues/413

To prevent confusion I am closing all WP Support Forum issues relating to this bug. If you have any further issues please open a new ticket and we will investigate further. Thank you all for the quick reporting and patience.

This bug has now been resolved and 2.4.0.7 release is available on Github, and will be available shortly via the WordPress repository.

The issue was indeed due to some debug information being output unconditionally. This was mangling JSON data endpoints (prepending to data making them unreadable) and redirections from working (headers already sent error.) Here is the issue on Github:
https://github.com/netmix/radio-station/issues/413

To prevent confusion I am closing all WP Support Forum issues relating to this bug. If you have any further issues please open a new ticket and we will investigate further. Thank you all for the quick reporting and patience.

This bug has now been resolved and 2.4.0.7 release is available on Github, and will be available shortly via the WordPress repository.

The issue was indeed due to some debug information being output unconditionally. This was mangling JSON data endpoints (prepending to data making them unreadable) and redirections from working (headers already sent error.) Here is the issue on Github:
https://github.com/netmix/radio-station/issues/413

To prevent confusion I am closing all WP Support Forum issues relating to this bug. If you have any further issues please open a new ticket and we will investigate further. Thank you all for the quick reporting and patience.

@rvargas17 Sorry this didn’t get the attention it deserved at the time, I have made a Github issue to answer and track these different translation parts.

https://github.com/netmix/radio-station/issues/406

• This reply was modified 3 years, 1 month ago by Tony Hayes.

@midwestbroadcasting Sorry this happened for you, we do our best to avoid such errors ever happening. However in this case, I can see it is a conflict with another plugin, which is checking some user capability after Radio Station has loaded, but *before* all plugins have finished loading. While this isn’t the best practice, it understandably happens in some plugins.

Rather than trying to work out which plugin is conflicting, I’ve just added a patch to check for the existence of the missing function (that is loaded later on.) You can use the version on Github (master branch) which includes this patch. https://github.com/netmix/radio-station/ (As this is an edge case, we’ll probably just hotfix 2.4.0.4 in the repo rather than bumping to the next version.)

@mj187 I’ve added a fix for this to the development version, please report further feedback to this issue: https://github.com/netmix/radio-station/issues/391

@sounds I will need your website URL to be able to debug this conflict, as it’s very specific data, we need to be able to reproduce the problem to fix it.

If you can provide an URL on this ticket opened here:
https://github.com/netmix/radio-station/issues/392

@skeltondm My bad, the code should be for next show (unsurprisingly):
$next = radio_station_get_next_show(); echo $next['show']['name'];

If you want to see the contents of these array information variables, I’d suggest debugging them something like:
<?php echo '<span style="display:none;">Current Show Data: ' . print_r( $current, true) . '</span>'; ?>

And then viewing the page source to see the data arary. $current['show'] should also be a (sub)array with the name key set to the Show name.

@sounds That really looks like it should just work. I can’t see anything wrong with the CSS itself. You may want to try inspecting the element in your browser and seeing which rules are overriding which for the element, but the !important should override that anyway.

One handy trick is to prefix the existing targeting with body instead of using !important. eg:
body .current-show-list .current-show-title {font-size: 14px;}

Other than that, I can only suggest inspecting in a browser. Or I can take a look at the URL myself if you provide one.

@skeltondm
I’m not sure what HTML is output, but it seems strip_tags is being used here to get text instead of HTML in the custom code.

In the second strip_tags, the second argument of <span> means that everything that is not a span tag is stripped. This could be the cause of your problem, as we have removed many span tags in favour of div tags…

In any case, if you just want the current and next show name, using shortcodes like this is not the best way. Something like this could work better:
<?php $current = radio_station_get_current_show(); echo $current[‘show’][‘name’]; ?>
<?php $next = radio_station_get_current_show(); echo $next[‘show’][‘name’]; ?>