The New Myth family: SprintPHP Bonfire Practical CodeIgniter 3

New Myth Media Blog

Serving the New Myth Media Family.

Practical CodeIgniter 3 Released

My new book about making the most of CodeIgniter 3 is out!

One roof. It might be slightly leaky, and might ping nicely when the rain hits the metal, but it's all under one roof, now. At least, the blogs are.

This is the first stage of an effort to consolidate my open source projects into one big, happy family. This will be the home now for all news regarding Sprint, Bonfire, my book, Practical CodeIgniter 3, and any future projects that might fall under this umbrella. You can also expect to find new tutorials from time to time, not just about Sprint or Bonfire, but about anything related to web development and/or design, but especially CodeIgniter, since there's some pretty cool stuff coming down the road in v4 discussions that I'll want to talk about.

Built On Sprint

This blog engine, while pretty basic, is built on top of Sprint. Yes, the dog food tastes great. To make it simple to keep the post history in the repo, it was built to be 100% file-based, using Markdown formatting for the blog (just like the previous one) with some custom header info to keep categories, title, and author information, and more.

I'm sure it will grow in capabilities over time, but seems to be working pretty well for us at the moment.

Coming Soon For The Family

At the top of this site, you can see the "Family Bar". This is all part of the consolidation process. That, and the featured news section (just below the header) will make their way across all of the sites for all members of the family.

The next few stages that will be happening are as follows:

  1. Sprint gets a home. Currently, it's a homeless project whose only information is sitting in GitHub. We know that's sad, and probably lonely for the poor guy, too, so I'm building the project a new home. This is very close to being ready to launch.
  2. Documentation Hub. Current and past versions of documentation for Bonfire and Sprint will find a new online home all in one place, as part of the new documentation hub that is under development. This is using a completely rewritten documentation engine. It's using a standalone doc engine that is a mix between what Sprint has, and that can generate static pages out of all of the docs and still keep everything searchable. It's not quite ready, but getting fairly close. Once complete, this new docs engine will find its way into both Bonfire and Sprint, replacing what is currently there.
  3. Bonfire gets a refresh. Bonfire's site will get a refresh to keep it matching the feel of the rest of the family. Can't have it feeling like an orphan in old rags, because it definitely is not.
  4. Forums get a redo. The current forums are pretty sad, I know that. I'm falling out of favor with the Vanilla, and it's really not doing us much love. I've got grand ideas about how a forum system could be created that would really rock, but we will have to wait and see if I've got the time to do that or not. If not, I'll have to revisit the existing solutions out there to see what would work best.

Thanks for being here

Without your continued interest over the years, Bonfire -- and now Sprint -- would not be here. Thank you for your excitement and kind words over the years. May we have many more to come.

Over at GitHub, I've opened an issue regarding increasing the minimum PHP version for the 1.0 release of Bonfire. We're interested in finding out what version of PHP everyone out there is currently using, especially those of you who might have less control over the PHP version run on your server(s).

It has been over two years, and three hundred thirty issues have been opened in our GitHub repository, since we upgraded the minimum version of PHP for Bonfire to 5.3. At this time, we're considering upgrading to 5.4 for the 1.0 release (so 0.7.x and 0.8.x will be unaffected), and probably moving to 5.5 after another 6-12 months.

Further details regarding the benefits and ramifications of the upgrade can be found over at GitHub.

Thanks for your help in this matter and continued support,

  • Mat Whitney

The short version (all dates tentative):

  • 0.7.4 by June 11th, 2015
  • 0.8 by June 12th, 2015
  • 1.0 by January 1st, 2016

The long version:

I am currently planning to release Bonfire 0.7.4 next week. This is intended to be the last release which ships with CodeIgniter 2.x. While the release will go into the master branch on GitHub initially, I will create an additional branch to hold this release for those users who still need a CI2 release of Bonfire in the future (and there may be future 0.7.x releases to keep CI2 in synch, as needed). Of course, since CI2 itself will only be receiving security updates through October, it is highly recommended that everyone using Bonfire make an effort to move to CI3.

With that in mind, Bonfire 0.8 will also be released next week. Bonfire 0.8 will continue to support CI2, but will ship with CI 3.x installed and enabled by default. The process for using CI2 in Bonfire 0.8 will be similar to the process for using CI3 in Bonfire 0.7, and the documentation will be updated to include that process.

Sometime after CI2 reaches end of life, I will go through a similar process to create a support branch for 0.8 (for those people transitioning their sites from CI2), and start working on a 1.0 release for Bonfire, which will drop support for CI2. This will remove some of the extra code which currently allows Bonfire to support both CI2 and 3, though some things (like the bcDirectoryMap function in the BF_directory_helper) may remain longer than others.

Thanks for your continued support and interest in Bonfire.

  • Mat Whitney

Sprint was just updated to use ZendFramework's escaper for the auto-escaping of data in ThemedController. This now supports different contexts to ramp the XSS protection up to 11.

This IS intended as a replacement for CI's xss_clean function. You should definitely upgrade, read up on the Escaper, and modify your code to ensure your security is kept working well.

Documentation has been updated in the repo to reflect this change.

Thanks to the help of some issue reports on GitHub and a focused effort on testing the Bonfire core with CodeIgniter v3.0, I'm announcing the release of Bonfire v0.7.3. This release drastically improves the functionality of Bonfire when used with CodeIgniter v3.x.

At this point, I believe Bonfire is ready for real-world use with CI3. Since I intend to start testing integration of my own site with CI3 using this release, fixes for any bugs I find or which are reported for this release will go into v0.7.4.

At this time, I intend for the future v0.7.4 release to be the last release which ships with CI2 installed and running by default. While I intend to support using CI2 in the v0.8.x line, it will require some extra steps to get things working, similar to those currently required for CI3.

I'd like to thank everyone for their patience regarding the lack of progress in other areas of Bonfire during this period of transition to CI3.