2-for-1 Special Offer: It's Version 2.4.1 of TiddlyWiki

[Jeremy Ruston]

We've just uploaded version 2.4.1 of TiddlyWiki to the usual place:

http://www.tiddlywiki.com/

This is a minor release, and contains mainly bug fixes. The details are here:

http://trac.tiddlywiki.org/wiki/History#Release2.4.1

Everyone is encouraged to upgrade to the new release, and to use the
recently added upgrade mechanism to do so. If you've got valuable data
locked up in your TiddlyWiki you are encouraged to back it up first,
too. To upgrade, open your current file in your browser and click the
"upgrade" tab of the Backstage Area.

As always, we welcome any comments and suggestions, please just reply
to this posting.

Finally, TiddlyWiki is a group effort that depends on the care and
skill of many people for it's continued good health. I'd particularly
like to thank Martin Budden, Fred Dohr and Eric Shulman for their
efforts who have all done more than their fair share recently.

Cheers

Jeremy

--
Jeremy Ruston
mailto:jer...@osmosoft.com
http://www.tiddlywiki.com

[HeX]

Dear Jeremy,

that's great to hear. Unfortunately the new version 2.4.1 triggers an
error when I try to import Tiddlers from a TW file using backstage->
import.

Steps to reproduce:
* get a fresh empty.html from TW.com
* open empty.html and go to backstage --> import
* choose another TW file to import from
* click open

Result:
* the follwoing error message is displayed in the 'displayMessage
area':

[Exception... "Component returned failure code: 0x80520012
(NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" nsresult:
"0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
file://localhost/path/to//empty.html :: httpReq :: line 7174" data:
no]

note: The same error occurs if empty.html is loaded with file:///path/to/empty.html
(i.e., without the FF3 workaround for cookie location exceptions).

Also, in my working TW with loads of other plugins the error message
does not appear but I'll get about 10 consecutive popup windows
telling me: "TypeError: story.findContainingTiddler(place) is null".
Strangly enough I once I've clicked them all away I can actually see
the tiddler list and proceed. This is not possible on the clean
empty.html from TW.com.

All this did not happen in TW 2.4 (neither in the empty.html nor in my
working TW file).
/HeX


Jeremy Ruston skrev:

[HeX]

Just a minor correction to the path in the error message (before you
start to wonder):

- file://localhost/path/to//empty.html
+ file://localhost/path/to/empty.html

/HeX

[HeX]

OK with the help of FND and TomO I could solve part of the problems
and neither of them are primarily caused by the new release ;)

1.
The exception error:

> [Exception... "Component returned failure code: 0x80520012
> (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" nsresult:
> "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
> file://localhost/path/to//empty.html :: httpReq :: line 7174" data:
> no]

is actually caused by the import file not being in the same directory
as the TW file. If you really like to use an import file in a
different directory then you will have to correct manually the path in
the "Enter the URL or pathname here: " field.

2.
The "TypeError: story.findContainingTiddler(place) is null". is
actually caused by some incompatibility of the GTDPlugins from d3[1].
As d3 is currently not supporting any TW version above 2.1.3 this
mainly an issue I have to come to terms with. The price one has to pay
if he does custom and unsuported upgrades to his d3.

/HeX

[1]: http://www.dcubed.ca

[Eric Shulman]

> The exception error:> [Exception... "Component returned failure code: 0x80520012
> > (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" nsresult:
> > "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
> > file://localhost/path/to//empty.html :: httpReq :: line 7174" data:
> > no]
>
> is actually caused by the import file not being in the same directory
> as the TW file. If you really like to use an import file in a
> different directory then you will have to correct manually the path in
> the "Enter the URL or pathname here: " field.

in FF3, the "browse for file" form control no longer provides access
to the full path/filename that you selected. The result is that
import tiddlers will only look for the correct filename if it is in
the local directory. As already noted, a quick work-around is the
manually fix the path/file in the "enter URL" input field.

However... I have a CoreTweak that *fixes* the problem for FireFox:

The tweak automatically replaces the standard "browse" button with a
button labeled "..." that uses FireFox-specific secure file I/O
functions to invoke an alternative "file picker" dialog that works
exactly the same as the regular "browse" file picker dialog, but
returns the full path/filename to the calling code. The result is
that the correct path is available for use by the ImportTiddlers
functionality, and TW files can once again be selected and imported
from any directory you want.

Get the fix here:
http://www.TiddlyTools.com/#CoreTweaks
(see ticket #683 and #604)

Note: A similar fix was also applied to TiddlyTools plugins that use
the "browse for file" button. You probably want to get those updates
as well:

http://www.TiddlyTools.com/#ImportTiddlersPlugin
http://www.TiddlyTools.com/#AttachFilePlugin

enjoy,
-e

[FND]

> OK with the help of FND and TomO I could solve part of the problems
> and neither of them are primarily caused by the new release ;)

*phew*!

-- F.

[HeX]

Thanks Eric,

I installed your CoreTweaks and it works fine now.

/HeX