Assignment 9: Rich Text Editor. Due Wednesday, Aug 17th.
For this assignment you will need to install a Rich Text Editor (RTE) for administrators to login and make changes to site pages you designate.
Your model for the design changes necessary is the Rich Text Editor package. Please view this carefully, as all instructions to accomplish this task are to be found there.
Documentation: All of your documentation sources need to be kept up to date with your progress. Particularly the "Page Description" spreadsheet would need to be updated to include documentation and explanation of the purpose, contingencies and feeding/fed by files related to the files you are creating. Also, if you are doing work, I expect to see it reflected in your blog. EXCEPTION: Only document the files you edit for the fckEditor!
ACCESS FOR GRADING: Create a "Developer" level administrator with the login/email of developer@example.com, and a password of asdfasdf. Please keep this available, so I can view your work. If you are working on a public site (or have sensitive data) please email a password.
So what is ACTUALLY due for this assignment?:
- Rich Text Editor Integration, so I can login and edit site pages you designate
- Links to editable pages via your admin page, with information identifying WHICH page is editable, so I know which pages to test
Extra Credit: Successfully integrate the 'File Upload' piece of the handout with RTE's for a possible 30 extra points!
Assignment 8: Image Upload. Due Wednesday, Aug 10th.
For this assignment you will need to get an Image Upload system built for administrators to login and upload images currently visible on your 'view' pages.
Your model for the design changes necessary is the Image Upload Package. Please view this carefully, as all instructions to accomplish this task are to be found there.
Documentation: All of your documentation sources need to be kept up to date with your progress. Particularly the "Page Description" spreadsheet would need to be updated to include documentation and explanation of the purpose and contingencies related to the files you are creating. Also, if you are doing work, I expect to see it reflected in your blog.
ACCESS FOR GRADING: Create a "Developer" level administrator with the login/email of developer@example.com, and a password of asdfasdf. Please keep this available, so I can view your work. If you are working on a public site (or have sensitive data) please email a password.
So what is ACTUALLY due for this assignment?:
- Image Upload Integration, so I can login and upload images over your existing 'view' images
- Your page description and weblog needs to be updated to reflect all work, time spent & related files.
Extra Credit: Successfully integrate the 'Thumbnail' piece of the handout with your 'list' page for up to 30 extra points!
Assignment 7: Administrative Login Integration. Due Wednesday, Aug. 5th.
For this assignment you will implement an administrative area for your website. This area will consist of web pages and files that create a web application that allows administrators to login and view private pages.
The administrative pages will be protected via PHP Sessions, where anyone who tries to access a page before successful login will be redirected to the login page.
Your model for these pages is the "nmAdmin" package. Follow the directions in the word document to create the admin files.
Once you have your admin setup and working, please create a 'developer' level administrator, using the email 'developer@example.com' and make the password 'asdfasdf'. I'll be using this login to view your work.
All visible admin pages must be integrated into the 'look and feel' of your site design. Specifically, the visible pages must have the appropriate header, footer and nav as the rest of your site.
Documentation: All of your documentation sources need to be kept up to date with your progress. Particularly the "Page Description" spreadsheet would need to be updated to include documentation and explanation of the purpose and contingencies related to the files you are creating. Also, if you are doing work, I expect to see it reflected in your blog.
ACCESS FOR GRADING: Create a "Developer" level administrator with the login/email of developer@example.com, and a password of asdfasdf. Please keep this available, so I can view your work. If you are working on a public site (or have sensitive data) please email a password.
So what is ACTUALLY due for this Assignment?:
- Password protected administrative pages allowing add/edit/delete access to all your database tables
- The above page (or pages) need to be protected via login and password, with an administrator login and password I can use (developer@example.com, 'asdfasdf')
- Your page description and weblog needs to be updated to reflect all work, time spent & related files.
Assignment 6: Paging. Due Monday, July 29th.
For this assignment, you'll add paging to your list & view pages. (Well, list page, to be exact).
Your model for these changes is the Pager class on the Classes/Paging lesson on the class website.
All your site documentation pages need to be updated! Update that blog with time spent!
Assignment 5: List/View Pages. Due Wednesday, July 29th.
For this assignment you will need to build custom (meaning personalized) list & view pages, modeled after the 'muffins' example from the List/View lesson. These pages could be adjusted to match the final goal of your site, in which the items featured will appear. Example List/View Code
To get the most out of this class, I recommend thinking of using your database to store items that can be thought of as an inventory. If you plan to sell or display things, for example, you could build a table of pictures, CDs, books, articles, artwork or crafts.
A prior student of the class built a list/view application on bicycle hazards
You will need to build this table in MySQL, and feature the data (items) on your "list" and "view" pages.
All pages (however) must have the entire look and feel of your site design, in that the pages must include your custom nav, header and footer as appropriate.
All "view" pages need to feature a "custom" (unique) image! Customers need to know when they are on a different page, and a custom image is a good way to let them know. If you are doing a calendar site, you could use number "images" to indicate the date, etc.
YOU MUST HAVE AT LEAST 20 TOTAL ITEMS FEATURED. If you don't have 20 items, fabricate believeable material, that can be deleted later!
Once your list/view pages are functional, link your page on your "final" website.
All your site documentation pages need to be updated! BLOG ENTRY REQUIRED OR POINTS OFF!
Assignment 4: Functional Includes. Due Monday, July 27th.
This assignment will have us re-configure our include files and add functional include files to create a unified site architecture.
Doing so will allow us to store DB credentials, error & session handling and PHP configuration settings and apply these sitewide. Install the pages as described in the handout below:
nmCommon
Once you have these application pages installed, be sure to swap the header, footer and stylesheets for your own.
All of the involved files need to show up on your page documenation spreadsheet.
Once done, link your new version of first_data.php (with your include files applied) as Assignment 5 on your construction page.
Update all documentation, including your blog, or I may deduct points.
Assignment 3: Troubleshooting Exercise. Due Monday, July 20th.
This assignment will be to troubleshoot a PHP page called "adder.php". Before the errors were added to it, the page was designed to add 2 numbers via a form field, and produce the correct answer. Here is a link to the repaired version:
adder "repaired"
In the attached word doc, you will find some instructions, and the "damaged" version of "adder.php". Please print this word doc, (if you have not already done so) and follow the directions on the sheet. Copy the code from the word doc to begin troubleshooting.
When you are done, you will be linking the finished product to your construction page. If you are unable to complete the troubleshooting, track all of the functional errors you find, and detail them on a word document, for partial credit.
IMPORTANT: Be sure to track the errors you find right away when you start troubleshooting, in case you can't find all of them!!
Below is a link to the word document with the damaged code, and instructions for the assignment:
Assignment 3: Adder word doc
HINT: For troubleshooting techniques refer to Troubleshooting Lesson!
Assignment 2: HTML & PHP Templates. Due Monday, July 13th
For this assignment you will need to decide on the look and feel for your site (at least temporarily).
You will first create an HTML 'template' page, that will carry the basic look and feel of your website, and will function properly in all browsers you choose to support.
Be sure your template 'behaves' in at least Internet Explorer and Firefox! You need to fix ALL html errors before going to the next step!
Once you have your HTML template, you will split that file up into functional include files, based on work in class and the includes lesson page. The page thus created will be the 'starting point' for all your other pages.
This 'starting point' we'll call the PHP Template (since we'll keep the HTML template as well for reference).
Your PHP Template must be functional, and feature at least 2 include files. At a minimum, these would be a header and a footer. The footer must feature a dynamic copyright.
Feel free to use the following PHP template as a starting point. Remember to at least change the colors to make it your own look & feel: PHP Template
Update all applicable documentation, most specifically the 'page description' and 'weblog'.
Please link the assignment as target="_blank" on your construction page.
So what is ACTUALLY due for Assignment 2?:
- A HTML template page featuring the look and feel of your website, that functions consistently in IE/FF
- A PHP template page that must be composed of at least 2 include files
- All involved pages (HTML Template, PHP Template, include files) must show up on your Page Description (spreadsheet)
- One of the include files must feature a dynamic copyright
- All documentation (page desc., etc.) must be up to date
I will start taking points off for lack of documentation. Keep those documents up to date!
What to blog?
Assignment 1 will lay the groundwork
for your final project, a dynamic web site.
