TW5 Advice on upgrading to new 5.1.20

[Jon]

Hi,

received the following message:

 import - 17:51:47 9 8 2019 (count: 1096)
You are about to import a tiddler that will overwrite a core module tiddler. This is not recommended as it may make the system unstable

Can't imagine what this would be but there doesn't appear to be an option to identify the offending tiddler from the list so as not to import it.

Regards

Jon

[Mark S.]

Is it possible that you have modified existing core modules? Possibly a TOC macro or something?

If you put this in the filter tab of the advanced search:

[all[tiddlers]is[system]!prefix[$:/state]!prefix[$:/temp]!sort[modified]limit[25]]

It might help jog your memory about tiddlers you might have modified. You can increase the "25" to see more.

[Jon]

Hi Mark,

I'm more of a copy and paste kinda guy - I wouldn't really know how to modify anything!

Your filter produced a list of mainly plugins...but I'll investigate.

It would be good at the upgrade stage to know what the problem tiddler is.

Thanks

Jon

[Suzanne McHale]

I had this notice too - on doing that search, I saw I had made copies of some shadow tiddlers to modify these (rather than the originals).

[Michael Wiktowy]

I had this on a couple of mine. I believe that it was flagging $:/core/modules/filters/match.js as that was still selected as being a tiddler to be imported from my old tiddlywiki.

I vaguely remember having to do something with that way back to make a function work and the upgrader may have been just silent on the matter until now. I unchecked that particular tiddler to import and just used what was included in 5.1.20 and things seem to be OK so far.

/Mike

[@magasine]

In my experience, after upgrading 5.1.19 / 5.1.20, when loading the file, the browser returns me the following error warning:

[Jon]

Mark, you were quite right I *did* modify an existing core module (now I know what that is!)

Encouraged by others here locating their own problems, I had another look and in my case it was $:/core/modules/widgets/navigator.js 1.

I only noticed it because of the "1". I can't remember what prompted me to do this but thanks for the pointer and now glad to be fully upgraded.

Regards

Jon

[Suzanne McHale]

Yes, my copies of core tiddlers had the " 1" after the title also; I thought that, being copies (and the original tiddlers thus unaltered), they would not have triggered that warning, but apparently not?

[@magasine]

I found a

$:/tags/StartupAction

  tagged tiddler with a macro that was generating the problem, although I didn't understand the exact cause of the problem.