Jun
15
Although I personally detest Wordpress, it does have its uses and the user-interface is well-constructed, making it much easier for non-technical users to use it. Regardless, when it doesn't do quite what you want it to do, extending it can sometimes be really easy (due to the massive number of plugins), or extremely difficult. Most of the time, in my case (recently), it's the latter and not the former.
I was recently given the task to import an unmodified XML dataset into a web-based tool as tabular data, HTML'ified, and allow for visual editing of the information, and they wanted to use Wordpress. I thought, "Okay, that should be easy enough." Well, okay, do I create a plugin to handle the import? I don't really want to learn Wordpress hooks and programming functionality considering I hate the thing...no, I'll just import it directly into the database. I used a diff tool to discover that creating a new draft entry only modifies three database tables anyway, that's easy enough. Got that working, 1-2-3, lickity-split!
But now, we need to let staff have access to modify the tabular data.
I was recently given the task to import an unmodified XML dataset into a web-based tool as tabular data, HTML'ified, and allow for visual editing of the information, and they wanted to use Wordpress. I thought, "Okay, that should be easy enough." Well, okay, do I create a plugin to handle the import? I don't really want to learn Wordpress hooks and programming functionality considering I hate the thing...no, I'll just import it directly into the database. I used a diff tool to discover that creating a new draft entry only modifies three database tables anyway, that's easy enough. Got that working, 1-2-3, lickity-split!
But now, we need to let staff have access to modify the tabular data.
