HELP: Import still not working

[David Masterson]

I understand there is problems with the latest browsers for importing
and updating older (pre-2.6.3) TiddlyWikis. I just tried downloading
a latest TW (2.6.5) and importing everything from another TW in the
current directory. It failed and told me that the URL needs to be
CORS enabled. Can someone explain why when I'm importing from a local
file? This is Windows XP with Firefox 9.01.

I've seen a lot of snippets about this problem posted in many places
(including tiddlywiki.com), but I'm not sure what the current state of
this problem is. Apparently, there are a number of people using TW
even today -- are they all using older versions of the browser (pre-
FF4) to avoid problems with updating and importing? Or is there a new
way of working with TW that I've so far not seen? Inquiring minds
want to know...

[twgrp]

FWIW, I just had that problem earlier today and went back and used an
older FF (3.6) as you mention. I'm no expert so I don't know if that
was the optimal way.

BTW, what do you mean with "Apparently, there are a number of people
using TW even today" - are you referring to that many now use
tiddlyspace, or what do you mean?

:-)

[JMT]

I'm having exactly the same problem.

[HansBKK]

Sorry I can't give a more complete answer, but personally I recommend using the latest Firefox v3 with standard TW, especially to ensure compatibility with plugins that haven't been updated.

Since I also use FF kept updated as an "installed" (=registered with Windows) app, I use the Portable Apps version, which doesn't require installation, can be run from any arbitrary location, including an external drive where the drive letter may change.

It is also compatible with Prism, to create standalone TiddlyWiki "applications" that strip out the FF navigation kruft.

I'm pretty sure this is what you'd search for on google:

FirefoxPortableLegacy36_3.6.23_English.paf

Hope this helps.

[julien23]

Hi there

I am also very annoyed by this importing issue, but I haven't found
alternative to TW neither the time to invest for it.

Prism sounds nice to me.

> HansBBK
Is-it portable ?
Does it works along with "another instance of FF" ?

thanks

[HansBKK]

On Thursday, January 5, 2012 3:07:30 PM UTC+7, julien23 wrote:

Prism sounds nice to me.

> HansBBK
      Is-it portable ?
      Does it works along with "another instance of FF" ?

