php - CodeIgniter 2.x Back-end and Front-end management -


i saw many threads, articles , clever posts concerning layouts both backend , frontend approach on same website.

i hear feedbacks (pros , cons) each type of introduced front/backend management had real experience codeigniter:

  1. controller-separated section

    ./web/system/... ./web/application      /application/controllers/* (config/controllers/hooks/models/views...)      /application/controllers/admin/* (config/controllers/hooks/models/views...) 
  2. application type of cms

    ./web/system/... ./web/front/* (config/controllers/hooks/models/views...) ./web/admin/* (config/controllers/hooks/models/views...) 
  3. sub-application

    ./web/system/... ./web/application      /application/admin/controllers/* (config/controllers/hooks/models/views...)      /application/front/controllers/* (config/controllers/hooks/models/views...) 

thanks suggestions , tips.

what did our application create structure so:

the application folder divided 3 subfolders backend frontend common

this helped better structure our resources when goes wrong in backend not need sift through frontend files, instance.


Popular posts from this blog

Toyota Camry

Delphi interface implements -

ios - UISlider customization: how to properly add shadow to custom knob image -