↑ Back to top

  • filter

    jetpack_email_editor_save_design

    Filters the result of saving the newsletter email design. The editor sends the whole styles document rather than a patch, so implementations replace rather than merge. Implementations should report on a read-back of the stored design rather than echoing the submitted one: sanitizing drops properties outside the theme.json schema, so a save can succeed into invisibility, and the screen has to be able to tell a person their edit did not survive. Internal, and not settled, for the same reason as the read above: expect the shape of the design document and of what is returned to change while the editor is being built.

  • filter

    jetpack_email_editor_bootstrap

    Filters the data the newsletter email editor needs to start. Returns the editor’s settings, its theme, the resolved canvas template, the available personalization tags and the blog’s saved design. Unfiltered on a site with nothing implementing it, which the endpoint reports as unavailable rather than as an empty design. Internal, and not settled: the editor this serves is still being built, so the shape of what comes back is expected to change. Do not depend on it from outside the plugin.

  • filter

    jetpack_podcast_feed_limit_max

    Filters the ceiling for the podcast feed’s episode limit. Raising it renders that many items in one request, so only where the host can absorb it.

  • action

    jetpack_site_data_fetched

    Fires after the site record was served, whether it was fetched or read from the cache. Consumers that cache anything derived from the record, such as the current plan, can refresh it here. This fires on a cached read too, so a consumer stays in step with every request that serves the record rather than only the ones that reached WordPress.com. The record is passed as an array rather than the object this method returns, so that a listener cannot mutate the instance that becomes the REST response.

  • action

    jetpack_connection_tokens_deleted

    Fires after all connection tokens have been deleted from the local site. `Jetpack_Options::delete_option()` fires no action of its own, so this is the only signal that the tokens backing the connection are gone. Anything holding derived state — a memoized connection status, a cached credential — must recompute from here.

  • filter

    DASHBOARD_PREVIEW_SCOPE_FILTER

    Filters whether the preview exposes a dashboard section. `__return_true` restores the whole dashboard, which is how a development or test site sees every tab.