<![CDATA[CodeIgniter Forums

<![CDATA[CodeIgniter Forums - All Forums]]> https://forum.codeigniter.com/ Wed, 15 Apr 2026 02:07:53 +0000 MyBB <![CDATA[*.env file in different location]]> https://forum.codeigniter.com/showthread.php?tid=94011 Tue, 14 Apr 2026 16:39:24 +0000 petewulf1]]> https://forum.codeigniter.com/showthread.php?tid=94011 It seems there is no official way to place the *.env file at a different location than the projects root folder. Why?
What would be an appropriate way to load from a different location without having to overwrite Boot.php?
Thanks!
Daniel]]> It seems there is no official way to place the *.env file at a different location than the projects root folder. Why?
What would be an appropriate way to load from a different location without having to overwrite Boot.php?
Thanks!
Daniel]]> <![CDATA[feat(DI): Some dependency injection in CI]]> https://forum.codeigniter.com/showthread.php?tid=94010 Tue, 14 Apr 2026 11:45:26 +0000 patel-vansh]]> https://forum.codeigniter.com/showthread.php?tid=94010 After working with CodeIgniter 4, I wanted to share some thoughts on Dependency Injection and CodeIgniter 4:
This is not a proposal to replace CI4’s simplicity or turn it into another framework. The goal would be to modernize dependency management in a way that still respects CI4’s philosophy: simple, predictable, explicit, and lightweight.

Why Discuss This?
The current Services pattern works well and is easy to understand, but it also has some limitations for larger or more modular applications:
- Uses a service locator pattern rather than constructor injection
- Manual dependency wiring increases as projects grow
For many apps this is not a problem. But for larger projects, cleaner dependency management can be valuable.

Suggested Direction
Introduce a small optional container that can coexist with the current system.
Example:
In the bootstrap process, you can inject any class:

PHP Code:
container()->bind( UserRepositoryInterface::class, DatabaseUserRepository::class ); 

And just use it via constructor injection:

PHP Code:
class UserService {
    public function __construct( private readonly UserRepositoryInterface $repo ) {}

    public function getUser(int $userId) {
        return $this->repo->getUser($userId);
    }
} 

Then, in controller:

PHP Code:
$service = container()->get(UserService::class); 

This would automatically resolve dependencies recursively.

Example Binding Types
Class to class:

PHP Code:
container()->bind( 
    CacheInterface::class,
    FileCache::class
); 

Factory closure:

PHP Code:
container()->bind(UserService::class, function ($c) {
    return new UserService(
        $c->get(UserRepository::class),
        'foo'
    );
}); 

Useful when primitives/config values are needed.

Why This Could Benefit CI4
Better testability
Cleaner architecture for medium/large apps
Better package/module ecosystem
Modern PHP patterns while preserving CI4 simplicity
Gradual adoption with zero breakage

After some time, maybe, we can make the current service calls go through this container system, like this:

PHP Code:
function cache(bool $getShared = true) {
    if ($getShared) {
        return container()->singleton(CacheInterface::class);
    }

    return container->get(CacheInterface::class);
} 

]]> After working with CodeIgniter 4, I wanted to share some thoughts on Dependency Injection and CodeIgniter 4:
This is not a proposal to replace CI4’s simplicity or turn it into another framework. The goal would be to modernize dependency management in a way that still respects CI4’s philosophy: simple, predictable, explicit, and lightweight.

Why Discuss This?
The current Services pattern works well and is easy to understand, but it also has some limitations for larger or more modular applications:
- Uses a service locator pattern rather than constructor injection
- Manual dependency wiring increases as projects grow
For many apps this is not a problem. But for larger projects, cleaner dependency management can be valuable.

Suggested Direction
Introduce a small optional container that can coexist with the current system.
Example:
In the bootstrap process, you can inject any class:

PHP Code:
container()->bind( UserRepositoryInterface::class, DatabaseUserRepository::class ); 

And just use it via constructor injection:

PHP Code:
class UserService {
    public function __construct( private readonly UserRepositoryInterface $repo ) {}

