Hi,

I am currently trying to put some CLI commands into a different folder than the standard app/Controllers folder.

I want to put it into app/Modules/Mod1/Controller

The putting the test CLI code into the folder is straightforward and all works fine in the main app/Controllers folder. But in my Modules folder, I cannot find the right set of paths to make it run.

I have put my Mod1 into the autoload.php as with the other modules. They all run fine.

So, what do I need to type on the command line to make the test code run.

I have an integration vs. Wordpress and set some data into the session. I am doing the operation in a Filter in the before function.
My implementation did before use the FileHandler for session which worked as a dream.
When switching to the DatabaseHandler, values being set to the session is not persisted and not available upon the next request.

Any reason why the set doesn't work from a Filter with the Databasehandler ?

Rgds Geir

i'm config baseURL = " https://intranet_new.mysite.com:8080/report/public/ " on production ( CodeIgniter 4.7.2) .
and my application display : Fatal error: Uncaught CodeIgniter\Exceptions\ConfigException: Config\App::$baseURL "https://internet_new.mysite.com:8080/report/public/" is not a valid URL ...  #19 D:\www\report\system\Debug\Exceptions.php(117): service() #20 [internal function]: CodeIgniter\Debug\Exceptions->exceptionHandler() #21 {main} thrown in D:\www\report\system\HTTP\SiteURI.php on line 200
Thanks for help me.

Can anyone with bigger mind see and write an adapter for flasher?
https://github.com/orgs/php-flasher/discussions/205
Its realy good tool.
Thx

I discovered that I had over 400k ci_session files in the writeable/session folder.
The oldest files were back from February. I checked the Session.php which had
public int $expiration = 7200;

What is causing those old session files not to be deleted ?

Geir

Today, I have run into an issue with exception handling when testing. I was building an API and wanted to take advantage of the exception handler and use exceptions to drive responses and this worked perfectly in dev or production modes. but when I wrote tests for the api endpoints, these exceptions were not being handled by the handler I registered. On digging deeper, I found out that the error handler registered by ci4 was running instead of the exception handler. To be honest, I would not consider myself an exceptional developer, so I have no telling why the error handler was firing instead of the exception handler. Is this a BUG?(current version 4.7.2)
Here is the exception handler: 

After calling software engineering 'dead,' Anthropic’s Claude Code creator Boris Cherny says coding tools like Microsoft VS Code, Apple Xcode, and others will be ‘dead soon’

Hello guys,
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

Hi everyone,
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:

I've been a rabid supporter of CI since 1.7.2.  During the 'great lull' Codeigniter really took a hard hit with Laravel coming up and many devs jumping ship. I really want to do my part to help CI get back to the popularity it once had and (*gasp*) maybe rival Laravel.   

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.