[rolly]

Please god make a Stable First Release!

[andoyoandoyo]

CodeIgniter-4.0.0-beta.1 launches today

This is a pre-release of 4.0.0. It is not suitable for production! (but it is pretty darn close)

Release highlights:

• New View Layouts provide simple way to create site site view templates.
  
• Fixed user guide CSS for proper wide table display
  
• Converted UploadedFile to use system messages
  
• Numerous database, migration & model bugs fixed
  
• Refactored unit testing for appstarter & framework distributions
   
  

New messages:

• Database.tableNotFound
  
• HTTP.uploadErr...
  

App folder changes:

• app/Config/Cache has new setting: database
  
• app/Views/welcome_message has logo tinted
  
• composer.json has a case correction
  
• env adds CI_ENVIRONMENT suggestion
  

Check the changelog for details, and the installation writeup for further directions.
Looking to upgrade from CI3 to CI4?

We expect 2-3 beta rounds, as we continue to fix remaining bugs and tighten up the code.
We don't plan any official release on April 1st, just so you know
Thank you to the community for stepping up to help make this the best PHP framework!

Do NOT post support questions or feature requests in response to this thread - those will be deleted. We are trying to make the best of the limited resources that we have!

Thank you, and ENJOY!

Alhamdulillah. Great to hear that. Thank you so much buddy

[andoyoandoyo]

Please god make a Stable First Release!

We have to be patient likely

[jasonzig]

I was wondering if something along the lines of this article might be appropriate? (It would massively help me, for instance!)
CodeIgniter 4, A Complete New Ballgame.

Good article
It needs refreshing for the way CI4 has actually turned out, but would make a good start.

If you use the appstarter package, or "require" the framework package, rather than the "CI3" manual installation, then release updating will become embarassingly simple. Yes, there us the onetime pain of converting from X to 4.0, but then updates become "composer update", and then check those "app" changes highlighted in the release notes.

Namespaces will take getting used to, agreed, but they solve potential naming collisions. Composer installation of packages will eliminate most of the hiccups with "HVMC" in CI3, as long as appropriate namespaces are used in such packages.

Maybe we need to encourage CI4 tutorials to help the diverse developer groups, and complement Lonnie's original blog posts!

Thanks for the excellent "What's New & Changed" content here!

[fajarsulaksono]

Good news, Great job, I really appreciate the efforts of all team members.