Wednesday, October 26, 2011

Progress Report (Week of 10/19-10/26)

What I accomplished the past week:
I have been working in the user account area fixing bugs and adding new functionalities. All account related web pages that can be modified by the owner are forbidden from access by any other users who are logged in. I have also set up the edit profile page for each user, so that there is now an about me and location field. I am still modifying the password recovery system.

What I plan to do next week:
I will continue working on the password recovery system and begin the implementation of the comments system for each individual project.

Concerns:
None

Tuesday, October 18, 2011

Progress Report (Week of 10/12-10/19)

What I accomplished the past week:
I have implemented the password recovery system for public users. I have also added a "change your password" page for users who are logged in to change their password. I am still in the process of implementing a password recovery system for student users.

What I plan to do next week:
I plan to finish the implementation of the password recovery system for student users and to continue finishing up implementing account settings for users to change.

Concerns:
None

Tuesday, October 11, 2011

Progress Report (Week of 10/05-10/12)

What I accomplished the past week:
I have replaced the long registration link found in the email with a tinyurl link. I am still in the process of implementing the password recovery system, and this should be done by next week.

What I plan to do next week:
I plan to finish the implementation of the password recovery system and to continue the re-design of a user's profile page.

Concerns:
None

Tuesday, October 4, 2011

Progress Report (Week of 9/28-10/05)

What I accomplished the past week:
I finished redesigning the url routing system for the website. Now the framework has checks in place to verify user permissions as well as checking the validity of the link in question.

A new registration process has been implemented. It works by having two registration phases. The first one asks the user for their name and their email address. The website will then send an email to them with a link to the second part of the registration. This part is where the user enters in their desired username and password. The database does not store any information regarding a user who does not completely finish their registration. This is because the link sent through the confirmation email contains the user's name and email, which is encrypted using a public-private key algorithm. The framework does a validation check on each url to confirm that the link hasn't been tampered with.

I also fixed up the website's navigation website by changing the previous look and feel of the site. To achieve this, I got rid of the side bar login screen and decided to include these components at the top of the page. Next, I moved the search option up to the header to open up the side bar. Now, only web pages that need the side bar can use it; otherwise other pages can use that space. I also got rid of the banner images on each and every page. Finally, I was able to make all footers stick to the bottom of the page.

What I plan to do next week:
I plan to implement the password recovery system and to start the re-design of a user's profile page.

Concerns:
None