Phalcon C Extension Documentation

The Phalcon\Session namespace has been refactored. Session manipulation is now handled by a single component: Phalcon\Session\Manager. This manager uses adapters that implement PHP's SessionHandlerInterface.

Available adapters include:

• Phalcon\Session\Adapter\Files
• Phalcon\Session\Adapter\Libmemcached
• Phalcon\Session\Adapter\Noop
• Phalcon\Session\Adapter\Redis

Note: Phalcon\Di\FactoryDefault no longer loads Phalcon\Session\Adapter\Files (as session) or Phalcon\Session\Bag (as sessionBag) by default.

Phalcon version requirements have evolved:

• v5.5.0+: Minimal support shifted from PHP 7.4 to PHP 8.0. This version also added support for PHP 8.3.
• v5.6.2+: Includes fixes for PHP 8.2 deprecation warnings (e.g., Phalcon\Di\AbstractInjectionAware now extends stdClass).

Phalcon provides several Schema implementations to feed Phalcon\Forms\Form::load(), allowing you to define forms in data formats rather than pure PHP code:

• Phalcon\Forms\Loader\ArrayLoader: Loads from a PHP array.
• Phalcon\Forms\Loader\JsonLoader: Loads from a JSON string or file.
• Phalcon\Forms\Loader\YamlLoader: Loads from a YAML string or file (requires pecl/yaml).

These loaders work in conjunction with Phalcon\Forms\FormsLocator to resolve element types.

In Phalcon v5.14.2, Phalcon\Cli\Console::handle() was updated to match the module resolution behavior of Phalcon\Mvc\Application::handle().

Key Changes:

• Modules are now resolved through the inherited getModule().
• New Exception: An unregistered module now throws Phalcon\Application\Exceptions\ModuleNotRegistered (replacing Phalcon\Cli\Console\Exceptions\ConsoleModuleNotRegistered).
• New Exception: A module definition that is neither an array nor a Closure now throws Phalcon\Cli\Console\Exceptions\InvalidModuleDefinition (replacing InvalidModuleDefinitionPath).
• Support: Closure module definitions are now supported and are invoked with the container.

Starting with version 5.0.0, Phalcon\Forms\Form requires a Phalcon\Html\TagFactory to be set before it can render elements.

If you are using Phalcon\Di\FactoryDefault, the tag service will automatically return a Phalcon\Html\TagFactory instance.

In Phalcon v5.0.0, the Phalcon\Autoload\Loader class has renamed its registration methods to follow a set naming convention. Update your loader configuration as follows:

• registerClasses() $\rightarrow$ setClasses()
• registerDirectories() $\rightarrow$ setDirectories()
• registerExtensions() $\rightarrow$ setExtensions()
• registerFiles() $\rightarrow$ setFiles()
• registerNamespaces() $\rightarrow$ setNamespaces()

To emit a block of code exactly as written without parsing it through the Volt engine, use the {% verbatim %} and {% endverbatim %} tags. This is useful for passing through {{ ... }}, {% ... %}, or client-side templates like Handlebars, Mustache, or Angular untouched.

Note: The previously used {% raw %} tag was removed and should not be used.

To generate new API documentation files from the repository, use the provided PHP script. This is useful for maintaining the documentation for specific tags or versions.

Steps:

1. Clone the phalcon repository.
2. Checkout the specific tag you want to document.
3. Run the generation script.
4. The resulting *.md files contain the documentation.

Note: For publishing to the official Phalcon website, the documentation is managed in a separate repository.

php bin/generate-api-docs.php

In version 4.0.0-alpha.3, the URL component was moved out of the MVC namespace. Update your imports and usage:

• Phalcon\Mvc\Url $\rightarrow$ Phalcon\Url
• Phalcon\Mvc\UrlInterface $\rightarrow$ Phalcon\UrlInterface
• Phalcon\Mvc\Url\Exception $\rightarrow$ Phalcon\Url\Exception