Fix 6 Bugs in Wordpress Plugin

We require a programmer to check the coding of our plugin to isolate and fix 6 bugs. It is likely that the bugs are due to the code being incorrectly upgraded after the wordpress 2.5 and 2.7 changes. You will be supplied with full source code and as such, will be obligated to ensure that it is handled with the strictest confidence. This is a big opportunity for any programmer who is comfortable with wordpress plugins as we have a whole host of extra features we are looking at adding to our plugin and would offer you first refusal of the work. The plugin is a membership plugin that uses paypal IPN to automate the membership process. Please contact me if you need specific information about an area of the plugin. Please only make sensible bids, feel free to ask any questions you want. We need someone who can start on this job very quickly, so please mention how long you estimate before you can start on this job when placing your bid. ## Deliverables I can create example sites to display all of the following bugs for you. The bugs are: **1)** Expiration dates are not being updated on the members page when the users subscription has succeeded on the pay date. **2)** Members accounts are not being restricted when their subscription fails, they cancel their subscription, or their account expires. **3)** When using the [Private] tags to hide content within a post or page, it does not seem to work properly. For example, if a post is created that can only be viewed by guests and premium members, free users can not see the post when logged in. However, when the private tags are used to hide a block of content, the entire post is viewable to free users when logged in. As I understood it, the private tags should hide content from guests, but I had assumed that it would therefore hide the private tagged content from guests and show it to higher levels that were selected as being allowed to view that post. It seems that this is not the case. I would like the private tags to work as I had assumed they would, however, it is something I would like to look at expanding by being able to narrow down exactly which level sees the private block of content. This is listed below, but if you can see a problem with the current system that could be quickly fixed or patched, that would be great. **4)** Upgrade/Downgrade option within the users profile does not work. It usually generates a "user not found" error. It is suspected this problem is caused by the user details being incorrectly called. **5)** When the site owner installs the plugin, they enter their e-mail address etc, but if using phpmail, the address seems to be getting ignored and instead it uses the default wordpress@ address. This would need to be corrected so that it will send the e-mail from a custom address that the user picks. **6)** Registration page cleanup. (not technically a bug) **6.1)** On the wordpress registration page, we need to have the registration options tabable (so that the user can tab from one option or field to the next). **6.2)** Remove the [login to view URL] link from the login/register page. The plugin currently uses a customizable background image for this screen/page, but we would like the [login to view URL] link either removed or changed to link directly to the blog. **6.3)** CSS should be removed from the files to the css file. Some of the css coding is in a php file and not in the css file. As our php files are encrypted, this causes a problem when a user wants to change their css. The site owner should be able to control the css on both the registration/login page and the payment page that follows the registration page where subscription buttons are displayed. Bug #6 is one that we can talk about the best solution for, it does not have to be completed, but we would like it to at least be cleaned up slightly.