Yes, the old Prism extension works fine - as does every other extension I ever tried (100's) in portable mode, and therefore by definition along with other instances of FF.

Doing things this way is IMO infinitely easier for most people than trying to get TW to work with recent browsers, at least until the next major revision is released (which I assume will be compatible with them).

Note that what seems to be your TW running an independent "app" is actually just using the FF binaries in a minimalist window. When the extension creates your batch file/icon stuff for you in your users docs&settings folder, you just move them over as regular batch files into your portable apps dirtree, maybe need to change paths to relative if your drive letter changes, but nothing rocket science.

[Alexandre C Vieira]

Great idea!!!

I also use FF9 Portable

I have FF and TiddlyWiki on my stick so I can load my tiddlers anywhere

Regards,

> --
> You received this message because you are subscribed to the Google
> Groups "TiddlyWiki" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/tiddlywiki/-/xIDx_7OrwRkJ.
> To post to this group, send email to tiddl...@googlegroups.com.
> To unsubscribe from this group, send email to
> tiddlywiki+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/tiddlywiki?hl=en.

[rakugo]

File import has been breaking in more recent browsers. If I remember
correctly some browsers are trying to load from a file uri. e.g.
file:///path/to/file - if you put the file in the same working
directory and manually edit the input to just be the filename you may
find it imports okay.

I started trying to tackle file importing in modern browsers using the
File API although didn't get much feedback. I'd be interested in how
you find this plugin:
http://repository.tiddlyspace.com/#TiddlyFileImportr
which swaps out the default file import code for a modern alternative
where it can.

Jon

On Jan 5, 12:39 pm, Alexandre C Vieira <acamargo.vie...@gmail.com>
wrote:

[twgrp]

Does portable FF not conflict with simultaneous instances of FF for
regular surfing? Does Prism change anything?

I use an old FF3.6 that is portable but I cannot run this at the same
time as FF9 standard version.

Thanks

[HansBKK]

On Friday, January 6, 2012 5:28:53 AM UTC+7, twgrp wrote:

Does portable FF not conflict with simultaneous instances of FF for
regular surfing? Does Prism change anything?

I use an old FF3.6 that is portable but I cannot run this at the same
time as FF9 standard version.

Create a general conflict, no. However I do recall running into into FF messages along the lines of "another instance is running".

I'll have a look at my batch files when I get a chance, but from memory, key issues are to not try to share the same profile across separate versions (wait while I google)

-P or -ProfileManager will let you set up different profiles if you haven't already

the

-no-remote

launch parameter is for instances you don't want activated from "outside".

Using the official PortableApps package, there's also a FirefoxPortable.ini file - change the AllowMultipleInstances=false preference to true.

I no longer keep my TW's open unless I'm working on specific projects, and I actually use Chrome now for my day-to-day browsing, (and also have IE9 available to use if I want, found it surprisingly good) so I have to admit I'm not the expert on this specific aspect, Googling will find more details - be sure to post back here with a "canonical" solution if/when you find one.

[HansBKK]

Sorry forgot to address

Does Prism change anything?

Prism is running the same underlying FF3 binaries just in a special mode. Not sure if that mode does anything to "shield" FF3 from launching another instance, most likely not.

Super easy to try though, give it a go!

[Smandoli]

I ran into this. My solution is stupid. But someone else might have
my stupid parameters, so here it is:

1. Download the current TW as an empty file.
2. Copy-and-paste your content from old to new. That's everything in
<div id="storeArea">.

I use Notepad++ and the code-folding makes this easy.

-------------------------------------------------------

> I understand there is problems with the latest browsers for importing

> and updating older (pre-2.6.3) TiddlyWikis. ... It failed and told me that the URL needs to be
> CORS enabled....

[rakugo]

Has anyone tried http://repository.tiddlyspace.com/#TiddlyFileImportr
?

[David Masterson]

Step by step on how to install it in basic TWs would be nice... Is it
a cut and paste (to what?) or is there another approach?

On Jan 9, 5:19 am, rakugo <jdlrob...@gmail.com> wrote:
> Has anyone triedhttp://repository.tiddlyspace.com/#TiddlyFileImportr

[David Masterson]

Copy and paste is very bad, but import seems to be broken.

[Smandoli]

So I take you ended with a working, upgraded wiki?

Because I can go more step-by-step if you wanted.

[FrD]

Hello,

I've tried this plugin to import from a file.
I'm able to import tiddlers ; so good news !

But ... some characters are transformed : "é" becomes "é" and "û" becomes "û" for instance.

Don't know where it comes from. I'm on Xubuntu 11.10, firefox 9.0.1

Apart form this, it gives hope that the import wizzard is about to work again !

[David Masterson]

No, I haven't -- I gave up on it and decided to watch to see if a
better solution came along. Cut/paste is very intensive for upgrading
your TW -- especially if you have a lot of tiddlers to move or TWs to
upgrade. Import -- even from a local file -- seemed to be broken in
the latest browsers (FF8+) with latest TW (2.6.5), but I haven't seen
independent confirmation of that. TW has a lot of plugins (etc.) that
I'd like to take advantage of for managing my information, but I want
to keep the TW up-to-date which is just too complex if import is
broken.

[FrD]

Hi again,

The error I 've just described above just reminded me of an old message of mine about the node.js server (Poul Staugaard) : https://groups.google.com/forum/#!topic/tiddlywiki/iN8EdWCeKco

In fact it seems to be exactly the same problem.

Don't know if this helps ...

FrD

[Smandoli]

Yes, I keep a half-dozen TWs and some are pretty large I'm sure.  It took me prolly a half-hour, if I include the quaking-in-my-shoes time.  And I was glad I'm handy with a swiss-army-knife text editor.  With Notepad ++ (and many others I'm sure), I can find
           <div id="storeArea">
...and then a plugin utility in Notepad++ lets me select everything between that tag and the closing tag. 

The new empty TW has nothing between those tags.  So pasting is simple. 

I was a bit worried about my tweaked code tiddlers, but of course those are held in the same place as my content.  For some reason there was one TW that failed to pick up color palette and some other details; but at that point I could use the backstage Import tool.

I use scavenged underpowered computer hardware; it increases my hourglass time, but nothing over 30 seconds.  

I agree it's a chore.  My own motto is "Go Stupid", and that's what I do in general.  In this case it was worth it to feel up-to-date. 

[Yakov]

> started trying to tackle file importing in modern browsers using the
> File API although didn't get much feedback. I'd be interested in how
> you find this plugin:
> http://repository.tiddlyspace.com/#TiddlyFileImportr
> which swaps out the default file import code for a modern alternative
> where it can.
>
> Jon

That's very interesting and important!

First note: the new wizard doesn't ask if some tiddlers would have get
overriden with imported ones. I tried to import all tiddlers from a
big TiddlyWiki (which caused the old wizard to crash Opera) and while
I didn't waited for them to get imported, pressing "restart wizard" is
much better than getting the browser to crash. Another good thing is
that the new wizard doesn't mess the file address (the old one somewhy
substitute the file://...C/.../the_file.html with file://...C/fakepath/the_file.html
which is to be corrected manually).

The bad news is that I haven't succeed with importing in Opera (11.60)
at all. The wizard sais: "Please wait" and that's where I'm (or it's)
stuck. The same story with FireFox (9). I tried even tiddlers which
have names and content without non-latin symbols. Maybe you can add
some diagnostic messages? Anyway, with which browsers did you succeed?

Are expecting feedback just in this group, or in a specific thread, or
somewhere else?

[rakugo]

On Jan 9, 9:24 pm, Yakov <yakov.litvin.publi...@gmail.com> wrote:
> > started trying to tackle file importing in modern browsers using the
> > File API although didn't get much feedback. I'd be interested in how
> > you find this plugin:
> >http://repository.tiddlyspace.com/#TiddlyFileImportr
> > which swaps out the default file import code for a modern alternative
> > where it can.
>
> > Jon
>
> That's very interesting and important!

Yakov! Thanks for the feedback. Much appreciated.

>
> First note: the new wizard doesn't ask if some tiddlers would have get
> overriden with imported ones.

Ahh interesting! I hadn't thought of this. That's quite an oversight
on my part. I'll look into adding this in a future version

I tried to import all tiddlers from a
> big TiddlyWiki (which caused the old wizard to crash Opera) and while
> I didn't waited for them to get imported, pressing "restart wizard" is
> much better than getting the browser to crash. Another good thing is
> that the new wizard doesn't mess the file address (the old one somewhy
> substitute the file://...C/.../the_file.html with file://...C/fakepath/the_file.html
> which is to be corrected manually).
>
> The bad news is that I haven't succeed with importing in Opera (11.60)
> at all. The wizard sais: "Please wait" and that's where I'm (or it's)
> stuck. The same story with FireFox (9). I tried even tiddlers which
> have names and content without non-latin symbols. Maybe you can add
> some diagnostic messages? Anyway, with which browsers did you succeed?

Interesting. I had succeeded with Firefox 9 so something odd is
happening here. I've added some more status messages. Please let me
know what you see with these additional ones. It's possibly breaking
on a single tiddler.
Are you importing into a blank TiddlyWiki? If not could you try that
and see if there is any difference?
Are you able to share the TiddlyWiki you tried to import from. It
would be good to have some examples.

>
> Are expecting feedback just in this group, or in a specific thread, or
> somewhere else?

Anywhere really. I guess the group would be good to discuss the
plugins and https://github.com/jdlrobson/TiddlyWikiPlugins/issues
would be a good place to keep concrete issues.

Thanks again!
Keen for us to find a future-proof solution to all this as it seems to
be generating a lot of discussion in the group!

[Yakov]

> > I tried to import all tiddlers from a
> > big TiddlyWiki (which caused the old wizard to crash Opera) and while
> > I didn't waited for them to get imported, pressing "restart wizard" is
> > much better than getting the browser to crash. Another good thing is
> > that the new wizard doesn't mess the file address (the old one somewhy
> > substitute the file://...C/.../the_file.html with file://...C/fakepath/the_file.html
> > which is to be corrected manually).
> >
> > The bad news is that I haven't succeed with importing in Opera (11.60)
> > at all. The wizard sais: "Please wait" and that's where I'm (or it's)
> > stuck. The same story with FireFox (9). I tried even tiddlers which
> > have names and content without non-latin symbols. Maybe you can add
> > some diagnostic messages? Anyway, with which browsers did you succeed?
>
> Interesting. I had succeeded with Firefox 9 so something odd is
> happening here. I've added some more status messages. Please let me
> know what you see with these additional ones. It's possibly breaking
> on a single tiddler.

I don't see any new messages, aside that now the wizard sais "Please
wait (Importing EditTemplate)" instead of "Please wait". This is when
importing TW is not empty and has v2.6.0. If I delete all the tiddlers
(besides TiddlyFileImportr), it seems that nothing changes (in both
Opera and FireFox, 9.0.1).

However, in TW v2.6.5 the plugin worked fine for both empty and non-
empty TW, in both Opera and FireFox (haven't tried nonempty in
FireFox, though). And, most importantly for me, massive import in
Opera seems to work fine (there was a non-systematic error when after
import some tiddlers with some core code were stuck together in one of
the tiddlers; now there's no such symptom, but it occured not each
time of import).

> Are you able to share the TiddlyWiki you tried to import from. It
> would be good to have some examples.

So would you like 2.6.0 examples, or you'll try it yourself, or just
skip? Note that all the TWs I imported from are still v2.6.0.

> > Are expecting feedback just in this group, or in a specific thread, or
> > somewhere else?
>
> Anywhere really. I guess the group would be good to discuss the
> plugins and https://github.com/jdlrobson/TiddlyWikiPlugins/issues
> would be a good place to keep concrete issues.

Keep in mind that there's ImportTiddlersPlugin [1] which extends
importing with many options. For me, an important feature it
implements is filtering of tiddlers to import (though, I tried a
minute ago and it doesn't work for me -- as the main import dialogue,
it generates this "fakepath" and doesn't find the file which is
weird). Anyway, perhaps it's a good idea to discuss this with Eric.

[1] http://www.TiddlyTools.com/#ImportTiddlersPlugin

[rakugo]

Okay that narrows it down a lot.
Back in version 2.6.0 the internal saveTiddler function was much more
cumbersome and didn't work quite as nicely as it works now.

Is there any reason you are still using 2.6.0? If not I'd encourage
you to move to a later version as it prevents these sort of problems
as I always test against the latest and greatest TiddlyWiki.
Regardless I've updated the plugin so it should now allow you to
import :-)

Thanks so much for the feedback. If only I can get some more
validation that this works better we can try to get this folded into a
future TiddlyWiki release.

Best wishes
Jon

> > plugins andhttps://github.com/jdlrobson/TiddlyWikiPlugins/issues

[rakugo]

Link remains the same:
http://repository.tiddlyspace.com/#TiddlyFileImportr

[FrD]

Hi

I've tried the new version and managed to import from a 2.6.5 TW on firefox 9.0.1 (xubuntu).
But still the probvlem remains as I said in a previous message (see below).

But when, inside the code, I replace :
 

reader.readAsBinaryString(evt.target.files[0]);

By :
reader.readAsText(evt.target.files[0]);

My problem of "stange" characters disappears : I get "é" ad not "é"

FrD

	moi(FrD Modifier)	Publier une réponse 9 janv. (il y a 2 jours)
	Traduire le message en français

[rakugo]

Whoops.... that's a regression. Fixed! Should be fine now.

[FrD]

Hi,

Works fine now

Thanks a lot !


FrD

[Yakov]

Sorry for long silence, was rather busy lately.

> Is there any reason you are still using 2.6.0? If not I'd encourage
> you to move to a later version as it prevents these sort of problems
> as I always test against the latest and greatest TiddlyWiki.
> Regardless I've updated the plugin so it should now allow you to
> import :-)

