Ok, I turned off auto jEmplode update and the error went away... I liked that feature. Will that be available again when you lock down the code?

- Jon