    public function getUser(int $userId) {
        return $this->repo->getUser($userId);
    }
} 

Then, in controller:

PHP Code:
$service = container()->get(UserService::class); 

This would automatically resolve dependencies recursively.

Example Binding Types
Class to class:

PHP Code:
container()->bind( 
    CacheInterface::class,
    FileCache::class
); 

Factory closure:

PHP Code:
container()->bind(UserService::class, function ($c) {
    return new UserService(
        $c->get(UserRepository::class),
        'foo'
    );
}); 

PHP Code:
function cache(bool $getShared = true) {
    if ($getShared) {
        return container()->singleton(CacheInterface::class);
    }

    return container->get(CacheInterface::class);
} 

]]> <![CDATA[Boosting CI4 popularity]]> https://forum.codeigniter.com/showthread.php?tid=94009 Mon, 13 Apr 2026 15:50:33 +0000 enlivenapp]]> https://forum.codeigniter.com/showthread.php?tid=94009
While I've been working on my CMS, I've found, what I feel, would be one of the best ways to implement such functionality similar to what Laraval offers. Their Service Providers solution to adding whatever package you want to use would be a massive advantage to Codeigniter.

The one argument I often hear/read is 'composer whatever' has this, just 'composer require' it and use it (usually coming across as kinda negative nancy since text has no real context). I get that and it's 100% true, but that advice doesn't really cut it when CI is better than many frameworks in many ways but kinda can't get out of it's own way.

As always, lively discussion is wanted, I'd really like to hear from the Foundation devs too. Is there any interest from the Foundation to create a Service Provider/Packages and much expanded spark CLI kind of ecosystem for Codeigniter?

Happy coding.]]>
While I've been working on my CMS, I've found, what I feel, would be one of the best ways to implement such functionality similar to what Laraval offers. Their Service Providers solution to adding whatever package you want to use would be a massive advantage to Codeigniter.

The one argument I often hear/read is 'composer whatever' has this, just 'composer require' it and use it (usually coming across as kinda negative nancy since text has no real context). I get that and it's 100% true, but that advice doesn't really cut it when CI is better than many frameworks in many ways but kinda can't get out of it's own way.

As always, lively discussion is wanted, I'd really like to hear from the Foundation devs too. Is there any interest from the Foundation to create a Service Provider/Packages and much expanded spark CLI kind of ecosystem for Codeigniter?

Happy coding.]]> <![CDATA[Ragnos: A "Configuration over Code" Enterprise Add-on built on CI4]]> https://forum.codeigniter.com/showthread.php?tid=93997 Fri, 10 Apr 2026 00:19:02 +0000 cgarciagl]]> https://forum.codeigniter.com/showthread.php?tid=93997 I have been using and loving CodeIgniter for years. I work as a developer and academic technician at a University Research Center, where we constantly build administrative and educational systems. While CI4 is blazing fast and elegantly structured, I found myself getting burned out writing the exact same CRUD controllers, HTML views, data tables, and permission logic for every new project.

To keep my sanity, I built a higher-level enterprise add-on entirely on top of CodeIgniter 4 called Ragnos. I just released it as 100% open-source and wanted to share it with the community that makes CI4 possible.

The core philosophy of Ragnos is "Configuration over Programming." Instead of writing standard MVC boilerplate for admin panels, you use our RDatasetController. You simply define a "Data Dictionary" (a plain PHP array) in your controller, and this add-on automatically renders a fully styled dashboard, handles pagination, advanced search filters, data exports, and forms.

Because it runs native CI4 under the hood, it automatically benefits from its Query Builder, CSRF protection, and XSS filtering, but it adds a dynamic Role-Based Access Control (RBAC) layer on top. Also, since modules are generated from PHP arrays, it is incredibly easy to use AI to write your configurations and generate entire modules in seconds.

You can check out the documentation, the philosophy, and the GitHub repository here: https://ragnos.build

Because the project grew quite a bit, I also wrote a complete 162-page official manual called "Ragnos from Zero to Pro" (available in English and Spanish on Leanpub) for those who want to master the architecture or implement it at an enterprise level. But the core add-on is completely free and open for the community.

