I put in another good 20 hours of work this week. I finally got to a ton of little fixes I’d been meaning to for a long time. I compiled a bunch of feedback we got from the face-book page, the walls on the BETA site, and from some of the testing our team and other people had done this week and earlier.
- still more formatting fixes (almost there)
- brand new more inviting registration page
- log-in error feedback, and redirect to full login-page.
- registration error/success feedback
- edit profile error / success feedback
- added links the the user profile when you click their name in the ‘recent items’ list.
- added links to more information in the logged out ‘big box’
- I made some new colorful buttons for the 3 major links on the logged-in user page
- full working edit profile section
A majority of my time was spent on this edit profile interface. First of all, it just wasn’t working at all before, so I overhauled it. We moved the edit profile page into a new tab inside the user profile. This makes sense as it has do do more with the user profile than anything else, and it also keeps the links under the user drop-down more unified. I then made all the various links to the settings page, and redirects point to this new location. Next I had to completely re-write the script that ran to check the information. I implemented a check for each field this time. First it checks to make sure you entered an old password, and that it indeed matches the user password in the DB: this is required to edit any settings. Next, it checks each field, if you entered information it adds it to a list, and if you didn’t it adds your standing information to the list. Then this list is re-entered into the DB as your user information.
This new system also starts to implement a one-field full-name slot for the DB and the site. We still need to add this change to some other pages, but it doesn’t effect too much. Right now it keeps the first names that were in the DB, but users will have to re-add their last name if they had one registered (which most of them did not anyway)
- setting / storing birthday information
- started to implemented user name
- full-name paradigm (production begun)
- character limit for branches implemented
- logged out trespassing feedback “you need to be logged in to do that”
- automatic flagging for mature content based on profanity search
how this works now is that instead of replacing profanity, I wrote a function which searches each posts every time you write one or view one (a double safety) and if any of the words are found in the post, it automatically changes that posts rating to mature. The team agreed this would be a better way to go about it.
- implemented blurb creation whenever a story or branch is mode.
- other users only see your testimonials you approve (production begun)
I started to build functionality for this last item: first I made an ‘approved’ field in the DB. Next I made it so that whenever you go to a user profile you can only see the testimonials they have approved. If you’ve written a testimonial on somebody else’s wall it shows up dimmed until it is approved. Also, whenever you write on your own wall, it automatically gets approved. I started to make boxes and approve buttons for non-approved posts on your own profile, but I didn’t get to all the functionality there just yet.
I think instead of relying on Aaron to help me with the rest of the Ajax that needs to get done for this function, and especial the rest of the functionality for commenting and story combining, I’m going to need to sit down and wrap my head around it myself. We have too much work in the next 2 weeks for any work being held up. It shouldn’t be difficult, I’ve just been cautious about how much work I do on the JS side, since Aaron had a lot of the architecture set up. This week I’ve also started to take a look at that.
Next week I hope with this new knowledge I can get the user In-box set up (if for nothing else, sending notifications to users about branches being written to their stories, and testimonials). This coupled with the functionality to delete unimproved posts marks a major remaining void in the functionality we’ve promised for week 8 and I pledge now to have them done this week ASAP.
If we get the others started now on the remaining pages that need to be built for the other items on the list, we should be in good shape to have them hooked up by me next week.
- Christian