Upgrading from 4.3.4 to 4.3.5

Please refer to the upgrade instructions corresponding to your installation method.

Breaking Changes

Validation Placeholders

To use Validation Placeholders securely, please remember to create a validation rule for the field you will use as a placeholder.

E.g., if you have the following code:

    'email' => 'required|max_length[254]|valid_email|is_unique[users.email,id,{id}]',

You need to add the rules for {id}:

    'id'    => 'max_length[19]|is_natural_no_zero', // Add this
    'email' => 'required|max_length[254]|valid_email|is_unique[users.email,id,{id}]',


Prior to v4.3.5, the Session::stop() method did not destroy the session due to a bug. This method has been modified to destroy the session, and now deprecated because it is exactly the same as the Session::destroy() method. So use the Session::destroy method instead.

If you have code to depend on the bug, replace it with session_regenerate_id(true).

See also Session Library.

Project Files

Some files in the project space (root, app, public, writable) received updates. Due to these files being outside of the system scope they will not be changed without your intervention.

There are some third-party CodeIgniter modules available to assist with merging changes to the project space: Explore on Packagist.

Content Changes

The following files received significant changes (including deprecations or visual adjustments) and it is recommended that you merge the updated versions with your application:


  • app/Config/Generators.php

All Changes

This is a list of all files in the project space that received changes; many will be simple comments or formatting that have no effect on the runtime:

  • app/Config/App.php

  • app/Config/Generators.php

  • composer.json