I would love for the CI experts here to take a look at the code, install it, break it, and give me your honest feedback. I owe a lot to CodeIgniter, and I hope this contribution helps other developers save as much time as it has saved me.
Thanks for reading and happy coding!]]> I have been using and loving CodeIgniter for years. I work as a developer and academic technician at a University Research Center, where we constantly build administrative and educational systems. While CI4 is blazing fast and elegantly structured, I found myself getting burned out writing the exact same CRUD controllers, HTML views, data tables, and permission logic for every new project.

To keep my sanity, I built a higher-level enterprise add-on entirely on top of CodeIgniter 4 called Ragnos. I just released it as 100% open-source and wanted to share it with the community that makes CI4 possible.

The core philosophy of Ragnos is "Configuration over Programming." Instead of writing standard MVC boilerplate for admin panels, you use our RDatasetController. You simply define a "Data Dictionary" (a plain PHP array) in your controller, and this add-on automatically renders a fully styled dashboard, handles pagination, advanced search filters, data exports, and forms.

Because it runs native CI4 under the hood, it automatically benefits from its Query Builder, CSRF protection, and XSS filtering, but it adds a dynamic Role-Based Access Control (RBAC) layer on top. Also, since modules are generated from PHP arrays, it is incredibly easy to use AI to write your configurations and generate entire modules in seconds.

You can check out the documentation, the philosophy, and the GitHub repository here: https://ragnos.build

Because the project grew quite a bit, I also wrote a complete 162-page official manual called "Ragnos from Zero to Pro" (available in English and Spanish on Leanpub) for those who want to master the architecture or implement it at an enterprise level. But the core add-on is completely free and open for the community.

I would love for the CI experts here to take a look at the code, install it, break it, and give me your honest feedback. I owe a lot to CodeIgniter, and I hope this contribution helps other developers save as much time as it has saved me.
Thanks for reading and happy coding!]]> <![CDATA[Claude Code Skills]]> https://forum.codeigniter.com/showthread.php?tid=93992 Wed, 08 Apr 2026 07:01:50 +0000 enlivenapp]]> https://forum.codeigniter.com/showthread.php?tid=93992
fork it, PR it, whatever you need.
https://github.com/enlivenapp/Codeignite...laude-Code

Happy Coding!]]>
fork it, PR it, whatever you need.
https://github.com/enlivenapp/Codeignite...laude-Code

