I've just upgraded this blog to
Community Server 2.0. Since I'm not hosting this site on my own servers, the upgrading procedure wasn't so trivial. Database updating required some custom table tweaking due to strict [hosting provider's] security policy, but after after a few hours of peeking and poking, the site seems to be back in business. Got me worried there for a moment....
2f106565-e5a0-4d49-974c-dccb779e3739|0|.0|27604f05-86ad-47ef-9e05-950bb762570c
Tags :