Overall Satisfaction with CodeIgniter
CodeIgniter is the framework our content management system is built on. It is used university wide. CodeIgniter allows the web services team to easily develop customizations within the CMS. Some applications include developing API integrations with other third party services, our single sign on program, cache breaking, along with text and image manipulation.
- The active record class allows creating readable SQL statements that can be easily understood across the team's varying skill levels.
- The input class makes it easy to provide server side validation and scrubbing of user input.
- As an MVC framework, separation of code and presentation layer is easily implemented.
- While the active record class is nice, there are occasionally times where it is unsuited and a custom SQL query needs to be coded.
- An authentication method against an Active Directory would be nice. Everyone wants single sign on these days.
- Composer integration would be a nice to have
- Being able to build integration points in our CMS to our analytics and quality assurance products allows us extended use of those products via their APIs.
- Development of the framework had stalled for a period of time
- Using a CMS build on CodeIgniter has had a significant cost savings compared to other enterprise CMS solutions.
Both older and new versions of CodeIgniter lack installation via Composer. Laravel is our other framework of choice; its installation, updates, and addition of third party packages are significantly easier with Composer. CodeIgniter is our primary framework as our CMS is build on it and creating custom integrations and add-ons for it with CodeIgniter are easily accomplished.