- Prospective student directory: Converted notes to an object holding note, author, and time stamp for storage in the database and manipulation in PHP.
- Made sure dates are converted to user’s local time zone whenever printed by using a JS cookie to store the browser’s timezone. This cookie is retrieved whenever a date is to be printed so it can be displayed in the proper time zone.
- Worked on styling faculty notes for clear legibility.
- Changed the way recital hour faculty emails were addressed. They are now addressed like “Dear [personal title] [last name]”
- Edited Recital Hour programs to display proper instrument names, all signups (not just approved ones), and proper accompanist title and name.
- Dug into the login process to make sure the process is correct. Wrote 3 functions so now we can see exactly what the error is when someone has difficulty logging in.
- Attaches to authentication and if there are errors, saves them to a session variable.
- Makes sure PMPRO does not interrupt redirect back to wp-login.php
- Retrieves the error from the session variable and displays them on wp-login as message.
- Went through all users that have never logged in. I started with adjuncts and edited each profile to generate a random password and then emailed each of them with the new information. I only have to do this with users who have never logged in because of possible data corruption from the first week AND the fact that I used not-very-secure passwords for the beginning of the semester to make it easier for users to signin.
- Followed the process to reset passwords and fixed all errors. Made a big breakthrough because I discovered that the redirects are being processed in the Thim theme instead of one of the plugins. This is huge because it means that many of the little problems I’ve been trying to sort out are probably all buried in the code for this theme. Since I’ve been slowly replacing code from this theme and hope to have it all replaced by end of the year, it means that the entire website will be faster, less bloated, and more efficient.
- After months of reading and probing code I have decided to code my own connection between WordPress and Moodle, which is used for the Theory Placement Test. We need the functionality to be able to connect WordPress users with Moodle without them knowing they are taking the test from a second web technology. Edwiser sells a plugin called Bridge that does this and much more, meant for selling courses. I had even coded some functions in June using their plugin to accomplish what we need. But in the end, trying to hook into someone else’s plugin makes the code too delicate and prone to bugs. So I decided to write my own. I finished writing the connection between WP and Moodle as well as functions to add users, enrol them in the course, delete users, update passwords, list courses, as well as creating options for the Moodle token and course number that contains the Placement Test.
- Researched, installed, and became familiar with code for “User Key Authentication” Plugin for Moodle. This allows me to write functions to login and logout users directly from WP in Moodle. It’s an SSO system, meaning users have one single sign-on for WP and Moodle, but they never know about it. This allows me to incorporate the Teory Test directly into WordPress without users having to create a separate account with Moodle. So far, functions for:
- moodle api (master function to handle all connections with Moodle)
- enroll user into Moodle
- enroll user into Theory Course
- Delete Moodle user
- reset Moodle password
- Login Moodle User
- Evidently it is difficult to find a way to logout a user via the API, so I’m searching the Moodle code for a hook or function that fires during this process.