Chapter 8: Last-Minute Upgrades
266
“ Well, I ’ m going to be doing a sweep tomorrow to secure the web site. Anywhere there might be a place
for someone to cause mischief, I ’ m going to make it harder for them to do that. I ’ m also going to be
running a few tests for performance and setting up caching so your site can handle lots of visitors. ”“ Sounds good! Then we can turn on the checkout features and go live! ”“ We ’ re just about there. It ’ s exciting, isn ’ t it? ”Conclusion
In this chapter, you added a simple page management feature to the site, as well as a rudimentary but
effective Newsletter tool that Claudia can use to communicate with her customers. In the next chapter,
you ’ re going to apply some security features to your application and tweak the site for performance.Remember to keep these thoughts in mind as you continue working with CodeIgniter:It ’ s been said many times in this book, but it bears repeating: Just about any programming task
can be handled in CodeIgniter if you break it into small enough pieces and/or phases.Learn how to use such tools as the E - mail and File helpers — they help you conquer mundane
tasks like validating an e - mail address or writing log files.Don ’ t be afraid to reuse or copy views, models, and controllers when you build new
functionality.Sometimes upgrades and requests happen outside the regular notion of sprints. In this chapter,
you saw a scenario in which two medium - sized additions were made to the functionality
without the need for an extra sprint. Use your best judgment in these situations. They happen
all the time, and it would be less practical to be 100 percent rigid about not undertaking them.
However, if you don ’ t feel comfortable making on - the - fly adjustments, then you can certainly
create a process around them.