Customizing Controller Actions

Terrazzo generates a base ApplicationController for your admin namespace. All resource controllers inherit from it.

For authentication and authorization, see the dedicated Authentication and Authorization pages.

Customizing Actions

Each dashboard generator creates a resource-specific controller:

# app/controllers/admin/products_controller.rb
class Admin::ProductsController < Admin::ApplicationController
end

You can override any CRUD action here:

class Admin::ProductsController < Admin::ApplicationController
  def create
    # custom create logic
    super
  end

  private

  def scoped_resource
    Product.where(active: true)
  end
end

Customizing find_resource

Override find_resource when your model uses a non-id primary key or slug-based routing:

class Admin::ProductsController < Admin::ApplicationController
  private

  def find_resource(id)
    scoped_resource.find_by!(slug: id)
  end
end

How It Works

Terrazzo::ApplicationController provides standard CRUD actions:

• index — paginated, searchable, sortable list
• show — single record detail
• new / create — new record form and creation
• edit / update — edit form and update
• destroy — record deletion

Create and update use redirect_to on success (Superglue handles redirects as SPA navigations). On validation failure, the form is re-rendered with status: :unprocessable_entity.

Superglue Template Lookup

Terrazzo uses Superglue to render React pages server-side. When a controller has a long view prefix chain (e.g. from Devise or other engine-mounted controllers), Superglue's template existence check can accidentally match a gem-supplied HTML template and render it instead of the React page.

Terrazzo automatically scopes the template lookup to your app's app/views directory only, so gem templates are never used as a fallback.