Happy Coding!]]> <![CDATA[Testing same tables]]> https://forum.codeigniter.com/showthread.php?tid=93984 Sat, 04 Apr 2026 10:14:37 +0000 ozornick]]> https://forum.codeigniter.com/showthread.php?tid=93984 Main, Blog, Shop...
Each contains tests modules/src/Shop/Tests/* and data Shop/Database/{Migrations|Seeders} for them.
Errors occurred with identical tables (posts, users..) in the same test database. I am using the SQLite3 file.

How best to split the execution (random tests) without creating many connections: tests, tests_for_main, test_for_shop..? Because sometimes you may need data from modules that do not overlap.

In general, working with migrations is very strict - you can't just execute import and seeder files. And auto-searching of this data may be unsuitable: for example, when the imported data is located outside of ./Database/* or has a non-standard FQCN.

My test begin as:

PHP Code:
final class PostModelTest extends CIUnitTestCase
{
    use DatabaseTestTrait;

    protected $namespace = [
        'Neznaika0\Module\Blog',
        'Neznaika0\Module\Shop',
    ];
    protected $seed = [
        UserSeeder::class,
        PostSeeder::class,
    ];
    protected $migrateOnce = false;
    protected $seedOnce    = false; 

]]> Main, Blog, Shop...
Each contains tests modules/src/Shop/Tests/* and data Shop/Database/{Migrations|Seeders} for them.
Errors occurred with identical tables (posts, users..) in the same test database. I am using the SQLite3 file.

How best to split the execution (random tests) without creating many connections: tests, tests_for_main, test_for_shop..? Because sometimes you may need data from modules that do not overlap.

In general, working with migrations is very strict - you can't just execute import and seeder files. And auto-searching of this data may be unsuitable: for example, when the imported data is located outside of ./Database/* or has a non-standard FQCN.

My test begin as:

PHP Code:
final class PostModelTest extends CIUnitTestCase
{
    use DatabaseTestTrait;

    protected $namespace = [
        'Neznaika0\Module\Blog',
        'Neznaika0\Module\Shop',
    ];
    protected $seed = [
        UserSeeder::class,
        PostSeeder::class,
    ];
    protected $migrateOnce = false;
    protected $seedOnce    = false; 

]]> <![CDATA[Best way to implement a Service Layer in CI4 for complex business logic?]]> https://forum.codeigniter.com/showthread.php?tid=93983 Fri, 03 Apr 2026 19:42:58 +0000 marinkitagawa]]> https://forum.codeigniter.com/showthread.php?tid=93983

Code:
Config/Validation.php

, but I’m struggling with where to put complex business logic that doesn't belong in the Model or the Controller.
My questions are:

Is creating a separate

Code:
app/Services
directory the standard approach in CI4 for handling business logic?
How should I properly initialize these services? Should I use the

Code:
Services
configuration file or just instantiate them normally in the controller?
Are there any performance overheads or architectural 'gotchas' I should be aware of when moving logic out of the controller?

I'd love to hear how you guys structure your enterprise-level applications. Thanks!]]>

Code:
Config/Validation.php

, but I’m struggling with where to put complex business logic that doesn't belong in the Model or the Controller.
My questions are:

Is creating a separate

Code:
app/Services
directory the standard approach in CI4 for handling business logic?
How should I properly initialize these services? Should I use the

Code:
Services
configuration file or just instantiate them normally in the controller?
Are there any performance overheads or architectural 'gotchas' I should be aware of when moving logic out of the controller?

I'd love to hear how you guys structure your enterprise-level applications. Thanks!]]> <![CDATA[What do i need to do back to older version of a file]]> https://forum.codeigniter.com/showthread.php?tid=93982 Fri, 03 Apr 2026 13:01:42 +0000 mikehoague]]> https://forum.codeigniter.com/showthread.php?tid=93982 <![CDATA[Proper way to handle Form Validation in CodeIgniter 4?]]> https://forum.codeigniter.com/showthread.php?tid=93980 Thu, 02 Apr 2026 13:20:27 +0000 marinkitagawa]]> https://forum.codeigniter.com/showthread.php?tid=93980

Code:
$this->validate()

method and using a separate Validation service. Which one is considered best practice for large projects to keep the controllers clean? Also, how do I display custom error messages in the view?]]>

Code:
$this->validate()

method and using a separate Validation service. Which one is considered best practice for large projects to keep the controllers clean? Also, how do I display custom error messages in the view?]]> <![CDATA[can not find the setting PHP under Languages & Frameworks]]> https://forum.codeigniter.com/showthread.php?tid=93975 Wed, 01 Apr 2026 19:39:18 +0000 mikehoague]]> https://forum.codeigniter.com/showthread.php?tid=93975

Open Settings: Navigate to File | Settings.
Locate PHP Settings: Go to Languages & Frameworks | PHP. (not seing this PHP topic)
Set CLI Interpreter: Look for the CLI Interpreter field. If it says "None" or is highlighted in red, click the three dots (...) button next to it.
Add New Interpreter: Click the + (Plus) icon and select Local Path to Interpreter.
Specify the Path: Browse to your PHP executable. Common locations include:
- Windows (XAMPP):
  
  Code:
  C:\xampp\php\php.exe
Verify: Once selected, PhpStorm should automatically detect the PHP version and configuration file (php.ini). Click OK to apply.

]]>

Open Settings: Navigate to File | Settings.
Locate PHP Settings: Go to Languages & Frameworks | PHP. (not seing this PHP topic)
Set CLI Interpreter: Look for the CLI Interpreter field. If it says "None" or is highlighted in red, click the three dots (...) button next to it.
Add New Interpreter: Click the + (Plus) icon and select Local Path to Interpreter.
Specify the Path: Browse to your PHP executable. Common locations include:
- Windows (XAMPP):
  
  Code:
  C:\xampp\php\php.exe
Verify: Once selected, PhpStorm should automatically detect the PHP version and configuration file (php.ini). Click OK to apply.

]]> <![CDATA[Help: CodeIgniter 4 Installation showing 404 on Home Page]]> https://forum.codeigniter.com/showthread.php?tid=93973 Wed, 01 Apr 2026 15:10:01 +0000 marinkitagawa]]> https://forum.codeigniter.com/showthread.php?tid=93973

Code:
.htaccess

file and made sure

Code:
mod_rewrite

is enabled on my Apache server. Is there a specific configuration in the

Code:
App.php

file under the

Code:
baseURL

that I might be missing?]]>

Code:
.htaccess

file and made sure

Code:
mod_rewrite

is enabled on my Apache server. Is there a specific configuration in the

Code:
App.php

file under the

Code:
baseURL

that I might be missing?]]> <![CDATA[Problem entity return null (id) on save()]]> https://forum.codeigniter.com/showthread.php?tid=93968 Tue, 31 Mar 2026 08:08:35 +0000 AnotherOnit]]> https://forum.codeigniter.com/showthread.php?tid=93968 I'm creating a new user using an Entity and calling

Code:
save()

on my model:

Code:
$user_model = new UserModel;

$user = new User();

$user->fill([

    'username' => post('username'),

    'email'    => post('email'),

    'password' => post('password'),

    'auth_token' => generate_token(),

    'auth_token_expire_at' => date_add_duration("now", "+1 day")

]);

$user_model->save($user);

var_dump($user->id);

die();

The insert works fine in the database, but

Code:
$user->id

is still

Code:
null

after calling

Code:
save()

Code:
save()

on my model:

Code:
$user_model = new UserModel;

$user = new User();

$user->fill([

    'username' => post('username'),

    'email'    => post('email'),

    'password' => post('password'),

    'auth_token' => generate_token(),

    'auth_token_expire_at' => date_add_duration("now", "+1 day")

]);

$user_model->save($user);

var_dump($user->id);

die();

The insert works fine in the database, but

Code:
$user->id

is still

Code:
null

after calling

Code:
save()

.
Is this normal behavior in CodeIgniter 4?
I was expecting the entity to be updated with the inserted ID automatically.

Thanks in advance!

Sorry for my bad english .. I'm French]]> <![CDATA[Tasks v1.0.0 Released]]> https://forum.codeigniter.com/showthread.php?tid=93963 Sun, 29 Mar 2026 17:36:15 +0000 michalsn]]> https://forum.codeigniter.com/showthread.php?tid=93963 CodeIgniter Tasks v1.0.0 Released

We are happy to announce the first stable release of CodeIgniter Tasks for CodeIgniter 4.

CodeIgniter Tasks brings native task scheduling to CodeIgniter applications, making it easy to define scheduled work in code and run it from a single cron entry.

Highlights

Fluent task scheduling - define scheduled work with an expressive API designed for CodeIgniter 4.
Multiple task types - supports framework ccommands, shell, events, URLs, and queue jobs.
Timezone-aware scheduling - run tasks using the correct timezone for your application.
Rich frequency helpers - includes hourly, monthly, specific times of day, and custom cron expressions.
Next-run calculation - makes it easier to inspect and understand upcoming schedules.
CLI tooling - publish config, list tasks, run the scheduler, and enable or disable task execution.

Requirements

PHP 8.2+
CodeIgniter 4.3+

Fluent task scheduling - define scheduled work with an expressive API designed for CodeIgniter 4.
Multiple task types - supports framework ccommands, shell, events, URLs, and queue jobs.
Timezone-aware scheduling - run tasks using the correct timezone for your application.
Rich frequency helpers - includes hourly, monthly, specific times of day, and custom cron expressions.
Next-run calculation - makes it easier to inspect and understand upcoming schedules.
CLI tooling - publish config, list tasks, run the scheduler, and enable or disable task execution.

Requirements

PHP 8.2+
CodeIgniter 4.3+

See the release notes for details:
https://github.com/codeigniter4/tasks/re...tag/v1.0.0

Full changelog:
https://github.com/codeigniter4/tasks/commits/v1.0.0

Documentation:
https://tasks.codeigniter.com

Contributors

Thanks to everyone who contributed to the first stable release, including @ChoMPi0, @colethorsen, @datamweb, @ddevsr, @kenjis, @kloukas, @lonnieezell, @MGatner, @michalsn, @muhannad17, @samsonasik, and @yassinedoghri.

CodeIgniter Tasks is a task scheduler for CodeIgniter 4 that helps run scheduled work in a simple and framework-friendly way.]]> <![CDATA[Debug Toolbar Issue]]> https://forum.codeigniter.com/showthread.php?tid=93962 Sun, 29 Mar 2026 14:53:08 +0000 zeddy]]> https://forum.codeigniter.com/showthread.php?tid=93962 I just installed a fresh copy of CI 4.7.2 and set the environment to development (https://od.zeduweb.com/). The debug toolbar appears, but nothing happens when clicking on it (e.g. any of the buttons, the x to close, etc.). I am not seeing errors appear in the console either. Does anyone have ideas on how to troubleshoot?]]> I just installed a fresh copy of CI 4.7.2 and set the environment to development (https://od.zeduweb.com/). The debug toolbar appears, but nothing happens when clicking on it (e.g. any of the buttons, the x to close, etc.). I am not seeing errors appear in the console either. Does anyone have ideas on how to troubleshoot?]]> <![CDATA[Queue v1.0.0 Released]]> https://forum.codeigniter.com/showthread.php?tid=93961 Sun, 29 Mar 2026 10:26:29 +0000 michalsn]]> https://forum.codeigniter.com/showthread.php?tid=93961 CodeIgniter Queue v1.0.0 Released

We are happy to announce the first stable release of CodeIgniter Queue for CodeIgniter 4.

CodeIgniter Queue brings background job processing to CodeIgniter applications with a familiar developer experience, flexible backends, and the tooling needed to run workers in production.

Highlights

Multiple queue backends - supports database, redis/predis, and rabbitmq.
Flexible job dispatching - supports payloads, priorities, and delayed execution.
Chained jobs - build multi-step workflows that run in sequence.
Events and worker lifecycle hooks - useful for monitoring and integrations.
Failed job handling - includes failed job storage plus retry and cleanup commands.
CLI tooling - publish config, generate jobs, run workers, stop workers safely, inspect failures, retry jobs, and flush old failed jobs.

Requirements

PHP 8.2+
CodeIgniter 4.3+

See the release notes for details:
https://github.com/codeigniter4/queue/re...tag/v1.0.0

Full changelog:
https://github.com/codeigniter4/queue/commits/v1.0.0

Documentation:
https://queue.codeigniter.com

Contributors

Thanks to everyone who contributed to the first stable release, including @michalsn, @kenjis, @datamweb, @formbay-sanil, and @yassinedoghri.

CodeIgniter Queue is a queue library for CodeIgniter 4 that helps run background jobs in a simple and production-friendly way.]]> CodeIgniter Queue v1.0.0 Released

We are happy to announce the first stable release of CodeIgniter Queue for CodeIgniter 4.

CodeIgniter Queue brings background job processing to CodeIgniter applications with a familiar developer experience, flexible backends, and the tooling needed to run workers in production.

Highlights

Multiple queue backends - supports database, redis/predis, and rabbitmq.
Flexible job dispatching - supports payloads, priorities, and delayed execution.
Chained jobs - build multi-step workflows that run in sequence.
Events and worker lifecycle hooks - useful for monitoring and integrations.
Failed job handling - includes failed job storage plus retry and cleanup commands.
CLI tooling - publish config, generate jobs, run workers, stop workers safely, inspect failures, retry jobs, and flush old failed jobs.

Requirements

PHP 8.2+
CodeIgniter 4.3+