Comments on: Building Applications using CodeIgniter (Part 1) – File Structure

By: Integrating Wordpress & CodeIgniter | Marion Newlevant: Web Developer

Integrating Wordpress & CodeIgniter | Marion Newlevant: Web Developer — Mon, 06 Dec 2010 08:00:26 +0000

[...] set up CodeIgniter file structure w/ application at same level as system, and top level assets dir (not necessary, but I like it this way): http://www.christophermonnat.com/2009/04/building-applications-using-codeigniter-part-1-file-structu... [...]

By: Chris

Chris — Tue, 24 Aug 2010 13:59:41 +0000

Nuno, the download I created is really to be used as a template so I don’t necessarily want to add any extra files. Including a template within a layout is just as easy as loading another view file but within a view file. So, within your layout view file you simple say $this->load->view(‘_templates/footer’); or something like that. In this case I’m loading the footer.php view file within the _templates folder. That will display that template within the view.

As far as my layouts are concerned, I simply echo a bunch of variables within the view and then pass those parameters to the view from the controller. In some instances I’m returning views as strings to simplify things. To return a view as a string you simply add a TRUE parameter to the load function like so: $this->load->view(‘_templates/footer’, $params, TRUE); and that returns the specified view as a string into a variable which is then passed to the layout view.

Hope that helps.

By: Nuno

Nuno — Sun, 22 Aug 2010 03:28:38 +0000

Hi Chris
I’m starting my move to CI and MVC approach, and I find your articles so interesting…
I’m still heaving troubles reproducing your views _template-layout engine method.
Could you kindly rebuild your CI install from this series of articles, by adding a view using a template and calling parcial views from the layout file?
Those 2 extra files (template+layout) would clear the fog…

Thanks, best wishes

By: Chris

Chris — Mon, 09 Aug 2010 14:28:46 +0000

Yes, I will typically create an “admin” or “backend” folder in the controllers directory. That way all admin controllers are separated from the rest of the project and they can only be accessed by /admin/controller. Beyond that though I really don’t do much in the way of separation. I will sometimes also organize assets into front and back end but not too often.

By: Mark

Mark — Mon, 02 Aug 2010 12:20:02 +0000

this is really a great article. However , I was wondering how do you organize file structure for front and backend, would you create admin folder?

By: Getting Started with CodeIgniter and How to Create All Those Great Apps | PHP Lovers

Fri, 07 May 2010 07:15:15 +0000

[...] Applications using CodeIgniter Series: File Structure, Configuration,Helpers, Code [...]

By: Roppa

Roppa — Thu, 25 Mar 2010 12:12:50 +0000

Cool stuff. I love CI and will be using it a lot more so thanks for the info!

By: Getting Started with CodeIgniter and How to Create All Those Great Apps « Web Development News

Thu, 11 Mar 2010 13:04:19 +0000

[...] Applications using CodeIgniter Series: File Structure, Configuration, Helpers, Code [...]

By: Getting Started with CodeIgniter and How to Create All Those Great Apps | DevSnippets

Tue, 23 Feb 2010 12:03:01 +0000

[...] Applications using CodeIgniter Series: File Structure, Configuration, Helpers, Code [...]

By: Chris

Chris — Fri, 14 Aug 2009 14:13:53 +0000

Saad… you might have me stumped here. I’ve never had to deal with a multi-lingual CI project before. I think your on the right track though. If you create 2 folders in the root of views called en and ar and then mirror the folder structure between the two, so the only difference is the text on the pages, you should be able to store a language preference in a session or something and then load the appropriate views based on that preference.

Hope that helps.