Hooks

Hooks are the event system for plugins. Register a hook in the manifest, implement the function in your entry file, and RaisFast calls it at the right time.

Hook Types

All Hooks

Content Lifecycle

Post Lifecycle

Comment Lifecycle

Product & Order

Payment & Wallet

Tag & Category & Page & Media

User & Auth

Utility

Custom Events

Plugins can emit custom events via emitEvent(). Other plugins can listen by registering a hook matching the event type:

[hooks.order-created]
priority = 10

export function order_created(input) {
  const data = JSON.parse(input);
  logInfo("order created: " + data.id);
}

Priority Ordering

Hooks execute in ascending priority order (lower number = runs first):

[hooks.on-content-creating]
priority = 10   # runs first

[hooks.on-content-creating]
priority = 50   # runs second

[hooks.on-content-creating]
priority = 100  # runs last (default)

Default priority is 100 if not specified.

For filter hooks, each plugin receives the output of the previous plugin in the chain. For action hooks, all plugins run independently.

Content Type Filtering

Limit a hook to specific content types:

[hooks.on-content-creating]
priority = 10
content_types = ["product", "course"]

Or use the shorthand match:

[hooks.on-content-creating]
priority = 10
match = "product"

When content_types is empty (default), the hook fires for all content types.

Filter Hooks

Filter hooks can modify data before it is saved. Return the modified data:

export function on_content_creating(input) {
  const data = JSON.parse(input);
  if (!data.slug) {
    data.slug = data.title.toLowerCase().replace(/ /g, '-');
  }
  return JSON.stringify(data);
}

Plugin.on_content_creating = function(input)
  local data = sdk.extractJson(input, "body")
  if not data.slug then
    data.slug = string.lower(data.title):gsub(" ", "-")
  end
  return sdk.ok(data)
end

fn on_content_creating(input) {
  if input.slug == "" {
    input.slug = to_lower(input.title);
    input.slug = replace(input.slug, " ", "-");
  }
  input
}

Action Hooks

Action hooks are for side effects — logging, notifications, cache invalidation. Return value is ignored:

export function on_content_created(input) {
  const data = JSON.parse(input);
  logInfo("created: " + data.id);
  eventEmit("content.created", JSON.stringify({ id: data.id }));
}

Plugin.on_content_created = function(input)
  local data = sdk.extractJson(input, "body")
  sdk.logInfo("created: " .. tostring(data.id))
  sdk.eventEmit("content.created", sdk.jsonEncode({ id = data.id }))
end

fn on_content_created(input) {
  log("info", "created: " + input.id);
  emit_event("content.created", to_json(input));
}

Render Override Hooks

Render overrides use a first-wins strategy. The first plugin to return a non-null value wins, and the remaining plugins are skipped:

[hooks.render-markdown]
priority = 10

export function render_markdown(input) {
  const data = JSON.parse(input);
  return customMarkdownRenderer(data.content);
}

Error Recovery

• After 5 consecutive errors, the plugin is auto-disabled
• Error count resets to 0 on a successful invocation
• You can re-enable via Admin API: POST /api/v1/admin/plugins/{id}/enable
• Uncommitted transactions are automatically rolled back on timeout or crash