Late last year, we completed a massive transition from Ning 2.0 to Ning 3.0.
I was actually delighted with the process, given the amount of content we had to move over as ours would be one of the longer-running Ning networks still kicking around, and we've always had a lot of content that we didn't want to sacrifice.
We had considered moving to another platform, but we wanted to make the transition to a more modern experience for our users as seemless as possible and thought that moving to Version 3 would get us most of the way to where we wanted to be.
I've been as patient as one can be. I've copped it from our users. I've had to hold off on all the big relaunch plans we had because I'm so embarrassed by this bug. My site is sporting related, and we made this move in the off-season when traffic was low. The season will start in a couple of weeks, and I'm looking at having all of that embarassment, as all our less-than-regular users return to the site and I literally have no indication that this issue can even be fixed. I really should pull the entire site, but it would be devastating to the community and of course, pretty much destory what has been 15 years for me in building up my brand and the site's following, which has already been harmed by the problem.
I'm desperate now. Our migration contact who at least seemed sympathetic to our plight has left the company and I cannot wait any longer for this to get fixed. I can only assume its a migration issue given that other people don't seem to be crying about it, so I would give a very big warning to any big 2.0 sites considering a move to 3.0 that this issue exists as I'd hate to see anyone else go through this.