Here Comes AJAX

As of this writing the Testimonials plug-in is mostly written, with all essential backend code in place. Users are able to view, and submit their own testimonial at will. These submitted testimonials aren’t viewable until they are approved by an administrator. In the administration panel, an administrator may add in, approve, unapproved, delete, and edit testimonials. All variables represented in the database for each testimonial may be edited in the testimonial’s individual edit page, even its unique ID. This was to overcome a slight issue that to resolve completely would require too many extra database reads and writes. Now work resumes on the layout end and AJAX functions for the plug-in. One last feature set would be nice to add to the admin panel is an option for randomizing the first seen testimonial. I just need to figure out where/how other plug-ins have been saving their settings as WordPress doesn’t specify a certain location in their API documentation.

I’m considering creating a Moo.fx plug-in for WordPress, so that various plug-ins can share a common library instead of many separate ones. It’ll have an admin panel that allows to select the inclusion of various parts of the Moo.fx family, incase not all of them are needed. Then all plug-ins with Moo.fx/prototype dependencies can just look for the function wp_moo.fx and if it exists, they can use that instead of adding redundant lines to the head of the xHtml document.

-John Havlik

[end of transmission, stay tuned]

3 thoughts on “Here Comes AJAX

  1. Very, very nice work!

    A couple notes:
    #1 about 10% of our users have their own domain name. So the current prohibition against domains could be problematic.

    Easiest solution may be to resolve the domain names, see if they point to the IP range.

    #2 if we don’t make it super clear, people are going to use that form to ask for a blog… (i.e. I get a lot of emails from people requesting blogs, even when we can’t add them)

    Perhaps under the “signup” option, when our signups ARE closed, people could still enter their email address and a blurb, then they would be notified when signups are open.

    Both #1 and #2 are minor, there’s no hurry on them, you are doing a great job!

    Best regards,

  2. In regards to #1, I was well aware that some people have their own domain name, but most just have it foward to their address. To make the plug-in more friendly for other hosts to use, I’ll add some options to the admin pannel, which can either force a domain, or ip address resolution, but first I think I should try to rap up the rest of the plug-in and make some headway on the RPC plug-in, as well as probably a AJAX signup plug-in.

    -John Havlik

Leave a Reply

Your email address will not be published. Required fields are marked *