Filevue 2.17.1 has 12 actions and 32 filters, read directly from its source code on Nov 18, 2026. The list updates automatically when a new version is released.
How to use these hooks
Actions let you run your own code at a specific moment. Filters let you change a value before the plugin uses it. Put your code in a child theme's functions.php or a code-snippets plugin, never in the plugin's own files, because updates overwrite them.
// Run your own code when Filevue fires an action
add_action( 'filevue_appearance_css_rebuild', function( $hash, $css ) {
// Your code runs here.
}, 10, 2 );
// Change a value Filevue is about to use
add_filter( 'filevue_custom_css_sanitize', function( $css ) {
// Change $css here.
return $css;
}, 10, 1 );Parts of a name in {braces} are filled in at runtime (for example a post type or field ID). Choose Example on any hook for a ready-to-edit snippet.
All hooks
-
/** * Fires after the customisation CSS has been rebuilt. */ do_action( 'filevue_appearance_css_rebuild', $hash, $css ); -
/** * Filter the final sanitised custom CSS string. */ apply_filters( 'filevue_custom_css_sanitize', $css ); -
/** * Filter the final, merged appearance tree before it is returned. */ apply_filters( 'filevue_appearance_get', $merged, 'global' ); -
/** * Fires after a preset has been applied. */ do_action( 'filevue_appearance_preset_apply', $slug, $preset, $client_id ); -
/** * Filter the final CSS string just before it is written to disk / inlined into * the page. */ apply_filters( 'filevue_appearance_built_css', $css, $global ); -
/** * Filter the capability required to manage Filevue appearance settings. */ apply_filters( 'filevue_appearance_capability', FILEVUE_Plugin::CAPABILITY_SETTINGS ); -
/** * Filter the default appearance schema. */ apply_filters( 'filevue_appearance_defaults', $defaults ); -
/** * Filter the appearance-overrides CSS block. */ apply_filters( 'filevue_appearance_overrides_css', $css ); -
/** * Filter the list of registered appearance presets. */ apply_filters( 'filevue_appearance_presets', $out ); -
/** * Fires after the appearance option is persisted. */ do_action( 'filevue_appearance_save', $payload ); -
/** * Fires when a value was successfully decrypted using a fallback key. */ do_action( 'filevue_crypto_migrated_value', $plain, $cipher, self::encrypt( $plain ) ); -
/** * Filter the CSS custom properties emitted into the portal scope. */ apply_filters( 'filevue_css_variables', $vars, $global ); -
/** * Filter whether the Custom CSS layer should auto-flag declarations with * `!important`. Defaults to true so the editor reliably overrides the bundled * stylesheet. Return false to opt out (advanced users who prefer to manage * `!important` manually). */ apply_filters( 'filevue_custom_css_force_important', true, $css ); -
/** * Filter the Custom CSS starter template shown in the empty state. */ apply_filters( 'filevue_custom_css_template', $template ); -
/** * Filter the resolved email theme for a single render. */ apply_filters( 'filevue_email_theme', $emails, $template ); -
/** * Filter whether frontend assets should be enqueued for the current request. */ apply_filters( 'filevue_enqueue_frontend_assets', $is_portal ); -
/** * Fires after files have been successfully uploaded to a client folder. */ do_action( 'filevue_file_uploaded', $client_id, $upload_folder_name, $uploaded_names, $project_id ); -
/** * Filter the PWA Web App Manifest data. */ apply_filters( 'filevue_pwa_manifest', $manifest, $appearance ); -
/** * Filter the candidate paths checked when locating a Filevue template. Plugins * can prepend their own paths to provide drop-in overrides without forking a * theme. */ apply_filters( 'filevue_template_candidates', $candidates, $relative ); -
/** * Filter the list of Google Font families to load on the portal. */ apply_filters( 'filevue_typography_google_fonts', $needed, $appearance ); -
/** * Filter the detected viewer type. */ apply_filters( 'filevue_viewer_type', self::$cache ); -
apply_filters( 'filevue_report_max_export_rows', self::DEFAULT_MAX_ROWS ); -
do_action( 'litespeed_control_set_nocache', 'filevue private client portal' ); -
apply_filters( 'filevue_appearance_export', self::build_payload( $client_id ), $client_id ); -
apply_filters( 'filevue_appearance_import', $decoded, $client_id ); -
apply_filters( 'filevue_email_body_admin_portal_upload', (string) ob_get_clean(), $client, $file_names, $project_name, $folder_name, $portal_url, $uploader_type, $uploader_name ); -
apply_filters( 'filevue_email_body_credentials', (string) ob_get_clean(), $client, $portal_url ); -
apply_filters( 'filevue_email_body_new_files', (string) ob_get_clean(), $client, $file_names, $portal_url, $folder_name ); -
apply_filters( 'filevue_email_body_project_files', (string) ob_get_clean(), $client, $file_names, $project_name, $folder_name, $portal_url ); -
apply_filters( 'filevue_email_body_smtp_test', (string) ob_get_clean() ); -
apply_filters( 'filevue_email_body_staff_credentials', (string) ob_get_clean(), $staff, $portal_url ); -
apply_filters( 'filevue_email_body_staff_project_files', (string) ob_get_clean(), $client, $file_names, $project_name, $folder_name, $portal_url ); -
do_action( 'filevue_free_preset_applied', $slug, $preset ); -
do_action( 'filevue_fs_loaded' ); -
apply_filters( 'filevue_is_pwa_portal_page', false ); -
do_action( 'filevue_pwa_send_push_notification', $client_subs, $payload ); -
apply_filters( 'filevue_pwa_vapid_public_key', $public_key ); -
apply_filters( 'filevue_test_allow_unverified_upload', false ); -
apply_filters( 'filevue_upload_debug', defined( 'WP_DEBUG' ) && WP_DEBUG ); -
apply_filters( 'https_local_ssl_verify', true ); -
do_action( 'litespeed_purge_url', $url ); -
do_action( 'litespeed_vary_no_cache', 'filevue private client portal' ); -
apply_filters( 'plugin_locale', determine_locale(), $domain ); -
do_action( 'w3tc_flush_url', $url );
Generated from Filevue's GPL-licensed source code. Hooks inside bundled third-party libraries are not listed.
Done for you
Rather have it built for you?
Tell us what should change and we’ll write and test the code using these hooks.
Custom hook snippet
from $49
A small, update-safe change built on the plugin’s own hooks.
- Code written against the plugin’s actions and filters
- Tested on a staging copy of your site
- Install instructions included
Typical turnaround: 2–3 business days
Choose thisPlugin customisation
from $149
New features or changed behaviour, without editing the plugin’s files.
- Built as a companion plugin, so updates never wipe it
- Exact quote before we start
- Tested on staging, then deployed
Typical turnaround: 3–7 business days
Choose thisNot sure which fits? Describe what you need and we’ll suggest the simplest option.
Can't find the right hook?
We can build the customisation for you. Describe what you need: