if you are adding 30+ controllers just for CRUD, think about abstracting the models into a MY_Model.php core file. Keep it DRY, it makes testing easier too.

Eric

On Fri, Nov 30, 2012 at 10:33 AM, keith smith <klsmith2020@yahoo.com> wrote:

If I can avoid modifying the routing.php script that would be great.

I watched both video's that were on the old CI site, read lots of posts on Google, and have a book that I read cover to cover.

I have not found any real in-dept info on CI routing.

Thanks for your help!!

------------------------
Keith Smith

--- On Fri, 11/30/12, Tom Haws <tom.haws@gmail.com> wrote:

From: Tom Haws <tom.haws@gmail.com>

Subject: Re: OT: CodeIgniter Routing
To: "Main PLUG discussion list" <plug-discuss@lists.phxlinux.org>
Date: Friday, November 30, 2012, 9:53 AM

Yeah. Keep researching CodeIgniter tutorials, because ideally, you wouldn't ever need to use routes.php unless you had a need for an alias or some other special occasion.

On another note, it would be more conventional to talk to your database tables in model files and then call model functions in your controllers. Again, I recall watching a short CodeIgniter tutorial video that really helped clarify this.

--
"To forgive is the highest, most beautiful form of love. In return, you will receive untold peace and happiness." - Dr. Robert Muller

On Fri, Nov 30, 2012 at 9:36 AM, Eric Cope <eric.cope@gmail.com> wrote:
You can just put your controller "pages" in the controller/cp directory...

Then you don't have to muck with the routes...

Eric

On Fri, Nov 30, 2012 at 9:20 AM, keith smith <klsmith2020@yahoo.com> wrote:

Hi,

I'm rather new to CodeIgniter. I'm using version 2.0.3 and am using the provided .htaccess code to remove index.php from the URL.

I'm working on a control panel and would like to set up a controller for each table to keep things simple and modular. (any feedback on a better idea is much appreciated)

I was thinking I needed to configure the controllers this way

1) $route['cp/pages/(:any)'] = "cp_pages"; (would contain only controller code for managing the pages table.)

2) $route['cp/users/(:any)'] = "cp_users"; (would contain only controller code for managing the users table.)

.... other table configured with their own control panel.

3) $route['cp/'] = "cp"; (splash page and menu. If not logged in presents the log in form)

/cp/ gives me the splash page. so far so good.

/cp/pages - cp controller - not what I was expecting. I was wanting the index function of the cp_pages controler.

/cp/pages/list/ - takes me to the cp_pages controller / index function

What I would like to configure is:

/cp/ - use cp controller

/cp/pages/ - use the cp_pages controller / index function
/cp/pages/add/ - use the cp_pages controller / add function
/cp/pages/list - use the cp_pages controller /list function
/cp/pages/list/10 - use the cp_pages controller /list function with segment set to 10 as starting point.

If I'm going down the wrong path please let me know.

Thank you!

------------------------
Keith Smith

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

-----Inline Attachment Follows-----

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss