Hi Jeremy

Never could reproduce the error reliably, so gave up in Firefox and moved 
to Chromium.

Syncing would hang in the background without any indication -- when finally 
an error arose (the page would hang, usually when saving a draft), a reset 
of the server would take you back to wherever the sync error occurred 
(which could be some time before.) Impossible to work with.

I think this was more common in inactive tabs whilst I was working in 
another instance in another tab. On occasions, I would open several 
instances in different tabs, and an instance in a tab in the background 
would hang with no activity whatsoever in that tab.

regards

On Tuesday, July 15, 2014 9:56:41 AM UTC+2, Jeremy Ruston wrote:
>
> Hi Matabele
>
>>
>> In my environment, I eventually abandoned the use of Firefox for my 
>> node.js wikis in favour of Chromium (due to recurrent sync errors which 
>> necessitated restarting the server and refreshing my browser.)
>>
>
> I haven't come across the issue of sync errors in Firefox. Were you able 
> to reliably reproduce the problem?
>
> Best wishes
>
> Jeremy
>
>  
>
>>
>> As node.js saves automatically, Tiddlyfox isn't required. 
>>
>> For my standalone wikis, I either save manually in Chromium or use 
>> TiddlyDesktop (which also saves automatically.)
>>
>> regards
>>
>>
>> On Saturday, July 12, 2014 5:36:26 AM UTC+2, Edward Del Grosso wrote:
>>>
>>> I am a new Tiddlywiki user.  I have experimented with it on and off for 
>>> years, but finally have committed to spending the time to really learn how 
>>> to use it.
>>>
>>> I am running OSX Mavericks.  I also have the latest versions of Chrome 
>>> and Firefox installed.  I have tiddlyfox installed as well.
>>>
>>> I started out several days ago and installed tiddlywiki under node.js.   
>>> After doing some image imports and renaming them I began to get errors and 
>>> was loosing images from some of the toddlers.  So in Chrome I opened up 
>>> 127.0.0.1 and loaded my wiki.  Then I saved it on my desktop as a new file 
>>> and abandoned running it under node.js.  Loaded it up with no problem began 
>>> adding toddlers and saving them to a separate directory.   When I was done 
>>> I loaded up the last copy of the wiki(A) I had saved and loaded it no 
>>> problem.  I saved it to the desktop.  When I try to open it Tiddlywiki is 
>>> unresponsive.  When I copy the original file to the desktop with the old 
>>> name,  Tiddlywiki is unresponsive.   When I copy the same file to the same 
>>> directory and open it Tiddlywiki becomes unresponsive.  
>>>
>>> When I go back and open (A)  it loads no problem.
>>>
>>> Sorry to be so long winded.  Just wanted to make sure you had enough 
>>> info if you can help me.
>>>
>>> Thanks
>>> ED 
>>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "TiddlyWiki" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at http://groups.google.com/group/tiddlywiki.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Jeremy Ruston
> mailto:[email protected] <javascript:>
>  

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

Reply via email to