Well, there are a couple of reasons:

first, I have many TiddlyWikis, so updating them all without a
particular reason is not a shiny idea; though, I'd like to update some
of them, especially to have Mario's CodeMirror plugins working there;

second, there were some issues regarding updating of TWs in some
versions and at the same time Opera has problems with import (but this
plugin can solve it);

finally, I'd like to overview all the changes between 2.6.0 and 2.6.5
not to get some unexpected behavior. In fact, in some cases I don't
like that content is no longer selected when a tiddler is opened, but
this is not that problematic. But I would love to see the changelog
first, and I haven't succeed in finding it. Do you know any places
where the changelog can be found (I mean the "changelog for users",
don't need "for developers one" for now)?

> Thanks so much for the feedback. If only I can get some more
> validation that this works better we can try to get this folded into a
> future TiddlyWiki release.
>
> Best wishes
> Jon

Ok, what tests would you like get results from? I can test in
different browsers and with various versions of TW. Although, I don't
have TWs older than 2.6.0 with content.

[rakugo]

Hi Yakov!
Sorry missed this one!

> finally, I'd like to overview all the changes between 2.6.0 and 2.6.5
> not to get some unexpected behavior. In fact, in some cases I don't
> like that content is no longer selected when a tiddler is opened, but
> this is not that problematic. But I would love to see the changelog
> first, and I haven't succeed in finding it. Do you know any places
> where the changelog can be found (I mean the "changelog for users",
> don't need "for developers one" for now)?

I don't think so.. there are release notes in the google groups but
I'm not sure if those were shared elsewhere. It would be a good
exercise to collate those and stick them somewhere e.g. linked off
tiddlywiki.org
Of course in terms of the developer changelog it would be a case of
going through old commits

> Ok, what tests would you like get results from? I can test in
> different browsers and with various versions of TW. Although, I don't
> have TWs older than 2.6.0 with content.

I'm not really sure really. I think it's just a case of people having
issues with import using this and saying "that fixed my problem". So
far I'm only aware of you and one other that has tried it - unless
others have tried it and not reported back. I guess this could wait
till a beta release but my experience shows me hardly anyone ever
tries these... especially to the extent of trying things like file
importing!

I am also aware that the existing file importer does things like show
tags and size. I'm not convinced how useful these are but it also
confirms overwriting which probably does need to be addressed. It
would be good to get a feel for if there is any other 'key
functionality' missing.

[j]

The standard TiddlyWiki import works with URI's but a local file import generates the CORS error.
The ImportTiddlersPlugin from TiddlyTools works with local files but the URI import won't show any tiddlers.
The TiddlyFileImportr plugin is working with both URI's and local files.  I'd appreciate having the 'overwrite' warning though.

I find that TiddlyTools ExportTiddlersPlugin is handy for saving just a subset of tiddlers for later re-import using TiddlyFileImportr. 

• TiddlyWiki 2.6.5
• Firefox 11.0
• Windows 7

[bbb]

One more remark: Importing from a local file works when that file is in the same directory with the TiddlyWiki. You may need to change some browser setting (Firefox: about:config).