We still haven't been able to reproduce this locally to fix it, and we've never seen it on our hosted wagns but our best guess is that it has something to do with rails 3. What version of rails are you using?
Sorry, I know this is a frustrating problem. I'm hoping we can nail it down soon.
- ethan
Actually I'm on 2.3.8. but, another clue may be that I had tried to restore my SQL database earlier using "mysqldump" and "source". Is there a better way to backup and reload the contents of a Wagn wiki?
(from email)
It looks like a bug in a recent Rails release, introduced as of 2.3.6 or so. Happily, the Wagns that we host are running 2.3.5, so you should not see those issues on our hosted wagns. Users have reported problems with releases as late as 2.3.8. Until we know more about the bug, we're recommending that folks use 2.3.5 or earlier.
fyi, the code is now requiring version 2.3.5. should help folks avoid this issue.
--Ethan McCutchen.....Fri Nov 19 14:18:46 -0800 2010
Where might one acquire the rails 2.3.5 gem? It appears to be absent from the repository that my ruby gets gems from (whatever is default). Rubygems.org sort of says that it's there, but I cannot seem to get it:
http://rubygems.org/gems/rails/versions/2.3.5
Does that mean getting it from github? https://github.com/rails/rails/tarball/v2.3.5 or https://github.com/rails/rails/tree/v2.3.5
Or using Ruby Version Manager? http://rvm.beginrescueend.com/
I got the Rails 2.3.5 code from GitHub, and now I don't know what to do with it.
--Patrick Gibbs.....Fri Dec 10 01:54:54 -0800 2010
I'm actually kind of new to gems -- Lew always used to handle them -- but I'll look into it. What happens when you do gem install rails -v 2.3.5?
--Ethan McCutchen.....Fri Dec 10 09:36:46 -0800 2010