Make WordPress Core

Opened 3 years ago

Last modified 3 months ago

#36293 reopened defect (bug)

video/audio object passed to wp_video_shortcode/wp_audio_shortcode is always null

Reported by: gnotaras Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: General Keywords: bulk-reopened
Focuses: Cc:



The following:

apply_filters( 'wp_video_shortcode', $output, $atts, $video, $post_id, $library );

apply_filters( 'wp_audio_shortcode', $html, $atts, $audio, $post_id, $library );

send the $video and $audio objects respectively to the filtering function.

However, these objects seem to be always null.

By checking the relevant code I notice that these objects are only set when the $primary variable is set to false. The code does not clarify why the audio/video object is bound to that variable. Perhaps someone more familiar with the logic behind these functions should check this please.

Change History (2)

#1 @iseulde
5 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to wontfix
  • Status changed from new to closed

This ticket has not seen any activity in over *two* years, so I'm closing it as "wontfix".

The ticket may lack decisiveness, may have become irrelevant, or may not have gathered enough interest.

If you think this ticket does deserve some attention again, feel free to reopen.

For bugs, it would be great if you could provide updated steps to reproduce against the latest version of WordPress (5.0.2 at the time of writing). Remember images or a video can be superior to explain a problem. At the very least, quickly test again to make sure the bug still exists.

If it’s an enhancement or feature, some extra motivation may help.

Thank you for your contributions to WordPress! <3

#2 @JeffPaul
3 months ago

  • Keywords bulk-reopened added
  • Milestone set to Awaiting Review
  • Resolution wontfix deleted
  • Status changed from closed to reopened

A decision was made to reopen tickets that were closed in the bulk edit that this ticket was affected by. This ticket is being placed back into the Awaiting Review milestone so it can be individually evaluated and verified to determine if it is still relevant/valid or reproducible.

Note: See TracTickets for help on using tickets.