Import and Upgrade not working

[Loren]

I don't see this issue in the forum as an open and urgent problem.  Is it being aggressively worked and I just missed it?  My TiddlyWikis are at the core of managing my professional and personal life and it would be distressing indeed if future upgrades, improvements, and bug fixes were not somehow integrated into my current set of wikis. (I am currently at version 2.6.4 and use Firefox 9.0.1 for viewing/editing)

[Jeremy Ruston]

Hi Loren

The current status is that there are the workarounds described on
tiddlywiki.com. There are ongoing investigations to rewrite the
importing code to use new HTML5 features. Longer term, I'm personally
working on TiddlyWiki5, a complete overhaul of the TiddlyWiki codebase
which will give us a much more stable and flexible base for the
future.

Best wishes

Jeremy

> --
> 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/-/nSeUo9LHLlAJ.
> 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.

[HansBKK]

This issue - stock core TW's incompatibility with modern browsers - has in fact been coming up here for a long time and in fact for those that keep up with threads here been beaten to death.

The problem is that modern security improvements to browser technology don't allow what TW does in modifying its own source file, so a solution requires a major change in the fundamental approach.

Personally I started running in to problems in moving from FF 3 to 4, and since then have continued to use Firefox v3 to run my TWs, 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.

Here's a good source:

http://portableapps.com/apps/internet/firefox_portable/localization#legacy36

FFR I recommend that you keep in closer touch with the community for any other projects that have that level of importance to you. Also note that unless you're a contributor, financial or otherwise to the project you don't really have the right IMO to take the same sort of attitude you would with a commercial supplier. . .

[Loren]

I didn't realize my post had an attitude, HansBKK.  Sorry if it sounded demanding.  That was certainly not my intention.  This is the reason I generally eschew online communities, particularly techies, of which I am one, is that they tend to become elitist, with a strong sense of those that are deserving, and those that are not.  Jeremy's response to my question was kindly, patient, and satisfying.  He's working on it.  That's good enough for me.  I also appreciate your thoughts on an elegant near-term workaround.  I will give that a try.  I am a passive member of the community, and not a contributor, financial or otherwise, so I'm not sure that I am deserving of your feedback.  But I thank you for it, nevertheless.

[HansBKK]

My apologies if I misinterpreted the tone of your post.

"You teach best what you most need to learn."
  - Richard Bach

[Loren]

Upgrades

After some experimentation, I actually found that the following, lifted into my TW a long time ago from where I do not know, to work like a charm for upgrades, even now, and regardless of TW version or browser.  I also do not personally find it any more onerous or cumbersome than the normal upgrade process.

• Open your TiddlyWiki file in FireFox (say it's called "mystuff.html")
• SaveChanges (with SaveBackups switched on) to make sure that you've got a backup of it
• Without closing that page, right-click on this link, select 'Save target' or 'Save link' and save it as "mystuff.html", replacing your existing file
• Now go back to the previously opened copy of "mystuff.html" in your browser and SaveChanges again. It will inherit the newly saved code
• Refresh the page in the browser to verify that the upgrade has worked

The most likely cause of the upgrade process not working properly is that one of the Plugins you're using is not compatible with a change in the new release. If so, you can use the ImportTiddlersPlugin from TiddlyTools to selectively import your content and Plugins into a new empty TiddlyWiki.

Imports

For imports, I found that if in the dialog box, I first selected the source file, say, C:\Users\myaccount\Desktop\test.html, and then manually entered a URL for it in the preceding box, file:///C:/Users/myaccount/Desktop/test.html, that it worked just fine.

[rakugo]

For importing tiddlers **from files** in recent versions of browsers
please try this plugin with modern code:
http://repository.tiddlyspace.com/#TiddlyFileImportr
(tested in Chrome, Safari, Firefox)

Jeremy might it be worth linking to this plugin and other alternatives
from http://tiddlywiki.com ?

On Jan 25, 1:21 pm, Loren <lorenrsoren...@gmail.com> wrote:
> *Upgrades*

>
> After some experimentation, I actually found that the following, lifted
> into my TW a long time ago from where I do not know, to work like a charm
> for upgrades, even now, and regardless of TW version or browser.  I also do
> not personally find it any more onerous or cumbersome than the normal
> upgrade process.
>

>    - Open your TiddlyWiki file in FireFox (say it's called "mystuff.html")
>    - SaveChanges (with SaveBackups switched on) to make sure that you've

>    got a backup of it

>    - Without closing that page, right-click on this link<http://www.tiddlywiki.com/empty.html>,

>    select 'Save target' or 'Save link' and save it as "mystuff.html",
>    replacing your existing file

>    - Now go back to the previously opened copy of "mystuff.html" in your

>    browser and SaveChanges again. It will inherit the newly saved code

>    - Refresh the page in the browser to verify that the upgrade has worked

>
> The most likely cause of the upgrade process not working properly is that
> one of the Plugins you're using is not compatible with a change in the new

> release. If so, you can use the ImportTiddlersPlugin<http://www.tiddlytools.com/#ImportTiddlersPlugin>from

> TiddlyTools to selectively import your content and Plugins into a new empty
> TiddlyWiki.
>

> *Imports*

[Jeremy Ruston]

> Jeremy might it be worth linking to this plugin and other alternatives
> from http://tiddlywiki.com ?

What do you think about adding it to the core? Do you think it's ready?

Cheers

Jeremy

[rakugo]

Well, it doesn't completely mimic existing import code in that
currently it doesn't confirm overwrites amongst other things that I
might be missing. Also the CORs problem remains for importing from
urls this solves the file import problem.

Note in the plugins current form it can be bundled alongside
FileImport and will upgrade TiddlyWiki's import mechanism where it can
and leave them intact where it can't but that then introduces more
code. Alternatively the existing FileImport code might be an optional
plugin / moved to deprecated.

I'd still like more feedback for the plugin as what I've got so far is
not conclusive in particular from IE9 users.

I just tried cooking a tiddlywiki file with the code but ran into a
problem with my use of jQuery in that apparently it is not defined at
the time of running. Will take another look at it some other time...