Productions plugin: Two steps forward, one step back

I've made a lot of progress on my plugin. All of the content can be created and edited directly within the plugin. Site administrators can add and edit seasons, venues, and plays. They even have the ability to update cast lists, production and audition dates, and upload publicity photos. The only things left to do were to enable the ability to delete some of those items when needed, and then make the code more "generic" so it would work on another server, instead of only on my specific server.

Or so I thought.

Productions plugin updated

Time for another updated on my Wordpress theater productions plugin.

I've now got it to the point where it can work with either PostgreSQL (which the original application was coded with) OR the MySQL database that runs the Wordpress installation. I happen to prefer PostgreSQL, which is of course why I wrote the original app that way in the first place. However, running against MySQL has the distinct advantage of being much easier for a non-technical person to set up on a new blog.

My first Wordpress plugin

I've been using Wordpress for handling my (dormant) blog for a while now. I've also been hosting the website for Baytown Little Theater, but the content was managed using just HTML. I had a database of productions that was visible on the site, but it was all handled with custom PHP code and. PostgreSQL.

A facelift for my blog

Wendy told me that she wanted her own blog site, (her welcome message is here) so I did some checking for her. In the process, I've decided that I wanted to change my own as well. So I've (hopefully) moved all of my old posts and comments to this new system, based on WordPress 2.

Subscribe to RSS - wordpress