TW5 Problems saving and loading

[Edward Del Grosso]

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 

[Richard Smith]

"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"

To do this bit properly (under Node.js) you have to go to the 'server' tab on the Control Panel and click 'Download offline snapshot' instead of the regular download button, otherwise the file will appear to work but it's "not quite right".

 

"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."

How did you save it to the desktop? You can't use the browser to do it, although again, I think you might get something that seems to work a little bit. At the moment, I don't think there is a 'save as' command in TW so you need to save the file and then move/copy it using finder.

If you've got a working stand-alone TW file (A) then you should be able to make copies of it (in finder) and open them. Does it work?

I am running the same set-up as you so if I can help further, just ask. I haven't experienced any problems with images in the Node.js version.

I have found that it's much better to run TW in firefox than chrome - I usually run both browsers and use firefox just for my TW's

Regards,

Richard

[Edward Del Grosso]

Wow.  Doesn't that explain a lot.  Is this something I should have understood from reading?

Under node.js  what is the best way to save the wiki as you are working on it?

What is the best way to back it up.  Under node.js it looks like all the tiddlers are saved as individual files.

I have installed Firefox thinking that might be the problem.  What kind of problems on Chrome?  I really don't want to be running two browsers?

Thank you.

ED

[Richard Smith]

Wow.  Doesn't that explain a lot.  Is this something I should have understood from reading?

 

I like TiddlyWiki a lot but I think it's fair to say it could use better documentation for newcomers.

 

Under node.js  what is the best way to save the wiki as you are working on it?

It will save itself automatically every time you make a change.

 

What is the best way to back it up.  Under node.js it looks like all the tiddlers are saved as individual files.

Yes, they are. You just need to back up the folder that the wiki runs from. You can also edit the separate tiddler files - just remember to stop and restart node and refresh your browser.

 

I have installed Firefox thinking that might be the problem.  What kind of problems on Chrome?  I really don't want to be running two browsers?

It's really only saving I suppose - it's much easier with tiddlyfox. I find running two browsers quite useful in general but if you don't want to, you should be fine with Chrome as long as you follow the instructions for saving that are given at Tiddlywiki.com

If I were you, I'd give the Node version another go. It automatically saves itself and if you want a standalone you go to the server tab in control panel. I find one of the most useful features of TiddlyWiki to be dragging and dropping tiddlers from one wiki to another. If you start a new Node instance, you should be able to drag in any tiddlers from your earlier files that aren't corrupted.

Regards,
Richard

 

[Edward Del Grosso]

I'll me trying it again in a few days.  Also  I wanted to mention that I found an extension for Chrome called Overwrite existing files.  Not as useful as Tiddlyfox in that it overwrites anything you download.

Thanks for your help

ED

Be the match.  Become a marrow donor.  www.marrow.org

--
You received this message because you are subscribed to a topic in the Google Groups "TiddlyWiki" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tiddlywiki/cF6_WAU7n-M/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tiddlywiki+...@googlegroups.com.
To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

[Matabele]

Hi 

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.)

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

[Jeremy Ruston]

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 tiddlywiki+...@googlegroups.com.

To post to this group, send email to tiddl...@googlegroups.com.
Visit this group at http://groups.google.com/group/tiddlywiki.
For more options, visit https://groups.google.com/d/optout.

--
Jeremy Ruston
mailto:jeremy...@gmail.com

[Matabele]

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