On May 29, 2010, at 12:35 AM, Martin Ammermüller wrote: >> I don't see any evidence of a crash from the log you attached. Lots of >> chatter from Maruku (the Markdown processor), which is very verbose, but >> nothing even vaguely indicative of a crash. (Well, OK, I don't see the log >> entry for the "show" action, after you saved the page, but perhaps you cut >> off the log early.) > > Maybe it's a problem with ruby itself. Every crash is accompanied by a > "Application stopped working" dialogue for ruby. And these installers > for Windows are only release candidates. I'll try the 1.8.x ruby > installer and installing by zip files. Maybe that will fix it. > >> Aside from the Maruku chatter, is there anything in the log which looks like >> an error message? > > I don't think so. I've attached my production.log, if you want to have a look.
I see one encoding-mismatch error (discussed below), but nothing else out-of-the-ordinary. Weird. >>> Another thing: is it by design, that wiki words can only be us-ascii? >> >> As you can see from >> >> >> http://golem.ph.utexas.edu/~distler/code/instiki/svn/annotate/head%3A/lib/wiki_words.rb >> >> that's not true. > > Interesting. 'Cause i got an "ArgumentError in WikiController#new" > when i tried to create a new page via a wiki word that contained an > umlaut (see attachment). That's definitely a Ruby 1.9.x error. Rails and Ruby 1.9 is still a work-in-progress. (To explain: In Ruby 1.8, strings are just sequences of bytes; in Ruby 1.9, string are encoding-aware. On the one hand, that's great, because methods that manipulate strings (count the number of characters, or reverse the characters in a string) need to be aware of multi-byte encodings, like utf-8, which is what Rails and Instiki use. On the other hand, all HELL breaks loose if two different libraries disagree about what the encoding of a given string is supposed to be. That's what's happening to cause your error message.) I have been running quite successfully with Ruby 1.9.2 (including creating pages with non-ASCII names). But I encountered problems with 1.9.1. On the other hand, I have users, who are running successfully on 1.9.1, so go figure .... For best stability, I'd still recommend Ruby 1.8.7. Seems to me that there's something causing your Ruby 1.9.1 to die, quite apart from anything going wrong in Instiki itself. Let me know if Ruby 1.8.7 solves your problem. JD
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Instiki-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/instiki-users
