Overview

The actions system allows executing PHP code before displaying HTML content. Actions are automatically matched to content pages based on the URL.

How It Works

• When a page is requested (e.g., /contact)
• The system looks for actions/contact.php
• If found, it loads the Contact class
• Executes the method matching the HTTP method (e.g., get() for GET requests or post() for POST requests)
• Then displays the views/contact.html page contents

Namespaces in actions

There is no need to use namespaces in actions as each action is included and called in isolation.

This means if there is a file in the following directories:

|- /var/www/project-root/actions/index.php
|- /var/www/project-root/actions/blog/index.php
    

Both files would define a class called Index without namespace and it should work without a problem:

<?php
class Index {
    public function get() {
        return "Hello from index action";
    }
}

File Naming Convention

• Action file: actions/contact.php
• Class name: Contact (capitalized, matches filename)

For multi-word files:

• File: contact-form.php → Class: ContactForm
• File: product_list.php → Class: ProductList

Creating an Action Class

Create a PHP file in the actions/ directory matching the content file name:

<?php
// actions/contact-form.php
class ContactForm {
    public function get() {
        // Runs on GET requests to /contact
        // Prepare data, check auth, etc.
        
        // Access to .env parameters
        $var = $_ENV['SOME_PARAMETER'];

        return ['title' => 'Hello!']; // This will be available as  in the template
    }
    
    public function post() {
        // Runs on POST requests to /contact
        // Process forms, save data, etc.
        $this->validateCsrf();
        
        $name = getPost('name');
        // ... process data
        
        redirect('/success');
    }
}

Tips:

• A common parent class (e.g. App) can be created which actions can extend to share functionality.
• Additional logic can be used or created behind the actions to connect to databases, APIs, or other services.

Supported HTTP Methods

The action system automatically supports all HTTP methods:

• get() - Handle GET requests
• post() - Handle POST requests
• put() - Handle PUT requests
• delete() - Handle DELETE requests
• patch() - Handle PATCH requests

all() method handles any HTTP methods that do not have a specific handler defined.

Helper Methods

redirect('/success');              // Redirect to another page

return json(['status' => 'ok']);          // Return JSON response instead of html content
return json(['status' => 'failed'], 503); // Return JSON response instead of html content with status code 501

$name = getPost('name', 'default');     // Get POST data sanitized

$query = getQuery('q', '');             // Get GET data sanitized

setFlash('success', 'Message sent!');   // Set flash message
$msg = getFlash('success');             // Get and clear flash

verifyCsrf();