• filter

    jetpack_forms_file_field_max_files_limit

    Filters the highest number of files an author may set a file upload field to. This raises the ceiling rather than setting the count. A field still takes whatever its author chose, so one deliberately set to a single file keeps taking a single file — which is the whole difference between offering more room and overriding everybody’s choice. The editor’s control reads the same number, so what an author is offered is what the site will honour. A field already storing a number above the ceiling is clamped down to it, so removing this filter returns those fields to the default rather than leaving them on a value nothing enforces any more. Bounded by FILE_FIELD_MAX_FILES_ABSOLUTE_LIMIT. Nothing at the receiving end refuses a submission for holding too many files — the endpoint’s per-site budgets log and alert but store the file regardless — so this ceiling is the only thing standing in the way.

  • filter

    jetpack_feature_flag_enabled_{$name}

    Filters whether a specific Jetpack feature flag is enabled. The dynamic portion of the hook name, `$name`, refers to the feature flag name. This mirrors the WordPress `option_{$option}` convention so a single flag can be toggled with a `__return_true`/`__return_false` one-liner.

  • filter

    jetpack_stats_post_list_column_url

    Filters where the post list table’s views column links to. Lets a newer analytics dashboard claim the entry point without this package knowing about it.

  • filter

    self::CHAPTERS_EDITOR_FILTER

    Whether the VideoPress chapters editor UI is available. Gates UI only — the chapters REST surface stays registered either way.