So I’m proclaiming today to be “Work on LTB day” instead. First up, backup the entire site, upgrade wordpress, and hope I don’t nuke everything in the process. Wish me luck.
So for almost the better part of a year, I’ve been working on a web-project. It’s nothing earth shattering or revolutionary, it’s just an entire accounting/billing/management/provisioning/support/sales/everything system for a business. I started looking at it over a year ago, around December 2006 I said to myself “Alright, I can do this with Drupal, some of the functionality it needs is already there, and the rest I can code up as modules… perfect.”
So I started playing with Drupal 4.7, learning how the various APIs worked, etc. I loved it, something new to sink my teeth into full tilt. Then in the middle of January 2007, Drupal v5 was released. New APIs, existing contributed modules borked (for a while), much new stuff to learn. Thankfully I had barely done any real *coding* in v4.7… I had spent most of the time up to that point planning, sketching, etc. I spent a couple months learning what all changed, retooling if you will, and decided to run with Drupal v5 as the platform to use for the project…. I hadn’t written much actual code for 4.7 yet, so why tie myself down to the old platform when I can just relearn a little and roll out of the gate on v5…. I started coding in earnest around July, and have been ever since, whenever I get some free time to work on said project. Right now the project is about 95% of where I feel it needs to be in order to launch.. not to be complete, just complete enough that I can use it. The project uses about 15 drupal modules that other people have written for Drupal5 and a set of my own home-rolled modules (currently 8 modules for various functions, totaling around 8500 lines of code so far…)
So of course, Drupal v6 was released just in time for Valentines day. With an entirely new set of enhancements and changes.
So now I’m back to “Do I roll forward with what I have, upgrade the base drupal later”, or “stop everything, get upgraded to v6, THEN continue on”. Sadly the project in question isn’t just a blog or something where I can take the data, move it over, and BOOM, it works.. there’s essentially an entire business operating from beginning to end inside the drupal framework here (APIs to third party services, billing providers, etc)… and it’s all coded to v5..
The problem is, v6 has some things I’d like to use, and some things that I think would lend themselves to helping with the project overall. But jumping to v6 bring a whole set of problems… modules will need to be re-written/upgraded (those 15 modules other people wrote? probably not updated yet for v6… some may never be officially, so I may need to dig into each one and make changes to get them to work)… Plus all the modules I from scratch, will need to be changed in major ways….
But if I put the upgrade off, then I’m stuck with basically writing the remaining sections of code *twice*, once for 5, and again for 6 when I make the upgrade down the road…
I think right now I need to sit down and look more closely at how much has changed in the move to v6, or at least download a copy, play with it, and see how borked my code is when run under it. 🙂 Then maybe I’ll have enough information on hand to make a real decision here.
Alright, so thats the “just cant win” part of this post.. whats the “sometimes you can” part you ask?
My lil Warlock finally made it to 60 in WoW… yeah yeah, I know, the level cap is 70 currently (and 80 soon, with lich king expansion).. but I *finally* got *someone* to 60.. I’m happy… 🙂 (I’ve not exactly been slacking mind you, in addition to the 60 lock, there’s a 48 hunter and a bunch of other lowbies I’m constantly rerolling and experimenting with…), but real life issues (work, the aforementioned project, etc) crimp my WoW time sometimes I fear. 🙁 The point is, I made it to 60.. time to see what all this hype about the outlands is about. 🙂