Open GoogleCodeExporter opened 8 years ago
Could you specify the size ? megabytes ? hundred of kbytes ? This way I can
make a
better test.
Original comment by marcelobarrosalmeida
on 7 Sep 2009 at 12:33
I'm having the same problem with the binaries I installed 3 days ago. I use
Wordmobi 0.9.4 on a Nokia e72. The
article I tried to post has about 350 words or 1800 characters. Although I was
planning to use Wordmobi to post
articles that could be 3 to 4 times that size.
I also have no problems with posting short articles with less than 100 words.
I'm using 3.5g at full speed, so I
doubt the connection could be the problem.
Original comment by dennis.r...@gmail.com
on 12 Apr 2010 at 7:03
I've been experimenting with publishing long posts. Seems when I incrementally
publish my post paragraph by paragraph, that at guarantees I won't lose the
entire
post when the error occurs. It does occur seemingly at random when the post
becomes
longer than three paragraphs. It could be the internet connection strength. At
some
point I got the error, I switched to my browser and opened a random webpage, it
reconnected and I could switch back to wordmobi and publish my post.
So that's what I do now, publish regularly every 5-10 minutes. Some sort of
auto-save
feature would be useful, for example saving my post as draft online or locally.
I see
no reason why I wouldn't want to publish any of my posts as draft, unless I'd
want to
delete it.
Anyway, the increasing size of the post doesn't seem to affect the frequency of
the
error. But it does seem to occur only at the longer posts. Since I only publish
articles, I almost always run into this error once or twice. It's a bit
annoying to
frequently exit my post, publish as draft, update post list, enter the post
again and
continue on the next paragraph. So an auto-save feature which saves as draft by
default would be a fantastic feature here. Or at least the option to publish
while
still creating/editing the post as a shortcut would really help as well.
Original comment by dennis.r...@gmail.com
on 14 Apr 2010 at 7:01
Original issue reported on code.google.com by
zyxf...@gmail.com
on 20 Aug 2009 at 4:13