Starting with WordPress 4.9, embeds that aren’t associated with a specific post will be cached in a new oembed_cache post type. There can be more than one such entry for a url depending on attributes and context.
Not to be confused with oEmbed caches for a given post which are stored in the post’s metadata.
- URL to retrieve oEmbed data for.
- Width of the embed in pixels. Part of cache key so must match. Defaults to
content_widthif set else 500px, so is theme and context dependent.
- Height of the embed in pixels. Part of cache key so must match. Defaults to 1.5 * default width (
content_widthor 500px), to a maximum of 1000px.
- Whether to search with the discover attribute set or not. Part of cache key so must match. If not given, will search with attribute: unset, ‘1’, ‘0’, returning first.
# Find cache post ID for a given URL. $ wp embed cache find https://www.youtube.com/watch?v=dQw4w9WgXcQ --width=500 123
GLOBAL PARAMETERS GLOBAL PARAMETERS
These global parameters have the same behavior across all commands and affect how WP-CLI interacts with WordPress.
||Path to the WordPress files.|
||Pretend request came from given URL. In multisite, this argument is how the target site is specified.|
||Perform operation against a remote server over SSH (or a container using scheme of “docker”, “docker-compose”, “vagrant”).|
||Perform operation against a remote WordPress installation over HTTP.|
||Set the WordPress user.|
||Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded.|
||Skip loading all themes, or a comma-separated list of themes.|
||Skip loading all installed packages.|
||Load PHP file before running the command (may be used more than once).|
||Whether to colorize the output.|
||Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help.|
||Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values.|
||Suppress informational messages.|