How to: Create an Admin panel with CodeIgniter

[eluser]Phil Sturgeon[/eluser]
[quote author="Dam1an" date="1247086853"]I find the title misleading, especially as I came accross a similarly titles post yesterday for cakePHP. Excpet the cakePHP one was more of a dashboard showing the current status of your application, traffic, visitors, refering links, real time errors etc... I was hoping this would be the same sort of thing[/quote]

The articles aim was to outline the best possible structure, not to tell you how to write your applications. That much people can do for themselves and any article trying to tell people how to write the actual code for their admin panel would be covering too many variables.

[quote author="Dam1an" date="1247086853"]On a totally unrelated side note (well, not totally unrelated)
Whats upp with your RSS feed, it seems to have pushed all of your posts out again from the very begining (until I realised I'd seen them all before I though you had a surge of activity on your blog lol)[/quote]

The recent multi-langification of PyroCMS (and therefore my blog) introduced a bug to the RSS feed. I fixed that yesterday so a few RSS readers may have issue with that and show all articles as new. Sorry for the confusion.

[quote author="umefarooq" date="1247100052"]i have used this structure with my application is working fine with me my url is always

access dashboard of admin
http://localhost/ci/admin

to access user or content
http://localhost/ci/admin/user

and add,edit will work in same way
http://localhost/ci/admin/user/add

no need to put any thing in route file.

its really working fine using HMVC. you just give one try to it will work[/quote]

Of course it works, but its a pain in the backside having files in many places. With my modules I can add or delete one folder and run the SQL and thats IT they are installed. Means files are only ever in one place which is the entire point of having modules.

Due to the extreme modularity of this approach (and therefore PyroCMS) I'll soon be able to have a install/uninstall service offered over REST which will download a single folder to your install from my server and run one set of SQL commands, boom, your module is installed.

If code was shared all over the place I would have to play "hunt the code" and introduce all sorts of annoying things like file mappers that work out which file belongs to which module, etc. What if they are shared? Nightmare!