Preparing the latest guides, releases, and feature request updates.
Loading guides
Preparing the right Knowledge Base content for this platform.
WordPress hooks and filters reference | Chamevo Support Center
WordPress hooks and filters reference
Complete reference of WordPress action hooks and filters provided by the Chamevo plugin for customizing behavior.
Updated April 29, 20265 min read
Chamevo provides WordPress action hooks and filters that let developers customize the plugin's behavior — modify the customizer configuration, intercept order data, control which products show the customizer, and adjust email notifications.
Frontend hooks
chamevo_designer_enabled
Type: Filter
File:src/functions.php
Controls whether the product customizer is enabled for a specific post/product.
apply_filters('chamevo_designer_enabled', bool $enabled, int $post_id): bool
Parameter
Type
Description
$enabled
bool
Whether the customizer is currently enabled for this post
$post_id
int
The WordPress post/product ID
Example: Disable the customizer for a specific product:
Modify or intercept customization data when a new order is placed. This is the central hook for all order types (WooCommerce, Shortcode, Gravity Forms).
These dynamic filters route Chamevo's AI Tools — text-to-image generation, upscaling, and background removal — to your own AI provider instead of the hosted Chamevo service. {tool} is one of the canonical tool keys: text2image, upscale, or remove_background.
Resolve the provider configuration for a tool. Return a config whose endpoint is non-empty to put the tool in custom mode — Chamevo then calls your endpoint directly, bypassing the hosted service-router, the license header (X_API_TOKEN), and credit metering. This is the runtime alternative to the CHAMEVO_AI_{TOOL}_ENDPOINT / _KEY / _MODEL constants.
Short-circuit the direct provider HTTP call. Return a service-router-shaped array to fully bypass the built-in request — useful for async providers (create + poll) or provider SDKs. Returns null by default.
Set the headers sent to the custom provider. Defaults to Authorization: Bearer {api_key} when a key is set. The Chamevo license header is never sent in custom mode.
Normalize the provider response into the service-router shape so the AJAX handler can consume it: ['status' => 'success', 'data' => ['output' => $url]]. output may be a remote URL, an array of URLs, or a data:image/…;base64,… URI.
