Trouble importing into Ver 2.5.1

[Morris Gray]

I downloaded a new TiddlyWiki from http://tiddlywiki.com/ and it
turned out to be Version 2.5.1

I cannot import into it using TiddlyTools ImportTiddlersPlugin either
as bookmarklet or by installing ImportTiddlersPlugin directly into the
empty TiddlyWiki.

When you choose the file to import from the plugin doesn't open to let
you see the tiddlers.

I wonder if anyone else has had this problem.

Morris

[alex]

> I wonder if anyone else has had this problem.

No but i updated my core and lost all the content

Alex

[Morris Gray]

I have exhausted all avenues I can think of to use
ImportTiddlersPlugin in 2.5.1 I've used the plugin or bookmarklet
extensively since it first appeared and have had no trouble until now.

I've imported Treeview into 2.5.1 using the rather crude built-in
import but by not being able to select import by tags it is tedious
and error-prone. Treeview seems to work alright at first glance in
2.5.1, but I still worry having the automatic update going to 2.5.1
and beyond during the rather complicated transition of integrating
jQuery past 2.5.0.

Morris

[AndrewMc]

I too updated my core from 2.5.0 to 2.5.1 and lost all of my content.
I immediately reverted to a backup and will stay away from 2.5.1 until
someone can convince me to do otherwise.

Cheers
Andrew

[FND]

> i updated my core and lost all the content

Unfortunately, I can confirm this. After automatically upgrading my
2.5.0 document to 2.5.1 (Firefox on Ubuntu), the store was empty.
Manually importing the tiddlers into a new 2.5.1 document worked though.

It appears this doesn't affect all browsers though.

We're looking into this and will report back ASAP.
Sorry for the inconvenience.

-- F.

[overett1]

On 23 June, 09:27, FND <F...@gmx.net> wrote:
> It appears this doesn't affect all browsers though.
>
> We're looking into this and will report back ASAP.
> Sorry for the inconvenience.

IE6 seems to be a problem with .hta files. The process halts on the
"Reloading the new core code" stage, having opened up a blank browser
window with an ActiveX dialog confirmation sought. Closing and
reloading shows the upgrade as taken place but the store has been
wiped.

Trying IE6 on a .htm file worked smoothly on one tiddlywiki, but got
stuck at the "Saving the new core code" stage on another so no upgrade
took place.

Jonathan

[FND]

> We're looking into this and will report back ASAP.

We have just posted a new beta which should fix the upgrade issue:
http://tiddlywiki.com/beta/
(Turns out it was a somewhat obscure encoding issue.)

For those interested in helping to test this, please install the
BetaUpgradePlugin before upgrading your document:
http://tiddlywiki.com/beta/BetaUpgradePlugin.html
(Please note that beta releases are not meant for production use, so use
a copy of your document for testing.)

We'll be looking into the remaining issues as soon as we're confident
this critical core issue has been resolved.

-- F.

[Paulo Soares]

Successful update from 2.5.0 with Firefox on ubuntu.
--
Paulo Soares

[overett1]

On 23 June, 12:04, FND <F...@gmx.net> wrote:
> We have just posted a new beta which should fix the upgrade issue:
>      http://tiddlywiki.com/beta/
> (Turns out it was a somewhat obscure encoding issue.)
>
> For those interested in helping to test this, please install the
> BetaUpgradePlugin before upgrading your document:
>      http://tiddlywiki.com/beta/BetaUpgradePlugin.html
> (Please note that beta releases are not meant for production use, so use
> a copy of your document for testing.)

Tested on IE6 and it worked upgrading two wikis with .htm filetypes,
but for the same files with a .hta filetype it still opens a new
browser window with ActiveX content and stalls at the "Reloading the
new core code" stage, wiping the store.

Jonathan

[FND]

> Tested on IE6 and it worked upgrading two wikis with .htm filetypes,
> but for the same files with a .hta filetype it still opens a new
> browser window with ActiveX content and stalls

I've raised a ticket:
http://trac.tiddlywiki.org/ticket/1077

> I cannot import [...] using TiddlyTools ImportTiddlersPlugin

You should create a separate thread for this so it's visible to Eric
when he returns from his trip.

-- F.