RiffSource

apply_filters( 'riff_import_private', bool $private, int $id, int $author )

Filters whether a zip uploaded to the Media Library imports privately: each track and video Protected, each album's post private, for its uploader to publish. A host whose privacy is site-wide, such as a private site, can return false so that what the site already keeps from visitors is not hidden a second time, album by album: return ! Private_Site::on(). It answers for the import in the background, which an upload to the Media Library and POST /riff/v1/imports both start; wp riff import takes --private and --no-private. Defaults to true.

Parameters

$privatebool
Whether the import is private.
$idint
The zip's attachment ID.
$authorint
The ID of the user who uploaded it, whom the import runs as.

More Information

Usage

add_filter( 'riff_import_private', function ( $private, $id, $author ) {
	return $private;
}, 10, 3 );

Source

$private  = (bool) apply_filters( 'riff_import_private', true, $id, $author );

plugins/riff/src/class-import.phpView on GitHub

Used byDescription
Import::uploaded_zip()plugins/riff/src/class-import.phpImports a zip uploaded to the Media Library, as the person who uploaded it, privately: each track Protected and each album's post private, for them to publish if the music is theirs to share. The zip stays in the Media Library, attached to its album's post, so the Media Library shows where it went, and it may hold more than the import reads, a booklet say; one that holds no audio stays as it was. Core serves the zip itself at a public address, which the docs tell its uploader, for them to delete it once they no longer need it. Its albums are its own, found by the zip's attachment, so a zip uploaded again, as a new file, skips the tracks already imported and puts any new ones in a post of their own, and never adds to a post its uploader did not make.

Changelog

VersionDescription
6.8.0Introduced.